Level AAAOperable
2.4.10

Section Headings

Break up content with real headings that label each section, so people can scan and jump around.

In plain English

Long content is much easier to use when it is broken into labelled sections. This AAA rule says use real headings to introduce each section. That is not just visual polish: screen-reader users jump from heading to heading to skim a page, the same way you scan bold titles with your eyes.

The key word is real, actual heading elements (<h2>, <h3>), not text that is merely made big and bold with styling.

Who this is for

  • Screen-reader users, who navigate and skim by pulling up the list of headings.
  • Everyone, who scans headings before deciding what to read.

How to check and fix it yourself

Break long pages (policies, guides, rich product descriptions) into sections, each starting with a proper heading in a sensible order.

<h1>Return Policy</h1>
  <h2>How to start a return</h2>
  <h2>Refund timelines</h2>
  <h2>Exchanges</h2>

Avoid faking headings with bold text, and do not skip levels (h2 to h4) arbitrarily.

Where we can help

We check whether your longer pages use a real, logical heading structure or just big-bold fake headings, and map the outline a screen reader would hear. Clean heading structure also strengthens your SEO.

How to meet it

Techniques the W3C accepts as sufficient (summarized). Follow a link for the full method.

Frequently asked questions

What does section headings require?+

Success Criterion 2.4.10 (Level AAA) says where content is organised into sections, those sections are introduced by headings. It is about using headings to structure longer content, not just as decoration.

Doesn't every page already have headings?+

Many have a title and then walls of text. This rule is about breaking longer content into labelled sections with true heading elements, so it's genuinely navigable, not just one big block with a headline on top.

Why does it help accessibility?+

Screen-reader users jump between headings to skim a page, exactly like a sighted person scans bold section titles. Real, well-structured headings turn a long page into something they can navigate quickly instead of reading top to bottom.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 2.4.10?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit