Perceivable

Headings & lists

WCAG 1.3.1 · A · 2.4.6 · AA

Automatic
deterministic fixer, re-verified
Guarded
live before/after diff inside the apply
Decision queue
human decides, machine applies

What the rule requires

Headings and lists are how a screen-reader user skims: jump by heading, count list items. That only works when headings are tagged as headings and lists as lists, rather than lines that start with a dash. PDF/UA requires unbroken heading levels; WCAG treats them as best practice; Proof repairs them either way.

How Proof clears it

  1. Hierarchy repaired automatically: skipped heading levels closed up, lists rebuilt with proper structure, roles mapped correctly.
  2. Guarded repair: structural fixes are re-checked by the rule engine, with a live before/after diff inside the apply.
  3. A reviewer rescues real headings mis-tagged as page furniture — a meaning judgment Proof deliberately doesn’t guess.

Watch it in Proof

Lesson 3.4 · 3:00

Tags and headings

Fix the outline a screen reader navigates by: heading levels that skip a step.

Transcript, chapters and the rest of the Remediators track

What to expect

Whether a big bold line is a heading or decoration is a judgment about meaning. Proof surfaces the candidates with evidence and lets a person decide, instead of guessing wrong at scale.

Run the full profile on one of yours.

Free, no account: one PDF of up to 10 pages and 50 MB per verified email, remediated file and verification record included. Certify it for $59 when you’re ready.