Heading hierarchy is logical

Search engines parse heading tags to build a content outline for your page — a skipped level (H1 → H3) tells crawlers the structure is broken, which can depress keyword relevance signals for the skipped content. WCAG 2.2 SC 1.3.1 (Info and Relationships) and SC 2.4.6 (Headings and Labels) require heading levels to convey actual document structure, not just visual styling. A heading hierarchy violation in a screen reader context causes users to jump unexpectedly between content levels, breaking navigation for keyboard-only and assistive technology users. This also flags on automated accessibility audits, which matters increasingly for enterprise and government procurement.

Audit every route page for heading level skips. Fix violations by inserting the missing level or demoting the offending heading:

// app/docs/page.tsx — fix a skip from H1 → H3
// Before (broken):
<h1>Documentation</h1>
<h3>Installation</h3>  {/* skip! */}

// After (correct):
<h1>Documentation</h1>
<h2>Getting Started</h2>
<h3>Installation</h3>

For UI component headings from libraries like shadcn/ui (e.g., CardTitle rendering as <h3>): check whether the rendered tag level skips relative to surrounding page headings. If it does, override the rendered element via the component's asChild prop or wrap with an explicit heading at the correct level.