GratisAIfield guide · accessibility

heading audit / page 6 · free workflow

Read a Page the Way a Screen Reader Would — Free

List the headings in order with their levels and the audit marks the ones that break the outline, so a page that is fine visually and useless by keyboard is caught before it ships.

source path: Google NotebookLM · terms checked 2026-09-13

order checked, not stylinga heading is its level, not its font size
breaks markeda skipped level is named
count reportedhow much of the outline is broken

What this replaces

Heading structure is invisible to anyone using their eyes and is the main way screen reader users navigate. This reads the levels in the order you paste them and marks the skips, so a broken outline is found before publication.

Tool note. This runs entirely in your browser — no account, no upload, no paid API key. Google NotebookLM is named as the free source-grounded reading path for the material you paste; its published free-tier terms were checked on 2026-09-13 and can change.

The four passes

01

Collect the smallest useful input

One heading per line with its level, in the order it appears.

02

Let the audit read the order

Each heading is checked against the one before it.

03

Fix the marked breaks first

A skipped level strands everything beneath it.

04

Do not style a paragraph as a heading

The audit reads levels, not appearance.

Try it on the heading audit / page 6

The board below runs in your browser. It opens with a worked sample so the result is visible before you paste anything; switch scenarios, edit the text, or reset to the sample.

first load

running the sample…

first-load · sample values are illustrative, not verified facts

Everything you paste stays in this browser tab. Nothing is uploaded, there is no account, and no request leaves the page to generate the result; clearing site data removes anything saved locally.

What breaks, and what to do

Headings styled but not marked up

A paragraph made bold is not a heading; nothing here can detect that.

Multiple H1s

The audit checks order; one H1 per page is the convention.

Headings hidden visually

Ensure they remain available to assistive technology.

Go deeper — Heading Audit

The free board above is the whole loop. The paid tier keeps the arranged output so you do not rebuild it.

  • Printable audit with the heading outline drawn as a tree — estimate: 17 minutes saved per page, basis: 5 headings re-checked at ~3.4 minutes each
  • Saved local history across pages — estimate: 12 minutes saved per page, basis: re-entering 5 headings at ~2.4 minutes each

$4 one-time

open the app