Common Violations

Missing or Generic Page Titles

The <title> element is usually the very first thing a screen reader announces when a page loads — it's how a user confirms they landed where they meant to, before hearing anything else on the page. It's also what shows up in a browser tab, a bookmark, and a search result. A missing or generic title (an empty <title></title>, or the same "Untitled" / "My App" on every single page) fails all three of those jobs at once.

This is WCAG Success Criterion 2.4.2 (Page Titled), a Level A requirement.

The fix

Every page needs a <title> that's both non-empty and descriptive of that specific page's content — not just the site name repeated everywhere.

<!-- Before: same on every page -->
<title>My App</title>

<!-- After: identifies this specific page -->
<title>Edit Profile — My App</title>

A common, effective pattern is {Page-specific title} — {Site name}, front-loading the unique part first since that's what's most useful when scanning a long list of browser tabs or search results.

Where this quietly breaks in single-page apps

Traditional multi-page sites get this mostly for free — each server-rendered page just needs its own <title> tag. Client-side-routed single-page apps are the more common failure point: navigating between "pages" via JavaScript router changes the URL and the visible content, but if nothing explicitly updates document.title to match, every route silently keeps whatever title the initial page load shipped with. If your site is built with React, Vue, or similar, check that route changes actually update the title — most routing libraries provide a hook or component for exactly this, but it's an easy step to skip.

Why "generic but present" still fails

A <title> that literally says "Page" or the bare site name on every route technically has a non-empty title element, but it doesn't satisfy the intent of the criterion — the title has to actually describe the page's specific topic or purpose. If two different pages on your site would have the identical title, that's a sign the fix isn't done yet.

Official references

Common questions

Why is the page title important for accessibility?
The `<title>` is usually the first thing a screen reader announces on load, letting a user confirm they landed on the right page. It also labels the browser tab, the bookmark, and the search result.
What makes a good page title?
Put the specific, unique page topic first, then the site name — for example the page subject followed by the brand. Avoid repeating one generic title across every page.
Which WCAG rule covers page titles?
SC 2.4.2 (Page Titled), Level A. axe-core reports it as `document-title`.

Want to see how your own site scores?

Run a free accessibility scan