Powered by
Structure & headings
The Page Has No Main Heading
Without a top-level heading, screen reader users can't jump straight to the main content or quickly confirm which page they're on.
page-has-heading-oneBest practiceBest practice — not a WCAG requirement, but it helps people all the same.
- Status
- ModerateModerate — An annoyance, with a workaround.CurrentScanners run this rule today.
- Owner
- DesignDevContentTest
- Audit
- Automated+ManualA scanner finds it; a person confirms the fix.
Why it matters
A level-one heading (h1) is the page's main title. Many screen reader users press one key to jump to it. That's how they skip menus and find where the content starts.
With no h1, that shortcut lands nowhere. People have to listen through the page to work out where they are. This is a best practice, not a WCAG requirement, but it's cheap and helps a lot.
Who it affects
| Who | What they experience | Impact |
|---|---|---|
| Screen reader users | They press the key for the main heading and hear "no heading level 1", so they must hunt for the content. | High impact |
| Low-vision users (magnification) | Affected if they use a screen reader or a heading list in their magnifier. | Partial impact |
| Cognitive and neurodivergent users | A clear main title helps them confirm they're on the right page, and some reading tools use it. | Partial impact |
Business & product impact
| Area | Why | Impact |
|---|---|---|
| Legal | Not a WCAG requirement on its own. But a clear heading structure supports WCAG 2.2 AA and shows good practice if a complaint is made under the Disability Discrimination Act. | Low impact |
| Conversion | People who can't find the main content quickly may give up, especially on landing and product pages. | Moderate impact |
| SEO | Search engines may read the `h1` as a hint about the topic, but the effect is small. Don't sell it as an SEO win. | Low impact |
| Brand trust | Pages that are easy to scan feel well made to everyone. | Low impact |
| Cost to fix | Usually a one-line fix in the page template. | High impact |
Fixing it in code
A styled title that isn't a heading
Don't
<div class="page-title">Your order</div>A screen reader says: “Your order”
Do
<h1 class="page-title">Your order</h1>A screen reader says: “Heading level 1, Your order”
An h1 marks the main title so screen readers can jump to it.
The logo used as every page's h1
Don't
<h1><img src="logo.svg" alt="Acme"></h1>
<h2>Delivery options</h2>A screen reader says: “Heading level 1, Acme”
Do
<a href="/"><img src="logo.svg" alt="Acme home"></a>
<h1>Delivery options</h1>A screen reader says: “Heading level 1, Delivery options”
The h1 should describe this page, not the site.
Designer's handoff note
Mark one visible main title on every page design and label it h1.
If the design has no visible title, add one, or agree with developers on a hidden heading.
Quick test
Tool
VoiceOver (opens in a new tab) (on every Mac)
Checklist
- Pass
- There is a heading level 1, and it names this page.
- Fail
- There is no level 1 heading, or it only names the site.
Check these at the same time
- A heading has no text in it
empty-heading
What a green scan still misses
A scanner checks that an h1 exists. It can't tell if the words describe the page, or if it sits where the main content starts.
Reference
- Rule ID
page-has-heading-one- Raised by
- axe-core: “Page should contain a level-one heading”
- WCAG
- Best practice — not a WCAG requirement
- Last reviewed
- 14 October 2026