What WCAG 1.3.2 Requires
Content must be readable in a sensible order when linearized, for example by a screen reader or with CSS turned off, even if it is visually arranged with CSS in a different order.
New to this criterion? Read our plain-English guide, WCAG 1.3.2 Meaningful Sequence Explained in Plain English, with examples and code.
Can AccessBell Test This Automatically?
Not fully. Like most WCAG criteria that depend on meaning or context, this one needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it never gets missed.
How to Test It by Hand
Disable CSS (or use the browser's reader view) and check that the page still reads in a logical order.
Common Failures
- CSS grid or flexbox visually reorders content in a way that reads out of order without styling.
- A multi-column layout interleaves unrelated content when linearized.
Related Criteria in Adaptable
WCAG 1.3.2 Questions
What does WCAG 1.3.2 require?
Content must be readable in a sensible order when linearized, for example by a screen reader or with CSS turned off, even if it is visually arranged with CSS in a different order.
Can AccessBell test WCAG 1.3.2 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 1.3.2?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 1.3.2 Meaningful Sequence (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.