Why Clear Section Headings Matter for Accessibility

Why This Matters

Without headings, long or complex content becomes difficult to understand and time-consuming to navigate, especially for users who do not perceive page layout visually.

Section headings allow users to:

• Understand how information is grouped
• Skip directly to relevant sections
• Avoid reading large blocks of unrelated content
• Track where they are within a document

For many users, headings are not supplemental; they are the primary navigation mechanism within content.

Who This Helps

This criterion primarily supports:

• Blind users who navigate by headings using screen readers
• Users with cognitive or learning disabilities who rely on clear structure to understand content
• Users with low vision who scan pages using headings as orientation points
• Keyboard users who use assistive technologies or browser features that support heading navigation

What “Programmatic” Means

When WCAG requires headings to be available programmatically, it means:

The section labels must be exposed in the page’s code so assistive technologies can recognise and navigate them, not just styled visually.

For example:

• A bold paragraph styled to look like a heading is not programmatic
• An HTML <h2> element is programmatic

Visual appearance alone does not communicate structure to assistive technologies.

Intent of the Criterion

This success criterion intends to ensure that when content is organised into sections, those sections are clearly identified.

Headings:

• Communicate document structure to assistive technologies
• Provide meaningful navigation targets
• Improve comprehension of long or complex material

Other visual techniques (spacing, borders, colour) may support presentation, but they do not replace headings as a structural indicator.

This criterion also relates closely to SC 1.3.1 Info and Relationships, which requires that structure and relationships be conveyed programmatically.

Why This Is Level AAA

This criterion is placed at Level AAA because it cannot reasonably be applied to all content.

Examples where headings may not be appropriate:

• Personal letters
• Short narrative text
• Historical documents published verbatim

WCAG does not require authors to invent structure where none naturally exists.
It requires headings only when the content is already organised into sections.

What Counts as a Section?

A section exists when content is:

• Grouped by topic or purpose
• Intended to be understood independently
• Part of a larger structured whole

Common examples include:

• Chapters and subtopics in articles
• Grouped settings or preferences
• Categories within informational content

If users would reasonably ask “What is this part about?”, a heading is likely appropriate.

What Counts as a Heading?

Headings can be provided using:

• Semantic HTML heading elements (<h1> to <h6>)
• Clearly labelled titles that introduce sections
• Programmatic structures that expose section labels to assistive technologies

Best practice is to use semantic HTML headings, as they provide predictable behaviour across browsers and assistive technologies.

Heading Structure Matters

Headings should reflect the logical outline of the content, not its visual styling.

Important principles:

• Heading levels should be nested logically (e.g., <h2> under <h1>)
• Heading levels should not be skipped arbitrarily
• Headings should describe the section’s topic, not its appearance

Using headings purely for visual emphasis (for example, to make text larger or bold) can mislead users who navigate by structure.

How Users Navigate with Headings

Screen reader users

• Jump directly between headings
• View a list of all headings on the page
• Navigate to specific sections without reading intervening content

Keyboard users

• Navigate by headings when using assistive technologies or browsers that support heading shortcuts
• Use headings as predictable focus targets within long content

Without headings, users must navigate content sequentially, increasing time, effort, and fatigue.

Common Misconceptions About Headings

• Bold text counts as a heading — it does not
• Short pages don’t need headings — they may, if the content is structured
• More headings always improve accessibility — excessive or meaningless headings can make navigation worse
• Headings are only for screen readers — they benefit all users by clarifying structure

Common Failure Patterns

This criterion commonly fails when:

• Long content is visually divided, but lacks headings
• Sections are indicated only by spacing or colour
• Headings exist visually but are not programmatic
• Heading levels are skipped or misused
• All content is presented as a single continuous block

Examples

Passing example

A menu page is divided into clear sections, each with a heading:

• Appetizers
• Salads
• Soups
• Entrées
• Desserts

Users can jump directly to the section they want.

Passing example

A settings page groups related options under headings such as:

• Account Settings
• Privacy Controls
• Notification Preferences

Each section is clearly labelled and programmatically identifiable.

Failing example

A long article uses spacing and visual separators to imply sections, but provides no headings.
Screen reader users experience the page as a single undifferentiated block of text.

Rule Description

When content is organised into sections, those sections must be clearly identified with headings. This requirement applies to content structure, not interface widgets or controls. If no meaningful sections exist, headings are not required.

The Algorithm

1. Identify whether the content is divided into sections
2. If sections exist:
   • Check that each section has a clear, descriptive heading
3. Confirm headings are:
   • Programmatically available
   • Structurally meaningful
4. If sections exist without headings:
   • The criterion fails

How to Test This

• Review long pages for logical content groupings
• Check that each grouping has a clear heading
• Use a screen reader to list headings
• Verify heading levels reflect content structure
• Ensure headings are not used solely for visual styling

Wrapping Up

Section Headings are about structure, clarity, and navigability. When content is divided into sections, headings provide the anchors users rely on to understand and move through information efficiently. They reduce effort, prevent disorientation, and make complex content usable.

This criterion does not require artificial structure, but when structure exists, it must be communicated clearly, programmatically, and consistently.