WCAG 2.1 · Level AA · Operable
WCAG 2.4.6 — Headings and Labels, explained with examples
Headings and labels must describe the topic or purpose of the content they introduce. Generic headings like "Section 1" or labels like "Field" force users to read the content beneath to find context. Descriptive text accelerates navigation for everyone.
- Number
- 2.4.6
- Level
- AA
- Principle
- Operable
- Guideline
- 2.4 Navigable
Why this criterion exists
Generic headings like "Section 1" or labels like "Field" force users to read the content beneath to find context. Descriptive text accelerates navigation for everyone.
If you only remember one thing: headings and labels must describe the topic or purpose of the content they introduce. Everything else on this page is detail.
Who feels it when this fails
Accessibility criteria sometimes feel abstract until you see who pays the cost when a site ignores them. Headings and Labels affects:
Screen reader users
Users with cognitive disabilities scanning for landmarks
How sites typically fail it
These are the patterns we see week after week. None are intentional — they are accidents of how teams build interfaces under deadline. Knowing the failure modes is the fastest path to writing them out of your component library.
Generic headings ("Welcome", "Section")
Form labels reading "Field 1"
How to test for it
Read headings and labels alone; they should still mean something.
Automated scanners catch this criterion most of the time, but never all of the time. Manual testing with the keyboard and a screen reader closes the gap.
A code fix you can copy
Be specific. Headings and labels should describe purpose, not position.
The problem
<h2>Welcome</h2><label>Email</label>The fix
<h2>Reset your password</h2>
<label for="email">Email address we will send the reset link to</label>Be specific. Headings and labels should describe purpose, not position.
Frequently asked questions
Is a heading that just says "Overview" a 2.4.6 failure?
"Overview" is borderline. On a page with a single clear topic it may be sufficient. On a page with multiple overview sections it is ambiguous. The test: if a screen reader user tabs through headings and hears "Overview" without surrounding context, do they know what product, process, or topic the overview covers? If not, make the heading more specific.
Do form field labels need to be long to pass 2.4.6?
No — labels need to describe the purpose, not be exhaustive. "Email" is fine. "City" is fine. "Password (8+ characters, one symbol)" is fine and adds useful instruction. What fails is "Field 1", "Item A", or a label that reads identically on ten different inputs on the same form.
How does 2.4.6 differ from 1.3.1?
WCAG 1.3.1 requires that labels exist and are programmatically associated with their inputs. WCAG 2.4.6 requires that those labels are descriptive. You can satisfy 1.3.1 with a label that reads "Input" — but that would still fail 2.4.6 because it gives no information about what to enter.
Other Operable criteria
2.1.1 Keyboard
Operable · Level A
2.1.2 No Keyboard Trap
Operable · Level A
2.4.3 Focus Order
Operable · Level A
2.4.4 Link Purpose (In Context)
Operable · Level A
All WCAG 2.1 criteria
Browse the full index by principle
Complete WCAG 2.1 guide
POUR principles, conformance levels, legal requirements
How to fix: missing H1 / wrong heading order
Fix recipe · 2.4.6, 1.3.1
How to fix: redundant title attributes
Fix recipe · 2.4.6
Find every accessibility issue on your site in 60 seconds.
Free public scan. No card. AI-generated fixes for every issue we find.