- Success Criterion 1.3.1
- Conformance level A
Same Page Content Accidentally Announced More Than Once
1.3.1 — Info and Relationships
Scenario
Setting
A calendar app's event-creation form
What’s wrong
The same content is announced twice — duplicated accessible nodes, or a landmark (a coded page region) re-announced with all its links on every encounter — creating noise and making users doubt where they are.
Example
During an audit of a calendar app's event-creation form: the same content is announced twice — duplicated accessible nodes, or a landmark (a coded page region) re-announced with all its links on every encounter — creating noise and making users doubt where they are.
Why it matters
Screen-reader, braille, and reading-tool users who depend on coded structure rather than visual layout. On a calendar app's event-creation form, that means they can't tell how the page is organized.
How to test
Navigate the page with a screen reader end-to-end: listen for the same landmark, link list, or content block being announced more than once — duplicated accessible nodes create this.
How to fix
Remove duplicated accessible nodes and label landmarks (coded page regions) once so content is announced a single time.
Outcome
With the fix in place on a calendar app's event-creation form, they navigate the content in a sensible order.
Who is affected
Screen-reader, braille, and reading-tool users who depend on coded structure rather than visual layout.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Text Styled to Look Like a Heading Instead of Coded as One
- Text Columns Faked With Spaces Instead of Real Table Markup
- Table Layout Faked With Spaces Instead of Real Table Code
- Clickable Div Acting as a Link Button With No Real Role
- Structural HTML Tags Used Purely for Visual Styling
- Layout-Only Table Wrongly Coded With Real Header Cells