What This Rule Checks
Every document should include a <title> element with meaningful text that briefly and accurately describes the page’s content. The title serves two purposes: improving accessibility for screen readers and enhancing SEO for search engines.
Who Is Affected
This issue primarily affects: Blind users, who rely entirely on screen readers or braille displays to navigate and interact with content; Deafblind users, who rely on braille displays and cannot access visual or auditory content; Mobility users, who navigate using keyboards, switches, voice control, or other assistive input devices.
Why This Matters
The page title is the first thing announced by screen readers when a page loads. It helps users identify the page and distinguish between multiple open tabs. Missing or generic titles violate WCAG 2.4.2 (Page Titled).
How to Fix
Add a Descriptive Title Element
Ensure each webpage contains a <title> element within the <head> section of the HTML document. The title should be brief yet descriptive, summarizing the content or purpose of the page.
Avoid Titles Like “Untitled Page” or “Home”
Generic or non-descriptive titles do not provide users with enough information to understand the page’s purpose. Titles should be specific to the page’s content.
Code Examples
<!-- Missing title -->
<head>
<meta charset="UTF-8">
</head>
Copy
<!-- Descriptive, unique title -->
<head>
<title>Pricing Plans - AccessibilityChecker.org</title>
</head>
Copy
Common Mistakes to Avoid
- Using the same title on every page (e.g., just the site name).
- Making titles too long or stuffed with keywords.
- Using titles that don’t reflect the page content.
- Leaving titles empty or using only whitespace.
Tip: Page-level metadata and settings affect the entire browsing experience. Language declarations, viewport settings, and page titles are foundational to accessibility and affect every user on every page load.
Related WCAG Criteria
- 2.4.2: Page Titled