WCAG 2.4.2Level ASeriousDocument

How to fix: Page missing or empty title

Every page needs a non-empty <title> element in the <head> that uniquely describes the page, because it is the first thing a screen reader announces and the label shown in the browser tab, bookmark, and history.

What it is

The <title> element lives in the document <head> and names the page. WCAG Success Criterion 2.4.2 Titled Pages requires that web pages have titles that describe their topic or purpose, so users can tell pages apart without reading the content. It is also the text that surfaces in the browser tab, the bookmark a user saves, the entry in their history, and the blue line in a search result, so it does a lot of work in a single short string.

For assistive technology the title is foundational. When a screen reader loads a page, the title is the very first thing it speaks, before any heading or body text. It is how a user confirms they landed on the right page and how they orient themselves when several tabs are open. A user switching between three tabs hears the title of each one to find the page they want, so a missing or duplicated title leaves them navigating blind.

Two states fail this rule: the page has no <title> element at all, or the element exists but is empty or contains only whitespace. Both leave users with nothing to identify the page by. A good title is unique across your site and front-loads the specific information, typically the page subject followed by the site name, for example "Pricing — AccessKnight" rather than a generic, repeated "Home" on every page.

Who it affects & why it matters

Screen reader users are affected first and most. The title is their initial point of reference, so when it is missing they may hear the URL or nothing meaningful, and when every page shares the same title they cannot distinguish one tab or history entry from another. This makes multi-tab and back-button workflows, which sighted users do effortlessly, slow and error-prone.

It also affects users with cognitive disabilities who rely on clear page identification to stay oriented, anyone managing a row of open tabs, and people returning through bookmarks or browser history. Descriptive titles double as an SEO and click-through win, since search engines weight the title heavily, so this is one fix that helps disabled users and your traffic at the same time.

A missing or empty page title is a Level A failure under SC 2.4.2, the most basic conformance tier, and it is trivial for an automated tool or a plaintiff to detect because there is exactly one title per page. WCAG 2.1 Level AA is the de-facto benchmark U.S. courts apply to ADA Title III claims, and Level AA includes every Level A criterion, so an absent title is a clear, documented gap in any audit or demand letter.

Web accessibility lawsuits have climbed year over year, and the majority target businesses under $25 million in revenue. A descriptive title is a near-zero-effort fix, one line per page, that immediately resolves a page-level violation while improving how your pages read in search results, browser tabs, and shared bookmarks. Leaving it blank is hard to justify when the cost of fixing it is so low.

How to fix it

Confirm the page actually has a <title> element inside the <head>; if it is missing entirely, add one.
Make sure the title is not empty or whitespace-only, because a blank <title></title> fails just as a missing one does.
Write a title that uniquely describes this specific page, front-loading the distinctive part (the page subject) before the site name.
Keep each page's title unique across the site so tabs, bookmarks, and history entries are distinguishable; avoid repeating a generic title like "Home" everywhere.
In a framework or templating setup, set the title per route or page rather than hardcoding one shared value, then re-scan to confirm the title is present and non-empty.

Before

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

After

<head>
  <meta charset="utf-8">
  <title>Pricing &amp; Plans — AccessKnight</title>
</head>

How AccessKnight detects this

AccessKnight parses your rendered HTML and looks for a single <title> element in the document. It flags the page when there is no <title> at all, or when a <title> exists but its text content is empty or contains only whitespace after trimming. This is a one-per-page check rather than a per-element scan, so adding one descriptive, non-empty title resolves the issue for the whole document.

Frequently asked questions

Is a missing page title a Level A or AA issue?

It fails WCAG 2.1 Success Criterion 2.4.2 Titled Pages, which is Level A, the minimum conformance tier. AccessKnight treats it as serious severity because the title is the first thing a screen reader announces and the primary way users identify and switch between pages.

Does an empty <title></title> count as having a title?

No. An element that exists but contains no text, or only whitespace, fails this rule exactly like a missing one. The check requires non-empty, meaningful title text, so a blank or placeholder title does not pass.

What makes a good page title?

Make it unique to the page and front-load the distinctive information. A common, effective pattern is "Page Subject — Site Name", for example "Pricing — AccessKnight". Avoid repeating the same generic title (like "Home" or your brand name alone) across every page, since users need to tell pages apart.

Is the page title the same as the h1 heading?

They serve related but different roles. The <title> lives in the head and labels the page in tabs, bookmarks, history, and search results, and it is what a screen reader announces on load. The h1 is visible on the page and names its main content. They can be similar but are not required to be identical, and both should be present.