Operable · 2.4 Navigable

Section Headings WCAG 2.4.10 · Level AAA

Section headings must be used to organize content, so that distinct sections of writing are introduced by headings. This applies to written content, not to user interface components, and heading is meant broadly to include titles and similar devices.

Level
AAA
Since
WCAG 2.0
Principle
Operable
Guideline
2.4 Navigable

Live demo

Find the part about refunds

The same task, done two ways: switch between the version that passes and the one that fails, or put them side by side. Everything in the box is live, so try it with a keyboard, a pointer or a screen reader.

Open the headings view and try to jump to the part about refunds. Then read the whole policy to compare the two versions.

Live example

Passes

Returns policy

How long you have

You can return most items within 30 days of delivery. Sale items can be returned within 14 days.

What we can take back

Items must be unused and in their original packaging, with all tags attached. For hygiene reasons we cannot take back earrings or swimwear.

How to send an item back

Print the free returns label from your account, then drop the parcel at any post office.

When you get your money

We refund you within five working days of receiving the item, to the card you paid with.

What happened

    Why it passes

    Each topic starts with a heading, so the headings view works like a table of contents and a screen reader user can jump straight to When you get your money.

    Why it fails

    The policy is one run of paragraphs under a single heading. To find the refund rules, a screen reader user has to listen to everything that comes before them.

    Examples

    Code that fails, and the fix

    Four examples, each one running: the usual ways this criterion fails, and code that passes. Listen to them, measure them, or copy the code.

    01What changes 4 lines

    Fails

    A policy as unbroken paragraphs

    Live preview

    HTML
    <h1>Returns policy</h1><p>You can return most items within 30 days of delivery.</p><p>Items must be unused and in their original packaging.</p><p>Print the free returns label from your account and take the parcel to a post office.</p><p>We refund you within five working days of receiving the item.</p>

    The page covers four topics, but only the title is a heading, so nobody can skim the sections or jump to the one they need.

    Passes

    A heading for each topic

    Live preview

    HTML
    <h1>Returns policy</h1><h2>How long you have</h2><p>You can return most items within 30 days of delivery.</p><h2>What we can take back</h2><p>Items must be unused and in their original packaging.</p><h2>How to send an item back</h2><p>Print the free returns label from your account and take the parcel to a post office.</p><h2>When you get your money</h2><p>We refund you within five working days of receiving the item.</p>

    Each section of writing starts with a heading, so people can see how the policy is organized and move straight to the part they need (techniques G141 and H69).

    02What changes 3 lines

    Fails

    Blank lines instead of headings

    Live preview

    HTML
    <p>Check in online from 24 hours before your flight and save your boarding pass.</p><br><br><p>You can take one cabin bag of up to 10 kg and one small handbag.</p><br><br><p>Arrive at the airport at least two hours before departure.</p>

    The changes of topic are shown only by extra space, which gives no structure to move by and nothing for a screen reader to announce.

    Passes

    Headings for each part of the trip

    Live preview

    HTML
    <h2>Checking in</h2><p>Check in online from 24 hours before your flight and save your boarding pass.</p><h2>Your bags</h2><p>You can take one cabin bag of up to 10 kg and one small handbag.</p><h2>Getting to the airport</h2><p>Arrive at the airport at least two hours before departure.</p>

    Each topic has its own heading, so readers see the structure at a glance and screen reader users can move from one part to the next.

    Why it matters

    Who it helps

    Headings break long content into navigable chunks, which helps screen reader users jump between sections and helps people with cognitive or reading disabilities understand the structure and find what they need.

    W3C: Understanding 2.4.10
    • Level AAA

      Level AAA is the highest level. It is not required for whole sites, but it is worth meeting where you can.

    • In WCAG versions

      Part of WCAG 2.0 since December 2008, and of every version after it.

      WCAG 1.0 checkpoints: 3.5, 12.3, 13.4

    • Where it is required

      No law on this site requires Level AAA criteria for whole sites.

    How to test

    Checking it

    A few concrete steps. Automated tools find some failures; most need a person.

    1. Review long or multi-part content and confirm each distinct section starts with a heading.
    2. View the page's heading outline and confirm it reflects how the content is divided into sections.

    Common failures

    Where it breaks

    • A long article or policy is presented as unbroken paragraphs with no section headings.
    • An instructions page marks changes of topic only with extra blank lines instead of headings.