Auditing a Page Outline by Ear

An outline audit means checking headings the way a screen reader exposes them, ignoring visual styling entirely. 👂

Forget colors and fonts. A clean outline should read as a sensible nested list of section titles, even with no CSS at all.

Pull out just your headings in order. If that list alone summarizes the page, your structure is doing its job well.

First, confirm there is exactly one h1 that names the page. A missing or duplicate h1 is the most common outline flaw.

Walk the levels and watch for a skip, like h2 jumping to h4. Each downward jump should move by exactly one level.

Look for bold text that should be a heading but is a styled div. These hidden gaps leave screen reader users with no signpost.

Browser dev tools and extensions can show an outline view. They list your real headings and flag skipped or missing levels.

Open the headings list in NVDA or VoiceOver. Hearing your own page read aloud reveals confusion no diagram will. 🔊

An empty heading with only an icon reads as nothing and clutters the list. Give every heading real, meaningful text.

Vague headings like More fail the ear test. Out of context, each one should still tell a user what that section covers.

Run a quick outline check on every page before shipping. A two-minute pass catches structure bugs that frustrate users daily.

While auditing, which finding signals a broken heading outline?

You learned to audit by ear: confirm one h1, catch skipped levels, expose fake headings, and verify wording with a real screen reader. ✅