- Success Criterion 1.3.1
- Conformance level A
Plain Text or Buttons Wrongly Wrapped in Heading Tags
1.3.1 — Info and Relationships
Scenario
Setting
A streaming music app's search results
What’s wrong
Plain text, buttons, or links wrapped in heading tags — over-heading that fabricates structure (inverse of F2).
Example
A QA pass on a streaming music app's search results turns this up: plain text, buttons, or links wrapped in heading tags — over-heading that fabricates structure (inverse of F2).
Why it matters
Screen-reader, braille, and reading-tool users who depend on coded structure rather than visual layout. The practical effect on a streaming music app's search results: they can't tell how the page is organized.
How to test
Use a screen reader's headings list: plain text, buttons, or links wrapped in h1-h6 create false headings that clutter navigation — check each listed heading is genuinely one.
How to fix
Reserve heading tags for actual headings — unwrap plain text, buttons, and links from h1–h6.
Outcome
That one change on a streaming music app's search results means they understand how the page is organized.
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