What WCAG 2.4.2 Requires
Every page needs a <title> that describes its topic or purpose, so visitors can tell pages apart in browser tabs, bookmarks and search results.
Can AccessBell Test This Automatically?
Yes. AccessBell's scanner runs axe-core, which includes 1 rule that catch code-level failures of this criterion:
document-title— Ensure each HTML document contains a non-empty <title> element (details (opens in a new tab))
This criterion is included in: WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
How to Test It by Hand
Check the browser tab and page source for a <title> tag that is unique and descriptive for each page.
Common Failures
- Every page on the site shares the same generic title.
- A page has no <title> element at all.
Example Fix
- Add a title to every page. The title is the first thing a screen reader announces and what appears in browser tabs.
- Make each title unique. Put the specific page topic first and the site name last.
<head>
<title>Pricing - AccessBell</title>
</head> Related Criteria in Navigable
WCAG 2.4.2 Questions
What does WCAG 2.4.2 require?
Every page needs a
Can AccessBell test WCAG 2.4.2 automatically?
Yes. AccessBell runs 1 automated rule that can catch failures of this criterion, including in our WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.
What level is WCAG 2.4.2?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 2.4.2 Page Titled (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.