page-has-heading-one
Web validation
<h1>) that reflects the purpose and content of the page.A clear, single <h1> introduces the purpose of the page and anchors the heading hierarchy that follows. Screen reader users rely on this heading to jump straight to the main content, while sighted users gain an immediate visual cue. Skipping the <h1>, or placing it elsewhere, forces people who use assistive technology to wade through extra material before grasping the topic.
Pass Patterns
A level-one heading at the top of the content
A well structured page starts with one <h1>, followed by lower-level headings that nest logically.
<h1>Annual Financial Report 2025</h1>
<section>
<h2>Executive Summary</h2>
…
</section>Fail Patterns
Missing <h1>
Without an <h1>, some users may miss or have difficulty discovering the purpose of the page.
<!-- No level-one heading at all -->
<h2>Product Overview</h2>Try It Yourself
Using a screen reader
New to screen reader testing, or need a refresher?
Review this article first: Practical guides for using screen readers
- Open the page in a desktop screen reader.
- Open the screen reader’s elements list (NVDA
Insert+F7, VoiceOverControl+Option+U), and go to the “Headings” section.
Expected result: The headings list includes a level-one heading.
Actual result: The headings list has no level-one heading, or is empty.
FAQ
Why is this validation considered a best practice?
Although WCAG does not explicitly require a level-one heading, starting the main content with an <h1> improves screen reader navigation. It provides the high level context for the page, and creates a predictable outline for all users.
Why is this issue marked as Moderate?
Missing <h1> headings may hinder quick navigation but rarely block completion of tasks entirely. The impact is noticeable for screen reader users and affects SEO, yet work-arounds (longer navigation, landmarks) still exist, so the severity is classified as Moderate.