- Success Criterion 1.3.2
- Conformance level A
Reading-Order Override That Contradicts the Actual Content Flow
1.3.2 — Meaningful Sequence
Scenario
Setting
A streaming music app's search results
What’s wrong
aria-flowto/reading-order overrides that contradict comprehension.
Example
A streaming music app's search results is a good example: aria-flowto/reading-order overrides that contradict comprehension.
Why it matters
Screen-reader and keyboard users who encounter content in DOM order. The practical effect on a streaming music app's search results: they can't navigate the content by its real structure.
How to test
Inspect aria-flowto or explicit reading-order overrides in DevTools: read the page with a screen reader and confirm the override actually improves rather than contradicts comprehension.
How to fix
The screen reader must read content in an order matching the visual/logical order, item by item — nothing skipped, merged, fragmented, or added.
Outcome
That one change on a streaming music app's search results means they understand how the page is organized, specifically for the “Reading-Order Override That Contradicts the Actual Content Flow” issue on a streaming music app's search results.
Who is affected
Screen-reader and keyboard users who encounter content in DOM order.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- CSS Layout Changes That Scramble the Screen Reader’s Reading Order
- Word Spelled Out Letter by Letter Instead of Read as a Word
- Text Columns Faked With Spaces Read Aloud Out of Order
- Layout Table That Reads in a Nonsensical Order When Linearized
- CSS Reordering That Makes Code Order Differ From Visual Order
- Multi-Column Article Whose Code Order Interleaves the Columns