Meaningful Sequence
Tier 1 · The normative floor
Baseline compliance
What the normative text of WCAG 2.2 requires, and nothing more. Only a failure of this tier is a WCAG failure.
The bare minimum
When the order of content affects its meaning, a correct reading order can be programmatically determined.
Normative text
Verbatim from WCAG 2.2, W3C Recommendation 12 December 2024. Underlined terms are defined below.
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Not required by the normative text
Common claims that this criterion does not support. Don't log these as WCAG failures.
- Source order matching visual order everywhere. It only matters where the sequence affects meaning.
Definitions used (2)
Glossary definitions are normative. Their notes are informative.
- correct reading sequence
-
any sequence where words and paragraphs are presented in an order that does not change the meaning of the content
- programmatically determined
-
determined by software from author-supplied data provided in a way that different user agents, including assistive technologies, can extract and present this information to users in different modalities
Tier 2 · The gap
Usability & user impact
Where content can meet this criterion and still make things harder for people with disabilities. These are not failures of SC 1.3.2, so raise them as usability defects. Known failures, including failures of related criteria, are listed in Tier 1.
CSS that reorders content visually (flex order, grid placement) can still pass, yet keyboard and screen magnifier users see focus and reading jump around the screen.
Tier 3 · The golden path
Recommended best practice
The pattern that meets the floor, closes the gap, and avoids audit disputes. A recommendation, not a requirement.
Keep source order and visual order the same. Treat CSS reordering as a code-review flag.
W3C's Understanding document and techniques for SC 1.3.2 ↗ are informative: sufficient techniques show ways to pass, and documented failures show common ways to fail, but neither changes what the criterion requires.
How SC 1.3.2 maps to the WCAG 3 draft
From this site's reviewed map to the WCAG 3 editor's draft. It's an interpretation: W3C has not published a mapping.
No provision in the current draft addresses reading sequence.
From WCAG 2.2, section 5.1: “The main content of WCAG 2.2 is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.”