---
title: "Heading Hierarchy: Page Titles and One Clear H1 · Rubric"
description: Give every page a unique title, one H1 and headings nested in order, so people and screen readers can follow how the page is built.
url: https://rubric.design/ux/accessibility.heading-structure
format: agent view of this page
updated: 2026-11-16
---

[UX guides](https://rubric.design/ux/) / [Accessibility](https://rubric.design/ux/topic/accessibility) / Pages have a descriptive title and a logical heading hierarchy

# Pages have a descriptive title and a logical heading hierarchy

Usually high · How serious this usually is when it goes wrong. Not a score.

## The guideline

Give every page a unique `<title>` that identifies its specific content, with the page-specific part first (WCAG 2.2 SC 2.4.2). Use exactly one `<h1>` per page for its main heading, and nest subsequent headings (`h2`, `h3`, …) so the level reflects the content's actual hierarchy without skipping a level just to hit a font size (SC 1.3.1). Write heading text that describes the section it introduces well enough to be understood on its own, since headings are read as a standalone list when a screen reader user scans the page structure (SC 2.4.6). Never mark up a visually prominent line (a tagline, a price, a promotional phrase) as a heading when it does not introduce a section of its own (SC 1.3.1).

## Common failures

- Pages share a generic `<title>` (or repeat the brand name without context), and heading levels skip from `<h1>` straight to `<h3>` or use multiple `<h1>`s.
- A visually prominent line that introduces no section, such as a tagline, a price or a promotional phrase, is marked up as a heading, so it appears in the page's heading list.

## Where it applies

### Where

- Applies to any site

### Disciplines

- Accessibility

### Devices

- Desktop web
- Mobile web

## Why it matters, how to fix it, and the research behind it

Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first.

[Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents)

## Related guides

- [Labels are programmatically associated with their fields](https://rubric.design/ux/accessibility.form-label-association) · Usually critical · Associate every input's visible label with its control using a native \<label for>/id pair, or aria-labelledby when a native label element is not possible.
- [Video and audio content ships with captions and a transcript](https://rubric.design/ux/accessibility.video-captions-transcripts) · Usually critical · Provide synchronized closed captions for every prerecorded video that has a soundtrack, including speaker identification and non-speech sounds that carry…
- [Pointer targets meet a minimum size or spacing](https://rubric.design/ux/accessibility.pointer-target-size) · Usually high · Make every pointer target at least 24 by 24 CSS pixels — the WCAG 2.2 Level AA floor — and design to 44 by 44 wherever the control carries weight, which is…
- [Password composition rules are shown before submission, not after](https://rubric.design/ux/auth.password-requirements-visible) · Usually high · If the password field enforces composition rules, state them next to the field before the first submit attempt — as static hint text or a live checklist that…
- [Autocomplete suggests as the user types, fast, clean and keyboard-operable](https://rubric.design/ux/search.autocomplete-suggestions) · Usually high · Show suggestions after two or three typed characters, with no visible lag or flicker as the user keeps typing.
