2.4.10 Section Headings
Section headings are used to organize the content.
Last reviewed: September 9, 2026
Understanding 2.4.10
Breaking content into sections with real headings lets users scan and jump between parts of a long document instead of reading it linearly. This particularly benefits screen reader users navigating by heading level and users with cognitive or attention-related disabilities who rely on chunked, clearly labeled content to process information in manageable pieces.
How to Meet It
Code Examples
<div class="section-title">Shipping & Returns</div>
<p>...</p><h2>Shipping & Returns</h2>
<p>...</p>Frequently Asked Questions
How is this different from 1.3.1 Info and Relationships, which also requires headings to be marked up correctly?
1.3.1 requires that where a heading is used visually, it must be coded as a real heading element. 2.4.10 goes further by requiring that content actually be organized into sections with headings in the first place; a long, undifferentiated block of text with no heading structure at all can fail 2.4.10 even if there are no fake headings to flag under 1.3.1.
Does every paragraph or short page need its own heading to comply?
No. This criterion applies to organizing substantial content into logical sections, not to mandating a heading for every small chunk of text. A short, single-topic page or a brief paragraph doesn't need to be artificially broken up just to add headings.
Related Success Criteria
Quick Facts
- Criterion2.4.10
- LevelAAA
- IntroducedWCAG 2.0
Automate Compliance
AccessiSight automatically scans and identifies 2.4.10 issues in your codebase.
Try Scanner Free