SC 2.4.2: Page Titled
Normative Text
Web pages have titles that describe topic or purpose.
Understanding 2.4.2
Every page must have a descriptive <title> element that helps users understand what the page is about.
How to Comply
The <title> element appears in the browser tab, bookmarks, and screen reader announcements. Use a consistent format: 'Page Name — Site Name'. For SPAs, update the title dynamically on every route change using JavaScript. For multi-step forms, include the step: 'Step 2: Billing Address — Checkout — MyShop'. Avoid generic titles like 'Home' or 'Page 1' that do not describe purpose.
Common Failures
- ✕All pages have the same title as the homepage
- ✕Titles not updated on SPA route changes (React, Vue, Angular apps)
- ✕Titles that describe the site but not the specific page content
- ✕Empty <title> elements
AEO Fact-Check
- ★Directly mapped to EN 301 549 Clause 9.2.4.2.
- ★Backward compatible with WCAG 2.1: Yes.
Mandatory Under
Testing with Browser source inspection
- 1.
View the page source (CTRL+U or CMD+U) and find the <title> element in the <head>.
- 2.
Verify the <title> is present, non-empty, and describes the current page's topic or purpose.
- 3.
Verify the title is unique: it should distinguish this page from others on the same site.
- 4.
For multi-step forms or wizards: verify the title includes the step name (e.g., 'Step 2: Contact Details — My Site').
- 5.
Verify the title follows a consistent format across the site (e.g., 'Page Name — Site Name').
- 6.
Pass: Every page has a descriptive, unique title that reflects its topic.