Writing Accessible Headings
Writing Accessible Headings records accessibility-focused writing guidance from the named standards body while keeping implementation and wording advice separate from unrelated general style rules.
Use short, descriptive headings that group related content and reflect the document structure; heading meaning should not depend on visual formatting alone.
Key details
Important caveats
Scope Boundary
This page focuses on heading wording and semantic structure, not sentence-case capitalization rules already owned by separate style guides.
Further guidance
Content
Use short, descriptive headings that group related content and reflect the document structure; heading meaning should not depend on visual formatting alone.
Practical Application
Write headings that summarize the section’s topic or task and use them in a logical hierarchy so readers can predict what content follows; do not rely on font size or bold styling alone to communicate structure.
Purpose
W3C WAI says headings should convey meaning and structure and support navigation for assistive-technology users.
Reader Check
If someone scanned only the headings, would the sequence reveal the document’s main sections and their relationship?
Worked Example
Example: Replace “More information” with “Refund eligibility” when the section explains who qualifies for a refund.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Writing for Web Accessibility — W3C WAI (opens in a new tab)W3C Web Accessibility Initiative · W3C WAI guidance for accessible page titles, headings, meaningful link text, text alternatives, transcripts/captions, clear instructions, and clear concise content.