What this rule checks
Ensure the order of headings is semantically correct.
Why it matters
Screen reader users navigate by headings. This is a best practice supporting WCAG 1.3.1.
This rule is a recommended practice: failing it isn't a WCAG failure on its own, so our reports list it separately from WCAG failures.
How to fix it
- Adjust the heading levels in the affected sections so they go in order without skipping levels.
- Change only the tag, not the visual style (use CSS classes for size).
How to check the fix
- Re-scan and check the heading outline with a browser extension such as HeadingsMap.
How FixReports finds it
Our scan runs the axe-core rule heading-order in a real Chrome browser on every page it tests, and reports each failing element with its page, its markup and, where it applies, a screenshot.
An automated test confirms that this specific problem is present. It can't tell whether the rest of the page is accessible: some barriers only show up when a person checks the page.