Skip to content
aulys.app · accessibility 100read the statement
Aulys

WCAG 1.3.1 · Level A

What is the correct heading structure for accessibility?

Use one `h1` per page, then nest headings in order without skipping levels (h1 → h2 → h3). Headings must describe the content that follows. WCAG 1.3.1 (Level A) requires structure to be programmatically determinable.

What it is

Heading structure is the outline of a page expressed through h1–h6 levels.

Why it matters

Screen reader users navigate by jumping between headings. A broken or skipped hierarchy makes the page impossible to scan and breaks their mental model.

How to fix it

  1. 01Use exactly one h1 — the page's main title.
  2. 02Nest subsequent headings in order; don't jump from h2 to h4.
  3. 03Choose levels for meaning and hierarchy, not for font size — style separately.

How Aulys catches it

Aulys audits the heading order implied by your frame and flags skipped levels and missing or duplicate h1s.

Scan your first frame free