Ensure each page has a descriptive and unique title
Accessibility isn’t only about avoiding violations — it’s about ensuring your product can be used confidently by everyone. This guide explains the principle of this rule, shows what goes wrong in real-world code, and provides a verified fix that meets WCAG and the European Accessibility Act (EAA).
Why this matters and how to fix it
Why this matters
The page title is the first thing screen readers announce when a new page loads. Missing or generic titles make navigation confusing, especially for users relying on assistive technology or browser tabs.
How to fix this issue
Include a `<title>` element inside the `<head>` that accurately describes the page content or function.
Developer guidance
Keep titles concise but meaningful. Follow a consistent format — e.g., 'Product Name | Store Name' or 'Dashboard – GetWCAG'. Test by switching tabs in a screen reader.
Code examples
Incorrect Implementation
<title>Home</title>Correct Implementation
<title>Accessibility Audit Report – GetWCAG</title>
Trusted by organizations across Europe working toward WCAG and EAA conformance