Navigation & links

The Page Has No Title

Without a page title, people can't tell which page or tab they're on, and screen readers announce only the web address or nothing useful.

document-titleWCAG 2.0Introduced in WCAG 2.0.Level AA — the minimum. Missing it blocks people outright.

Status: SeriousSerious — Significant friction, or information that is lost.CurrentScanners run this rule today.
Owner: DevContentTestProduct
Audit: Automated+ManualA scanner finds it; a person confirms the fix.

Why it matters

The page title is the text in the browser tab, in bookmarks and in history. It's also the first thing a screen reader says when a page loads.

Without it, people with many tabs open can't find the right one. Screen reader users can't confirm they reached the page they meant to.

Who it affects

Who it affects, and how much
Who	What they experience	Impact
Screen reader users	They hear the web address or "untitled" instead of the page's name when it loads or when they switch tabs.	High impact
Cognitive and neurodivergent users	With no name on the tab, it's hard to remember which page is which, or to get back to one.	High impact
Low-vision users (magnification)	Zoomed in, they often check the tab to confirm where they are, and find nothing useful there.	Partial impact
Keyboard-only users	Switching tabs by keyboard shows no names, so finding the right tab takes longer.	Partial impact
Voice control users	They can't easily say which tab or window to switch to.	Partial impact

Business & product impact

Business & product impact, with how much each claim weighs
Area	Why	Impact
Legal	Page titles are a Level A requirement under WCAG 2.2, the minimum. Australia's Disability Discrimination Act complaints and EN 301 549 both point to WCAG.	High impact
Conversion	Shoppers comparing tabs may lose your page and close it. Clear titles also help people return through history and bookmarks.	Moderate impact
SEO	This is a rare case where search does care. Search engines show the title as the result's headline.	High impact
Brand trust	An "Untitled" tab or a raw web address looks unfinished.	Moderate impact
Cost to fix	A one-line fix in the page template. Single-page apps also need the title updated on each route change.	High impact

Fixing it in code

Add a title to the page

Don't

<head>
  <meta charset="utf-8">
</head>

A screen reader says: “shop.example.com/cart, web content”

<head>
  <meta charset="utf-8">
  <title>Your cart – Example Shop</title>
</head>

A screen reader says: “Your cart – Example Shop, web content”

The <title> gives the page a name that browsers and screen readers announce.

Update the title in a single-page app

Don't

router.on('navigate', (route) => {
  render(route);
});

A screen reader says: “Example Shop (the same on every screen)”

router.on('navigate', (route) => {
  render(route);
  document.title = route.name + ' – Example Shop';
});

A screen reader says: “Checkout – Example Shop”

Each new screen gets its own title, not just the first page load.

Fixing it in design and content

Write a title that names the page

Don't

Every page is titled "Home" or just "Example Shop".

A screen reader says: “Example Shop”

Put the page's purpose first, then the site name: "Order confirmed – Example Shop".

A screen reader says: “Order confirmed – Example Shop”

The unique part comes first, so people hear it straight away.

Designer's handoff note

Include the page title in every page or screen spec, with the unique part first.

Show steps and states in it too, like "Step 2 of 3: Delivery" or "Error: Sign in".

Quick test

Tool

Any browser (no install)

Checklist

Step 1: Open the page.
Step 2: Look at the text in the browser tab, or hover over the tab.
Step 3: Click to another screen in the app and check the tab again.

Pass: The tab shows a clear name that matches what's on the page, and changes with each screen.
Fail: The tab shows the web address, "Untitled", or the same name on every screen.

What a green scan still misses

A scanner checks that a title exists and isn't empty. It can't tell whether the title describes the page, or whether every screen in an app gets its own.

Reference

Rule ID: document-title
Raised by: axe-core: “Documents must have <title> element to aid in navigation”
Lighthouse: “Document has a <title> element”
WCAG: 2.4.2 Page Titled (opens in a new tab) · Level A · since WCAG 2.0
Other standards: EN 301 549 9.2.4.2 · RGAA 8.5.1
Read more: Deque University: document-title (opens in a new tab)
Last reviewed: 14 October 2026