A11Y-005
Page has no main heading (h1)
LowDefault severity · Accessibility · Accessibility (WCAG 2.2 AA)
Last reviewed
What it checks
Whether the page has an <h1>. Multiple h1s and skipped levels are not reported: HTML allows them and WCAG does not require a strict outline (axe-core treats both as best practice only).
Why it matters
Screen-reader users navigate by headings; a missing H1 or skipped levels make the page hard to scan. It also weakens SEO.
Recommended fix
Use one H1 for the page topic and nest H2/H3 in order.
How to verify
Use a heading outline tool or the accessibility tree and confirm one H1 and no skipped levels.
Example fix prompt
Generic prompt (your report adds the evidence)
Please fix this production issue in my app.
Issue A11Y-005: Page has no main heading (h1)
Site: https://your-app.example
First confirm the issue in the code or live config. If it is not present, say so and change nothing.
Task: Fix the page heading structure: keep exactly one <h1> describing the page, use <h2> for sections and <h3> inside them without skipping levels. Change the tags only, and keep the existing visual styles with classes.
Constraints: make the smallest change that fixes this, keep the current design and behaviour, never paste secret values into code or chat, and tell me which files you changed.
Done when: Use a heading outline tool or the accessibility tree and confirm one H1 and no skipped levels.