Page <title> element must not be empty
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 needs a meaningful <title>—it’s the first thing assistive tech reads.
Why this matters and how to fix it
Why this matters
A blank or missing <title> leaves users—especially screen reader and tab-switching users—without context about what page they are on. The title is the first element announced by assistive technology and appears in browser tabs and history.
How to fix this issue
Ensure the <title> element contains concise, descriptive text that reflects the page's purpose. Do not leave it empty or whitespace-only.
Developer guidance
In templated or dynamic applications, ensure page titles are generated automatically and never left blank. Use the main heading or route name as the title source when unsure.
Code examples
Incorrect Implementation
<title> </title>Correct Implementation
<title>Order Summary – MyShop</title>Real-World Examples
Before
<title></title> <!-- Screen reader announces: 'unknown' or 'blank' -->After
<title>Dashboard – Analytics</title> <!-- Screen reader announces meaningful context -->Manual testing
- 1. Inspect the <title> element in the <head> of the document.
- 2. Confirm it is not empty or whitespace-only.
- 3. Ensure the title meaningfully reflects the page's purpose.
- 4. Switch browser tabs and verify the title clearly identifies the page.
- 5. With a screen reader, confirm the page title is announced when navigating to the page.
Trusted by organizations across Europe working toward WCAG and EAA conformance