Heading levels are sequential (no skipping from h1 to h3)

Screen reader users navigate pages by jumping between headings with shortcut keys (H in JAWS, NVDA, and VoiceOver). Skipped levels break that outline — a user lands on an h3 and cannot tell whether they missed intermediate context or whether the h2 simply does not exist. This violates WCAG 2.2 SC 1.3.1 (Info and Relationships) and SC 2.4.6 (Headings and Labels), and blocks Section 508 refresh 502.3.5 conformance required for federal procurement. Multiple h1 elements fragment the document model and confuse assistive technology about the page's primary topic.

Walk each route's rendered DOM from top to bottom and ensure heading levels never increase by more than one step. Reserve exactly one h1 per page for the primary topic and demote decorative text to a styled div or span. Example:

<h1>Pricing</h1>
<h2>Plans</h2>
<h3>Pro tier</h3>
<h2>FAQ</h2>

If the visual design calls for smaller text, control size with CSS (font-size, a utility class) — never by picking a lower heading level.