What this criterion requires
Headings and labels must describe the topic or purpose of what they head or label.
Who it helps
Screen reader users navigating by headings; people with cognitive disabilities scanning for orientation.
Example: fails vs passes
<h2>More</h2> ... <label>Info</label><h2>Delivery options</h2> ... <label for="tel">Phone number for delivery updates</label>Headings and labels must describe their content - screen reader users navigate by them.
How to meet and fix it
- Make each heading say what its section contains
- Label fields with what to enter ("Work email"), not vague words ("Info")
Common failures auditors find
- Decorative or clever headings that describe nothing
- A column of fields labelled only by a group heading
Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.
Sources
- W3C, Understanding 2.4.6: Headings and Labels - w3.org/WAI
- W3C, How to Meet 2.4.6 (quick reference) - w3.org/WAI/quickref
Last updated . Reviewed by the EqualWeb accessibility team.
Does your site pass 2.4.6?
Run a free automated check now, or have certified IAAP/CPWA auditors test every criterion and document the result.