- Success Criterion 1.3.2
- Conformance level A
Several Distinct Controls Merged Into One Announced Item
1.3.2 — Meaningful Sequence
Scenario
Setting
A customer-support live-chat widget
What’s wrong
Several distinct controls are merged into one announced item — size options or share buttons read as a single blob, so screen reader users cannot reach or operate them individually.
Example
Open a customer-support live-chat widget and this is what you'll see: several distinct controls are merged into one announced item — size options or share buttons read as a single blob, so screen reader users cannot reach or operate them individually.
Why it matters
Screen-reader and keyboard users who encounter content in DOM order. On a customer-support live-chat widget specifically, they can't tell how the page is organized.
How to test
Tab to a set of related controls (e.g., product size chips): if a screen reader announces them as one single item instead of separately focusable/reachable controls, 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
Fixed, a visitor to a customer-support live-chat widget can move through the content with confidence.
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