WCAG 2.4.2 — Page Titled

Missing Page Title

What is this issue?

A missing or inadequate page title occurs when the HTML <title> element is empty, absent, generic (e.g., "Untitled" or "Home"), or identical across multiple pages. WCAG Success Criterion 2.4.2 (Level A) requires that web pages have titles that describe their topic or purpose. The page title is the first piece of information announced by a screen reader when a page loads, and it appears in browser tabs, bookmarks, and search engine results.

Generic titles are nearly as problematic as missing ones. When every page of a site is titled "My Website" or "Home", users with multiple tabs open cannot distinguish between them. Screen reader users hear the same title announced on every page load, making it impossible to confirm they have navigated to the correct destination.

Single-page applications (SPAs) are particularly prone to this issue. Because the page does not fully reload during navigation, the document title often remains static unless the developer explicitly updates it via JavaScript on each route change. Many React, Vue, and Angular applications ship with the same title on every view because the title update was never implemented.

Impact on users

Screen reader users hear the page title as the first announcement when a page loads. If every page has the same title or no title at all, users cannot confirm they have reached the right page. They must explore the page content to figure out where they are, which adds significant time and cognitive load to every navigation action.

For users with cognitive disabilities, clear and descriptive page titles serve as orientation cues. A title like "Checkout -- Step 2 of 3 -- MyStore" tells the user exactly where they are in a process. A generic "MyStore" title provides no such guidance.

Page titles are also critical for SEO. The title tag is one of the strongest ranking signals for search engines, and it is the text displayed as the clickable link in search results. A missing or generic title directly reduces click-through rates and search visibility.

Code example

Before (non-compliant)

<!-- Missing title -->
<head>
  <meta charset="UTF-8">
  <!-- no <title> element -->
</head>

<!-- Generic title -->
<head>
  <title>My Website</title>
</head>

<!-- SPA that never updates title -->
<head>
  <title>App</title>
</head>

After (compliant)

<!-- Descriptive, unique title -->
<head>
  <title>Accessibility Audit Pricing -- Scrutia</title>
</head>

<!-- Pattern: Page Name -- Site Name -->
<head>
  <title>WCAG 2.1 Compliance Guide -- Scrutia Blog</title>
</head>

<!-- SPA: update title on route change -->
<script>
  // React: useEffect or react-helmet
  document.title = `${pageTitle} -- Scrutia`;
</script>

How Scrutia detects this issue

Scrutia checks the <title> element of every audited page. It flags pages with no title, empty titles, titles that match the site name exactly, and titles that are duplicated across multiple pages. The report lists each affected URL alongside its current title and a recommended descriptive replacement based on the page's main heading and content.

Check your site for this issue

Scrutia audits your site against WCAG criteria in minutes.

Free audit

Frequently Asked Questions

What makes a good page title?

A good page title is unique, concise (under 60 characters), and describes the page's specific content. The recommended format is "Page Topic -- Site Name". Put the specific content first so it is visible in narrow browser tabs.

How do I update titles in a single-page application?

Use your framework's routing system to update document.title on each route change. React has react-helmet or useEffect, Vue has vue-meta, and Angular has the Title service. Ensure every route sets a unique, descriptive title.

Should every page have a different title?

Yes. Each page should have a unique title that reflects its specific content. Duplicate titles across different pages confuse both users and search engines about the purpose of each page.

Does your site have this issue?

Scrutia scans your pages against WCAG success criteria and delivers actionable fixes. Results in 5 minutes.

Run a free audit