12.4% of home pages have missing or unhelpful titles
2.4.2 Page Titled
In Plain Language
Every web page must have a descriptive, unique <title> element that identifies the page content. The title is the first thing a screen reader announces when a page loads, and it appears in browser tabs, bookmarks, and search results.
Generic titles like "Untitled" or "Home" make it impossible for users to distinguish between open pages.
Why It Matters
- Screen readers announce the page title immediately when a page loads -- it is the user's first orientation cue.
- Users with multiple tabs open rely on titles to find the right page without clicking through each one.
- Descriptive titles help all users orient themselves, especially when navigating back through browser history.
- Single-page applications (SPAs) commonly fail this criterion because the title is not updated when views change.
Examples
Do: Descriptive, unique titles
<!-- Pattern: Page Name | Site Name -->
<title>Adult Literacy Programs | Bridges Learning Center</title>
<title>Contact Us | Bridges Learning Center</title>
<title>Spring 2026 Events | Bridges Learning Center</title>
Don't: Generic or missing titles
How to Fix It
- Use a consistent title format. The recommended pattern is "Page Name | Site Name" -- put the unique page identifier first so screen reader users hear the most important part immediately.
- Make every title unique. No two pages on your site should share the same title. Each title should clearly describe that page's specific content or purpose.
- Update titles in SPAs. When your application changes views without a full page load, update
document.titlein your router or use a framework-specific approach (e.g., React Helmet, Vue Meta). - Avoid generic titles. Replace titles like "Home", "Page 1", "Untitled", or just the site name with descriptive alternatives that identify the content.