WCAG 2.2 success criterion 1.3.2, Meaningful Sequence, is a Level A requirement: reading order follows the visual order.
Read the criterion in the W3C Recommendation, WCAG 2.2 (opens in a new tab).
How BearScan checks it
Reading order follows the visual order
Checked automatically: loads the page in a browser. Severity: medium. A DOM order that fights the visual order makes content read in the wrong sequence.
An approximation: In the rendered page, the children of every container are laid out and put in the order a sighted reader meets them (rows top to bottom, left to right, or right to left in a right-to-left container). Where that differs from the markup order, which is the order a screen reader reads, the pieces are put to a decisions model (TypeSafe's Jev) in both orders: it fails when sure the markup order loses the meaning, and asks for review when unsure. Fixed and sticky layers, inline text and tables are left out, and text drawn by CSS content is not seen.
How to fix it. Keep DOM order matching the visual reading order; correct the source order rather than fighting it with positioning, flex order or grid placement.
All WCAG 2.2 criteria · Next: 1.3.3 Sensory Characteristics
Questions
Is WCAG 1.3.2 required by the ADA?
The ADA doesn't name a technical standard for businesses, but the Justice Department's 2022 guidance points businesses to WCAG, and its 2024 rule for state and local governments adopted WCAG 2.1 Level AA, which includes 1.3.2.
Can an automated tool check WCAG 1.3.2?
Mostly. BearScan checks it automatically (loads the page in a browser). A clean result still isn't proof every page passes, only the pages scanned.
How do I fix a WCAG 1.3.2 failure?
Keep DOM order matching the visual reading order; correct the source order rather than fighting it with positioning, flex order or grid placement.