- 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
<div class="time-slots">
<span class="slot">9:00 AM</span><span class="slot">10:00 AM</span><span class="slot">11:00 AM</span>
</div> Why it matters
A parent using a screen reader hears one continuous run of times and cannot tell there are three separate, bookable slots to choose from.
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
Give each option real structure, a list item and a button, so assistive tech announces the count and lets people select one at a time.
<ul class="time-slots">
<li><button>9:00 AM</button></li>
<li><button>10:00 AM</button></li>
<li><button>11:00 AM</button></li>
</ul> Outcome
A parent using a screen reader hears "list of 3 items" and can select the 10:00 AM slot directly.
Who is affected
Screen reader users lose all indication that the times are distinct, individually selectable options rather than one block of text.
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