Why it matters
Screen-reader users skim pages by heading. Skipped levels make the structure confusing and suggest headings are being picked for their size.
How Patch checks
We run the axe-core "heading-order" rule.
How to fix it
- Use heading levels in order (h1, then h2, then h3) and change their look with CSS.
Your own report goes further: it names the exact pages, services and settings Patch found on your site, and with a full report you get a fix prompt to paste into Lovable, Bolt or Cursor.
Where this applies
Best practice under WCAG 2.2.