WCAG 2.0 · Level A · Perceivable
1.3.2 Meaningful Sequence
Manual verification
How to validate 1.3.2 by hand
Check whether the reading and focus sequence preserves meaning when presentation styling is removed or changed.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Identify content whose meaning depends on sequence, such as steps, conversations, labels with values, or multi-column reading order.
- Read the content linearly with CSS disabled or with a screen reader, and compare the sequence with the intended meaning.
- Check responsive layouts and reordered components to confirm the DOM or accessibility sequence still makes sense.
Evidence to record
Capture the intended sequence and the sequence actually encountered, then describe the resulting ambiguity or incorrect relationship.
Scope and exceptions
A different sequence is not automatically a failure if meaning remains understandable. Judge the content order, not whether it matches a preferred visual layout exactly.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.