Overview
Headings (h1–h6) must form a logical, nested hierarchy. Skipping levels and using headings for visual styling breaks navigation for screen reader users.
The Problem
This pattern is inaccessible — avoid it.
The Fix
Use this accessible pattern instead.
Step-by-step
Every page should have exactly one <h1> — the page's main topic.
Use <h2> for major sections, <h3> for sub-sections under h2, and so on.
Never skip levels (h1 → h3 is wrong; h1 → h2 → h3 is correct).
Don't choose heading levels for their visual size — use CSS to style them.
Use the Headings panel in browser accessibility tools to review the outline.
Framework Notes
How to apply this fix in your stack.