Goal
Help users understand what page they are on.
Success Criterion · WCAG 2.4.2
Page Titled
Web pages have titles that describe topic or purpose.
Level AWCAG 2.0Operable2.4 · Navigable
Copy button ready
What to do
Provide descriptive page titles that identify the page purpose or topic.
Why it matters
Page titles are used by screen readers, browser tabs, bookmarks, and history to orient users.
Success criterion
What WCAG 2.4.2 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Web pages have titles that describe topic or purpose.
Intent
Why WCAG created this requirement
- Titles help users orient and navigate among multiple pages/tabs.
- Screen reader users often rely on titles to confirm context.
- Clear titles improve findability and reduce confusion.
Benefits
Who gains when you pass
- Screen reader users can identify the current page quickly.
- Users with cognitive disabilities benefit from clear context cues.
- All users benefit from clear browser tabs and bookmarks.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may get lost when titles are missing or generic.
Users may choose the wrong tab/page when titles are unclear.
Overview
Each page must have a meaningful, unique title that describes its topic or purpose. Avoid generic titles like “Home” or “Untitled” across many pages.
- Include distinguishing info for similar pages (e.g., “Settings — Security”).
- Ensure single-page apps update document title on route changes.
- Match titles to visible headings when possible.
Reference: All summaries and highlights originate from Understanding WCAG 2.4.2 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.0
- Principle
- Operable
- Guideline
- 2.4 · Navigable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Settings page
Pass
Title is “Account Settings — Billing”.
Fail
Title is “Settings” for every settings subpage.
Tool page
Pass
Title includes tool name and purpose.
Fail
Title is “Developer Playground” only.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document a page-title naming convention for routes (e.g., “Page — Site”).
- Maintain a list of key pages and their intended titles.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Ensure each route/page sets a descriptive title.
- Avoid repeating the same title across multiple pages.
- For apps, update title dynamically on navigation.
- Include key context like section name and entity name when relevant.
Testing ideas
Prove conformance with evidence
- Navigate across pages and verify tab titles update appropriately.
- Check titles in browser history and bookmarks for clarity.
- Use a screen reader to confirm title is announced as expected.
Related success criteria
More from Navigable (2.4)
WCAG 2.4.1Bypass BlocksLevel AWCAG 2.4.3Focus OrderLevel AWCAG 2.4.4Link Purpose (In Context)Level AWCAG 2.4.5Multiple WaysLevel AAWCAG 2.4.6Headings and LabelsLevel AAWCAG 2.4.7Focus VisibleLevel AAWCAG 2.4.8LocationLevel AAAWCAG 2.4.9Link Purpose (Link Only)Level AAAWCAG 2.4.10Section HeadingsLevel AAAWCAG 2.4.11Focus Not Obscured (Minimum)Level AAWCAG 2.4.12Focus Not Obscured (Enhanced)Level AAAWCAG 2.4.13Focus AppearanceLevel AAA