Level A
Operable
WCAG 2.0+
Success Criterion 2.4.2: Page Titled
Official W3C Definition
Web pages have titles that describe topic or purpose.
Why This Criterion Matters
The page title (in the HTML <title> element) is the first thing announced by screen readers when a page loads. It helps users identify pages, appears in browser tabs and history, and is used by search engines. A good title immediately tells users where they are.
Best Practice: Put the unique, page-specific content first in the title, followed by the site name. Example: "Contact Us | Company Name" rather than "Company Name | Contact Us"
Who Benefits
Screen Reader Users
Title is first thing announced when page loads.
Cognitive Disabilities
Clear titles help users confirm they're on correct page.
Low Vision Users
May enlarge title in tab to identify pages.
Everyone
Helps with browser history, bookmarks, and tab management.
How to Meet This Criterion
Title Structure Best Practices
Good Examples
<!-- Good: Specific page content first, then site name -->
<title>Contact Us | Web Standards Commission</title>
<title>WCAG 2.4.2 Page Titled | Web Standards Commission</title>
<title>Shopping Cart (3 items) | Online Store</title>
<!-- Good: Form step indication -->
<title>Checkout - Step 2 of 4: Shipping Address | Store Name</title>
<!-- Good: Search results context -->
<title>Search Results for "accessibility" | Web Standards Commission</title>
<!-- Good: Error indication -->
<title>Error: Please correct form | Contact Us | Company</title>Dynamic Title Updates
Good Example - Single Page Application
<!-- Update title when content changes in SPA -->
<script>
function navigateTo(page) {
// Update page content
loadContent(page);
// Update page title
document.title = pageTitles[page] + ' | My Application';
// Announce to screen readers
announcePageChange(page);
}
</script>
Bad Examples
<!-- Bad: Missing title -->
<head>
<!-- No title element -->
</head>
<!-- Bad: Generic title on all pages -->
<title>Web Standards Commission</title>
<!-- Bad: Unhelpful title -->
<title>Untitled Document</title>
<title>Page 1</title>
<title>Welcome</title>
<!-- Bad: Site name first (unique content truncated in tabs) -->
<title>Web Standards Commission - Contact Us - Get Help - Support</title>Common Failures to Avoid
| Failure | Problem | Solution |
|---|---|---|
| Missing title element | Screen readers announce filename or URL | Add descriptive title to every page |
| Same title on every page | Users can't distinguish pages | Make each title unique and descriptive |
| Site name first | Unique content truncated in tabs | Put page-specific content first |
| Title doesn't match content | Confusing navigation | Ensure title accurately describes page |
| SPA doesn't update title | Title stays same as page changes | Update document.title on navigation |
Testing Methods
Manual Testing Steps
- Check every page: View title in browser tab
- Verify uniqueness: Each page should have distinct title
- Check descriptiveness: Does title describe page content?
- Test with screen reader: Title should be first thing announced
- Check SPAs: Title should update when view changes
Automated Testing
- Browser DevTools: Check
<title>element exists - WAVE: Flags missing or duplicate titles
- axe DevTools: Checks for title presence
- Lighthouse: Reports missing page titles
Related Criteria
1.3.1 Info and Relationships
Proper semantic structure including headings
2.4.4 Link Purpose
Links should describe their destination