Ensure each page has a descriptive and unique title
Content available in English only.
Accessibility isn’t just about avoiding violations — it’s about ensuring that everyone can use your product with confidence. This guide explains each rule’s intent, highlights common issues, and shows how to fix them according to WCAG and the European Accessibility Act (EAA).
These guidelines do not replace the official WCAG standards. They’re concise, developer-focused notes to help you identify and fix issues effectively.
Every page must have a unique, descriptive title that clearly conveys its content or purpose.
Why this matters and how to fix it
Why this matters
Screen readers announce the page title first when a page loads. The title is also what appears in browser tabs, bookmarks, window switchers, and task switchers. If titles are generic or identical across pages, users cannot tell where they are or move efficiently between sections.
How to fix this issue
Add a <title> element inside <head> that accurately describes the page’s content or function. Ensure titles update when navigating between pages or views, especially in Single Page Applications.
Developer guidance
Use a consistent naming pattern such as '<Primary Page Purpose> – <Product Name>'. In SPAs, update document.title on route change or use your framework's meta/title utilities. Avoid overly generic titles like 'Home', 'Dashboard', or repeating only the site name.
Code examples
Incorrect Implementation
<title>Home</title>Correct Implementation
<title>Accessibility Audit Report – GetWCAG</title>Real-World Examples
Before
Browser tabs when opening different product pages:
- <title>Dashboard</title>
- <title>Dashboard</title>
- <title>Dashboard</title>
→ User cannot distinguish pages.After
Dashboard navigation with descriptive titles:
- <title>Overview – GetWCAG</title>
- <title>Audit Results – GetWCAG</title>
- <title>Billing Settings – GetWCAG</title>
→ Each tab communicates context clearly.Manual testing
- 1. Turn on a screen reader (VoiceOver, NVDA, or TalkBack).
- 2. Open the page or navigate to a new route/view.
- 3. Listen to the first thing announced — it should clearly describe the page.
- 4. Open multiple tabs of the site (e.g., Dashboard, Settings, Reports).
- 5. Use CTRL+Tab (Windows/Linux) or CMD+` (macOS) to cycle between tabs.
- 6. Confirm that each tab title is unique and meaningful.
- 7. If using a Single Page Application, navigate between views and verify the page title updates accordingly (check in browser DevTools → Elements → <title>).
Trusted by organizations across Europe working toward WCAG and EAA conformance