meaningful-heading
Mobile validation
Sighted users and people with low vision rely on headings to scan a screen and understand where they are. Screen reader users jump between headings, with TalkBack's heading navigation or the VoiceOver rotor, to skip large blocks of content. When a heading does not describe the content below it, all of these users may miss what they need. Identify the main idea of the content that follows the heading, and make the heading specific, so it stands apart from other sections on the screen and elsewhere in the app. State what ties the content together, so users can predict what they will find. Avoid vague or repeated headings, such as “Details” or “More”.
Pass Patterns
Specific section headings
A product screen uses the headings “Shipping and delivery” and “Returns policy”, which tell users exactly what each section contains.
Headings that set similar sections apart
An order history screen uses the headings “Order #4821, March 3” and “Order #4790, February 18”, so each section can be told apart.
Fail Patterns
Vague headings
A product screen uses the headings “Details” and “More”, which do not describe the content below them.
Repeated headings
An order history screen uses the heading “Order” for every section, so users cannot tell the sections apart when navigating by heading.
Try It Yourself
Using a screen reader
New to screen reader testing, or need a refresher?
Review this article first: Practical guides for using screen readers
- Turn on VoiceOver on iOS, or TalkBack on Android.
- Set the screen reader to move by headings: on iOS, choose Headings in the rotor; on Android, choose Headings in TalkBack's reading controls.
- Swipe down or up to move from heading to heading, and listen to each one.
Expected results: Each heading describes the content that follows it, and you can tell the sections apart from their headings alone.
Actual results: Headings are vague or repeated, so you cannot tell what each section contains.
FAQ
How does this issue relate to 2.4.6 Headings and Labels?
SC 2.4.6 requires headings to describe the topic or purpose of the content they introduce. Vague or repeated headings do not indicate what their sections contain, so the criterion is not met.
Why is this issue marked as Moderate?
Unclear headings make it harder to understand the screen and slow down navigation, especially for people who move between sections by heading. Users can usually still reach the content by reading more of the screen, so it rarely blocks a task, and it is rated moderate.
Standards and Regulations
| Standard | Success Criterion | Reference |
|---|---|---|
| WCAG 2.2 | 2.4.6 Headings and Labels (AA) | Headings and labels describe topic or purpose. |
| EN 301 549 | 11.2.4.6 Headings and Labels | Same as the WCAG text. |