WCAG 2.2 - Success Criterion
2.4.2 Page Titled
Description
Web pages must have titles that describe their topic or purpose. The page title is the text in the HTML <title> element, which browsers display in tabs and window title bars and which screen readers announce immediately when a page loads or when a user switches tabs. A descriptive title allows users to quickly identify the content of a page without reading any of the page body.
How To Test
- View the page source or inspect the
<head>element and locate the<title>tag. - Verify that the title text is not empty and is not a placeholder like "Untitled" or "New Page."
- Confirm the title meaningfully describes the specific page's topic or purpose.
- If the site has multiple pages, compare the titles across several pages to confirm each is unique.
- Use a screen reader (NVDA, JAWS, or VoiceOver) and navigate to the page - confirm the title is announced when the page loads.
- Check browser tabs to confirm the title is readable and distinguishable from other open tabs.
Testing Tools
- axe DevTools — Scan for missing skip links and page title issues.
- Lighthouse — Audit to check page title presence and uniqueness.
- NVDA — Screen reader to verify skip link is announced and page title is read on load.
Demo
These titles give screen reader users no useful information about the page's topic. They are indistinguishable across multiple tabs.
<!-- Fail: missing title -->
<title></title>
<!-- Fail: generic placeholder -->
<title>Untitled Document</title>
<!-- Fail: same title on every page -->
<title>My Website</title>
Each page has a unique, descriptive title. The most specific information comes first so it is announced first by screen readers and visible in truncated browser tabs.
<!-- Pass: specific page name first, then site name -->
<title>Contact Us - Acme Corporation</title>
<!-- Pass: product detail page -->
<title>Blue Widget (Large) - ShopExample</title>
<!-- Pass: search results with context -->
<title>Search results for "keyboard" - WCAG 2.2 Demo</title>
Code
When browsing multiple pages of a site, all tabs show the same title. Screen reader users cannot identify which tab contains which content without switching to each one.
Browser tabs open for:
Each page has a unique, specific title. Tab switching is fast because users can identify content by the tab title alone.
Browser tabs open for:
Code
Fail Explanation
A failure occurs when a page has a missing, empty, or generic title - such as "Untitled Document," "Page 1," or a title that is identical across every page of a multi-page site. Screen reader users who have multiple browser tabs open rely on page titles to identify each tab without switching to it; identical or meaningless titles make this impossible. Users with cognitive disabilities and short-term memory challenges also depend on descriptive titles to re-orient themselves when returning to a tab.
Pass Explanation
A passing implementation provides a unique, descriptive <title> element for every page that clearly communicates both the specific page topic and the site name - for example, "Contact Us - Acme Corporation" or "Product Details: Blue Widget - ShopExample." The most specific information should appear first in the title so it is announced first by screen readers and visible in truncated browser tabs.
Notes
Single-page applications (SPAs) that update content dynamically without a full page reload must update the <title> element programmatically as the view changes, and should use an ARIA live region or focus management technique to announce the new title to screen reader users. Automated accessibility checkers can detect missing or empty titles but cannot judge whether a title is meaningful.
Techniques
WCAG techniques used in this demo: H25, G88
Suggested Solutions & References
Curated from 24 real-world audit findings and official WCAG guidance.