WCAG 1.3.2: Meaningful Sequence
1.3 Adaptable
What Does This Criterion Require?
When the sequence of content affects meaning, a correct reading sequence can be programmatically determined.
Technical Details
| WCAG Level | A |
|---|---|
| WCAG Version | 2.1, 2.2 |
| POUR Principle | Perceivable |
| Guideline | 1.3 Adaptable |
| A11yied Testing | Fully Automated |
How A11yied Tests This Criterion
A11yied automatically validates WCAG 1.3.2 using browser-based testing that analyzes your page in real-time.
Implementation: reading-order.ts
Testing Notes:
Comprehensive implementation with 5 rules: logical tab order (no positive tabindex), link keyboard accessibility, visual layout order validation (browser-based with getBoundingClientRect, RTL/LTR support, CSS reordering detection), structural HTML nesting, and form field sequence. Browser validator detects flexbox order, grid placement, absolute/fixed positioning, and float reordering. Total 245 passing tests across JSDOM and browser suites.
Last verified: 10/11/2025
Test This Criterion on Your Site
Use A11yied to scan your website and identify WCAG 1.3.2 violations automatically. Get detailed reports with code examples and fix recommendations.
Start Free ScanRelated WCAG Criteria
Official WCAG Reference
View the official WCAG specification for 1.3.2 Meaningful Sequence on the W3C website for complete technical details and implementation guidance.
Read W3C Understanding 1.3.2→