- Success Criterion 1.3.2
- Conformance level A
Heading or Sentence Split Into Disconnected Announced Fragments
1.3.2 — Meaningful Sequence
Scenario
Setting
An insurance company's claims form
What’s wrong
A single logical text unit (heading, sentence) split across sibling elements/spans so screen readers announce it in fragments.
Example
An insurance company's claims form runs into this exact issue: a single logical text unit (heading, sentence) split across sibling elements/spans so screen readers announce it in fragments.
Why it matters
Screen-reader and keyboard users who encounter content in DOM order. In this case (an insurance company's claims form), they can't tell what's going on without extra effort.
How to test
Read a heading or sentence with a screen reader: if it's split across multiple sibling elements/spans, it may be announced in disconnected fragments instead of one unit.
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
Once corrected, an insurance company's claims form lets them navigate the content in a sensible order, specifically for the “Heading or Sentence Split Into Disconnected Announced Fragments” issue on an insurance company's claims form.
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