Goal
Use clear section headings to help users navigate and understand content structure.
Success Criterion · WCAG 2.4.10
Section Headings
Section headings are used to organize the content.
Level AAAWCAG 2.0Operable2.4 · Navigable
Copy button ready
What to do
Provide section headings where appropriate for organizing content.
Why it matters
Headings provide navigation points and structure, especially important for screen reader users and users with cognitive disabilities.
Success criterion
What WCAG 2.4.10 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Section headings are used to organize the content.
Intent
Why WCAG created this requirement
- Headings provide structure and help users find relevant content.
- Screen readers allow navigation by headings, making them a key wayfinding tool.
- This is especially important for long pages and complex content.
Benefits
Who gains when you pass
- Screen reader users can jump between sections efficiently.
- Users with cognitive disabilities benefit from clear structure and chunking.
- All users can scan long pages more quickly.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Long pages without headings are hard to navigate and comprehend.
Users may miss relevant content because it is not clearly sectioned.
Overview
This AAA criterion encourages using headings to divide content into logical sections. Headings improve scannability and enable assistive technologies to navigate quickly.
- Use real heading elements (h2/h3/etc.), not styled divs.
- Keep heading hierarchy logical and avoid skipping levels without reason.
- Ensure headings are descriptive (see 2.4.6).
Reference: All summaries and highlights originate from Understanding WCAG 2.4.10 and the W3C quick reference.
Fast facts
- Conformance level
- Level AAA
- WCAG version introduced
- WCAG 2.0
- Principle
- Operable
- Guideline
- 2.4 · Navigable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Long article
Pass
Article has headings for Introduction, Steps, Examples, FAQ.
Fail
Article is a single uninterrupted block of text.
Tool page
Pass
Tool page uses headings for Inputs, Results, Export, FAQ.
Fail
Tool page uses only visual spacing with no semantic headings.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document heading hierarchy patterns per template.
- Maintain guidance for content authors on when and how to use headings.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Add headings to long pages and group related content under them.
- Use semantic heading elements and maintain hierarchy.
- Ensure headings reflect the content that follows.
- Avoid heading misuse (do not use headings purely for styling).
Testing ideas
Prove conformance with evidence
- Navigate headings using a screen reader and confirm structure matches the page.
- Verify headings exist for major sections on long pages.
- Check heading hierarchy for logical ordering.
Related success criteria
More from Navigable (2.4)
WCAG 2.4.1Bypass BlocksLevel AWCAG 2.4.2Page TitledLevel AWCAG 2.4.3Focus OrderLevel AWCAG 2.4.4Link Purpose (In Context)Level AWCAG 2.4.5Multiple WaysLevel AAWCAG 2.4.6Headings and LabelsLevel AAWCAG 2.4.7Focus VisibleLevel AAWCAG 2.4.8LocationLevel AAAWCAG 2.4.9Link Purpose (Link Only)Level AAAWCAG 2.4.11Focus Not Obscured (Minimum)Level AAWCAG 2.4.12Focus Not Obscured (Enhanced)Level AAAWCAG 2.4.13Focus AppearanceLevel AAA