- Success Criterion 1.3.2
- Conformance level A
Separate Content Items Announced as One Run-On Block
1.3.2 — Meaningful Sequence
Scenario
Setting
A childcare-booking service's scheduling page
What’s wrong
Distinct content items run together into one announcement because structural separation is missing.
Example
During an audit of a childcare-booking service's scheduling page: distinct content items run together into one announcement because structural separation is missing.
Why it matters
Screen-reader and keyboard users who encounter content in DOM order. The practical effect on a childcare-booking service's scheduling page: they can't tell how the page is organized.
How to test
Read distinct items (e.g., separate list entries or product cards) with a screen reader: if they're announced run together as one block with no separation, it fails.
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 childcare-booking service's scheduling page means they understand how the page is organized.
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