Keep headings in a logical order (WCAG 1.3.1)

Heading levels should not skip — don't jump from an <h2> straight to an <h4>.

Why it matters

Screen-reader users navigate by headings to understand and skim page structure. Skipped levels break that mental outline and imply a section that isn't there.

How to fix it

Use headings to convey structure, not size — style with CSS instead. Nest levels sequentially: h1 → h2 → h3.

<!-- Fails -->
<h2>Features</h2>
<h4>Scanning</h4>

<!-- Passes -->
<h2>Features</h2>
<h3>Scanning</h3>

Does your site have this issue?

Run a free scan to find out in seconds.

Scan page

Related guides

Fix low colour contrast (WCAG 1.4.3) 1.4.3 Contrast (Minimum)
Add text alternatives to images (WCAG 1.1.1) 1.1.1 Non-text Content
Give links a discernible name (WCAG 2.4.4) 2.4.4 Link Purpose / 4.1.2 Name, Role, Value
Give buttons a discernible name (WCAG 4.1.2) 4.1.2 Name, Role, Value

These guides cover automated checks (~30–40% of WCAG criteria). A full audit also needs manual review.