Heading hierarchy present and logical; no skipped heading levels on any page

Screen readers expose a page outline built entirely from heading elements. Users—especially blind users navigating long pages—jump between headings using the H key to skim structure. A heading hierarchy that skips levels (H1 → H3, H2 → H4) breaks this outline, making the document feel structurally incoherent and forcing users to re-navigate to understand context. WCAG 2.2 SC 1.3.1 (Level A) requires information conveyed through structure to be programmatically determinable, and SC 2.4.6 (Level AA) requires headings to be descriptive. Section 508 2018 Refresh 502.3.6 incorporates both.

Audit the heading structure of each page using browser DevTools (Accessibility tab) or the axe extension, then restructure to enforce sequential levels. Never skip from H1 to H3 or H2 to H4:

{/* Correct: sequential nesting */}
<h1>Documentation</h1>
<h2>Getting Started</h2>
<h3>Installation</h3>
<h3>Configuration</h3>
<h2>API Reference</h2>
<h3>Authentication</h3>
<h4>OAuth Flow</h4>

If a heading level looks visually wrong after correction, fix the style, not the hierarchy:

/* Style H3 to look large without breaking hierarchy */
h3.section-title { font-size: 1.5rem; font-weight: 700; }

Never choose a heading tag for its default visual size—use CSS instead.