Page Has Heading One

A page must contain a clear and meaningful level-one heading so users and assistive technologies can understand the main topic of the content. This blog explains what the page-has-heading-one rule checks, why an <h1> is essential for structure and navigation, how to implement it correctly and how this supports WCAG 2.2 and wider accessibility expectations. The article is fully original, accurate and structured using the Welcoming Web content framework.

What it is

The page-has-heading-one rule checks whether a page, or at least one of its frames, contains a single <h1> element. The <h1> represents the primary heading for the content. It forms a key part of the document’s semantic structure.

Headings help assistive technologies interpret hierarchy and allow users to navigate content quickly.

Why it matters

When a page does not contain a level-one heading: - screen reader users may struggle to understand the main topic of the page, - navigation through headings becomes less predictable, - users with cognitive impairments may find it harder to grasp structure, - search engines may interpret content inconsistently, - page templates may appear fragmented or incomplete.

An <h1> sets the context and anchors the page hierarchy.

Who delivers it

Designers define heading patterns and ensure a clear hierarchy. Content authors write descriptive headings that summarise page purpose. Front end developers implement semantic heading levels in templates and components. Accessibility specialists and QA testers validate that each page includes one primary heading. Welcoming Web assists by detecting pages missing an <h1>.

How to ensure a page contains a level-one heading

1. Include exactly one <h1> element

Each page or frame should contain one primary heading.

<h1>Account overview</h1>

2. Use <h1> for the main topic only

Do not use <h1> repeatedly across different sections.

3. Keep headings descriptive and relevant

The <h1> should summarise the page purpose clearly.

4. Ensure templates include consistent heading structure

CMS templates and page builders must generate an <h1> automatically or require one.

5. Avoid skipping directly to deeper heading levels

Maintain a logical sequence from <h1> downward.

Best practice guidance

Use meaningful headings that describe content rather than decorative or generic phrases. Align <h1> text with page titles where possible. Avoid placing logos or non-content items inside headings. Confirm that iframes containing standalone documents also include a primary heading.

Compliance mapping

Providing a level-one heading supports: - WCAG 2.2 Info and Relationships success criterion, - WCAG 2.2 Meaningful Sequence requirements, - ADA Title III expectations for understandable content, - EN 301 549 guidance on structural navigation, - Equality Act 2010 duties for clear and accessible communication.

Welcoming Web supports alignment with recognised standards but does not issue or guarantee compliance certification.

How Welcoming Web supports teams

Welcoming Web identifies pages that lack an <h1> element or contain multiple primary headings. The platform highlights structural issues and provides guidance for restoring heading hierarchy.

Key points for development teams

Include one <h1> per page. Keep the heading descriptive. Maintain logical structure. Use templates that enforce hierarchy. Support accessible navigation.

Call to action

Run an audit Check your site for pages missing a level-one heading. Supports WCAG 2.2 and ADA goals.

FAQs

What does the page-has-heading-one rule check

It checks whether a page or frame contains a single <h1> element.

Why is an

important It provides the main topic and defines the top of the heading hierarchy.

Can a page have more than one

It is discouraged, as it creates confusion for assistive technologies.

Do I need an

inside an iframe If the iframe loads a standalone document, it should include an <h1>.

Can the logo be the

Only if it genuinely represents the main topic of the page.

Does using

help SEO It helps search engines understand page structure but should be used semantically.

Does adding an

guarantee WCAG compliance It supports structural requirements but does not guarantee full compliance.

How does Welcoming Web help with heading issues

Welcoming Web detects missing or multiple <h1> elements and guides teams toward clear structure.

Disclaimer

Welcoming Web supports accessibility improvement and alignment with recognised standards but does not issue or guarantee compliance certification.