We'd like to set Google Analytics cookies to learn how people use the Knowledge Base, so we can improve it. We set them only if you accept.

Skip to main content
Digital Accessibility Knowledge Base

heading-order

Web validation

Heading levels order on the page should be consecutive.

Headings outline the page for everyone. When their levels follow a strict numerical sequence, <h1>, then <h2>, then <h3>, and so on, screen reader users can jump through the content confidently, and sighted users get a clear visual hierarchy. Skipped levels or decorative heading markup break that outline and slow navigation, and compromise the clarity of the content hierarchy.

Pass Patterns

A cohesive outline keeps each level consecutive

The structure moves from h1 → h2 → h3 without skipping, so assistive technology users understand the hierarchy immediately.

HTML
<main>
    <h1>Campus Housing</h1>
    <p>Overview…</p>


    <h2>Residence Halls</h2>
    <h3>North Hall</h3>
    <p>Details…</p>


    <h2>Dining Options</h2>
    <p>Details…</p>
</main>

Fail Patterns

Jumping over a level confuses assistive technology and people who rely on it

Because the document goes straight from h1 to h3, screen reader users cannot tell whether content is a subsection of the previous heading or a new major section.

HTML
<main>
    <h1>Campus Housing</h1>
    <p>Overview…</p>


    <h3>Residence Halls</h3> <!-- skips h2 -->
    <p>Details…</p>
</main>

Try It Yourself

Using a screen reader

New to screen reader testing, or need a refresher?
Review this article first: Practical guides for using screen readers

  1. Open the page in a desktop screen reader.
  2. Open the screen reader’s elements list (NVDA Insert+F7, VoiceOver Control+Option+U), and go to the “Headings” section.

Expected result: Headings on the list have a consecutive order like in the image below.

macOS VoiceOver's headings list that displays a list of the headings of the Screen Reader entry in Wikipedia

Actual result: Headings on the list do not have a clear order and hierarchy.

FAQ

Why is this validation considered a best practice?

WCAG doesn’t mandate sequential heading order, yet consecutive levels make pages easier to navigate and understand, especially for screen reader users. Following this rule therefore improves usability even when strict conformance isn’t required.

Why is this issue marked as Moderate?

Skipped levels rarely block access entirely, but they slow users who navigate by headings and can cause significant cognitive load. Most browsers and assistive technologies still expose the headings, so the impact is moderate rather than critical.

Standards and Regulations

This issue is classified as "Best Practice," meaning it isn't tied to a specific WCAG success criterion or any other regulation or standard; however it still affects the experience of some users. These issues fall outside formal compliance requirements, yet addressing them improves usability and accessibility in practice.

Personas impacted by this issue