- Success Criterion 1.3.1
- Conformance level A
Page Content Missing Landmark Regions Entirely
1.3.1 — Info and Relationships
Scenario
Setting
A music streaming app's playlist screen
What’s wrong
Landmarks absent or wrong: page content outside any landmark (a coded page region), multiple unlabeled navs, banner/main misuse.
Example
<div class="heading">Shipping Address</div>Why it matters
Screen-reader, braille, and reading-tool users who depend on coded structure rather than visual layout.
How to test
Use a screen reader's landmarks list (NVDA Insert+F7, VoiceOver Rotor): confirm one main, correctly labeled nav/banner/contentinfo — content sitting outside any landmark fails.
How to fix
Place all content in labeled landmarks (coded page regions): one main, named navs, correct banner/contentinfo.
<h2>Shipping Address</h2>A real heading element exposes the section structure to assistive tech; a styled div doesn't.
Outcome
On a music streaming app's playlist screen, this barrier is gone for screen-reader, braille — they can complete the task without hitting this wall.
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