document-title · WCAG 2.4.2 Page Titled · Level AHow to fix the “document-title” accessibility issue
The axe-core document-title rule fails when the page has no non-empty <title>. The title is the first thing a screen reader announces and how users tell tabs apart. WCAG 2.2 (2.4.2, Level A) requires every page to have a descriptive title.
What axe-core checks
axe-core fails when the document has no <title> element or it is empty/whitespace. It does not judge quality — but a good title is unique and describes the page.
Which standard this maps to
| WCAG 2.2 | 2.4.2 Page Titled (Level A) |
| EN 301 549 | 9.2.4.2 |
| BFSG / EAA | BFSG § 12 via EN 301 549 · EAA Annex I |
| Category | Structure & Landmarks |
Why it matters
A screen-reader user with ten tabs open relies on the title to navigate. A shop where every page is titled “Home” or untitled is disorienting — and a Level A failure a tester will note immediately in a BFSG review.
Common causes
- Pages rendered by a SPA that never updates
<title> - A single shared title across every route
- Empty
<title></title>left in a template - Title set only after a slow JS render
How to fix it
Give each page a unique, descriptive <title> — ideally “Page topic — Brand”. In SPAs, update it on every route change.
<!-- Fails -->
<title></title>
<!-- Passes -->
<title>Running shoes — Acme Store</title>FAQ
Aim for roughly 50–60 characters so it is not truncated in search results and browser tabs.
It should describe the page first; natural keywords help SEO, but clarity for the user comes first.
Find every issue like this on your site
Run a free WCAG 2.2 AA scan — real axe-core engine, no signup. Or get a timestamped evidence report for €29.