meaningful-page-title
Web validation
The page title, set by the <title> element, is the first thing a screen reader announces when a page loads, and it labels the browser tab, bookmarks, history, and search results. Users rely on it to confirm where they are and to tell pages apart.
When the title does not reflect the page's content, for example, a placeholder left from a template, such as "Untitled Document", users who rely on it to orient themselves may feel confused or disoriented. According to the W3C, a page title should:
- Clearly indicate what the webpage is about.
- Make sense when read out of context, for example, by a screen reader or in a site map or list of search results.
- Be short.
Pass Patterns
Title that describes the page
The title names the specific page first, then the site, so it makes sense on its own.
<title>Order confirmation - MyShop</title>Title that changes with the view in a single-page app
The app updates document.title whenever the view changes, so the title always matches the current content.
function showAccountSettings() {
// Render the account settings view…
document.title = "Account settings - FlowBank";
}Fail Patterns
Placeholder title left from a template
The title is the default placeholder from the project template and was never replaced, so it says nothing about the page and is the same on every page of the app.
<title>Untitled Document</title>Title that does not match the content
The page shows an order confirmation, but the title still names the previous step, so users may think the order was not placed.
<!-- Page content: "Thank you! Your order #1234 has been placed." -->
<title>Checkout - MyShop</title>WCAG techniques
Sufficient techniques
Advisory techniques
Failure techniques
ACT Rules
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
- Load the page with a screen reader running.
- Listen to the first announcement.
Expected results: The screen reader announces a title that describes the page's topic or purpose.
Actual results: The announced title is generic, outdated, or unrelated to the page's content.
Inspecting the browser tab
- Load the page and read the title shown in the browser tab.
- Compare it with the page's main heading and content.
Expected results: The title clearly identifies the page's topic or purpose.
Actual results: The title does not describe the page, or it is identical to the titles of other, different pages.
FAQ
How does this issue relate to 2.4.2 Page Titled?
SC 2.4.2 requires every web page to have a title that describes its topic or purpose. A title that is present but generic, outdated, or inaccurate does not describe the page, so it does not meet the criterion.
Why is this issue marked as Moderate?
Users still get a title, but it does not help them confirm where they are or distinguish the page from others. This causes confusion and slows orientation, especially for screen reader users, but rarely blocks a task outright, so it is rated moderate.
How is this different from document-title?
document-title checks that a page has a non-empty <title> at all. This validation checks that the title that exists actually describes the page.
Why does this check require human review?
Whether a title accurately describes a page depends on the page's content and purpose, which a tool cannot fully judge. This check surfaces titles that may not be descriptive so a reviewer can confirm whether they match the page.
Standards and Regulations
| Standard | Success Criterion | Reference |
|---|---|---|
| WCAG 2.2 | 2.4.2 Page Titled (A) | Web pages have titles that describe topic or purpose. |
| EN 301 549 | 9.2.4.2 Page Titled | Same as the WCAG text. |
| 508 Trusted Tester | 2.4.2-page-title-purpose, 12.B | The <title> element identifies the contents or purpose of the web page. |