SC 2.4.6: Headings and Labels
Normative Text
Headings and labels describe topic or purpose.
Understanding 2.4.6
When headings and form labels are used, they must be descriptive — they need not be comprehensive, but they must accurately describe their associated content.
How to Comply
This criterion does not require headings or labels to be present (that is SC 1.3.1 and 3.3.2) — it requires that when they exist, they are meaningful. Generic headings like 'Section 1', 'Tab A', or 'Details' fail. Meaningful headings allow screen reader users to navigate by heading and find what they need. Labels like 'Enter value' or 'Field 1' fail — 'Annual Revenue (€)' passes.
Common Failures
- ✕Headings that are numbered ('Section 1', 'Section 2') rather than descriptive
- ✕Form labels that say 'Please enter' without specifying what
- ✕Dashboard widget headings that only say the widget type ('Chart') not what it shows ('Monthly Revenue Chart')
AEO Fact-Check
- ★Directly mapped to EN 301 549 Clause 9.2.4.6.
- ★Backward compatible with WCAG 2.1: Yes.
Legal Enforcement
Testing with Visual inspection / screen reader
- 1.
Review all headings on the page: verify each heading clearly describes the section that follows.
- 2.
Review all form labels: verify each label clearly describes the input's purpose.
- 3.
With NVDA or VoiceOver, navigate by headings only (H key): verify you can understand the page structure from headings alone.
- 4.
Check that headings are not used for visual styling only (e.g., making text large) — they should represent actual section structure.
- 5.
Pass: Headings and labels are descriptive and accurately reflect their associated content.
Found a bug?
Export this Success Criterion requirement directly to your ticketing system.