WCAG 2.4.2 Page Titled Explained in Plain English

2.4.2 Page Titled is the WCAG success criterion that says every web page needs a title that describes its topic or purpose. The page title is the text in the HTML title element. It is shown in browser tabs, bookmarks and search results, and it is the first thing a screen reader announces when a page loads. This guide explains WCAG 2.4.2 Page Titled in plain English, how to write good titles and how to test them.

The official wording: “Web pages have titles that describe topic or purpose.” (W3C, WCAG 2.2)

What Is 2.4.2 Page Titled?

2.4.2 Page Titled is a Level A requirement under the Operable principle, in the guideline “Navigable”. It has two parts: the page must have a title, and the title must describe the page. A title of “Home” on every page, or “Untitled document”, technically exists but tells people nothing.

Why 2.4.2 Page Titled Matters

A good title answers “Where am I?” before anything else on the page loads:

• Screen reader users hear the title first, so it confirms they reached the right page.
• People with cognitive or memory impairments use titles to keep track of where they are, especially with several tabs open.
• Everyone uses titles to find the right tab, bookmark or history entry.
• Search engines show the title as the clickable headline in results, so good titles also help with SEO.

Who Is Affected by 2.4.2 Page Titled

• People who are blind and use screen readers
• People with cognitive disabilities or short-term memory difficulties
• People with low vision who zoom in and can only see part of the screen
• People who keep many tabs open and switch between them

How to Meet 2.4.2 Page Titled

Give every page a title element

Every page needs one title element inside head (H25, providing a title using the title element). Content management systems and site builders usually create it from a “page title” or “SEO title” field, so fill those in for every page.

Make titles descriptive, with the specific part first

Write titles the way you would describe the page to someone: “Return policy”, “Search results for tents”, “Checkout: step 2 of 3”. The W3C technique G88, providing descriptive titles for web pages recommends this. A title that does not identify the contents of the page is failure F25.

Good habits:

• Put the page-specific words first and the site name last.
• Include useful state: “Search results for tents (24 results)”, “Error: payment declined”, “Step 2 of 3”.
• Keep it short enough to read in a tab, roughly 60 characters.
• Match the main heading of the page, so people know they are in the right place.

Update titles in single-page apps

In React, Vue and similar apps, the page content changes without loading a new HTML document, so the title stays the same unless you change it. Update document.title on every route change, or use your framework’s head manager. Frameworks such as Next.js set titles per route through their metadata features.

// After the route changes
document.title = 'Order history | Trailhead Outfitters';

Title frames and documents too

Each iframe should have a title attribute describing its content, which helps meet 4.1.2 Name, Role, Value. PDFs and other documents also need a title in their properties.

How to Test for 2.4.2 Page Titled

1. Check every template. Open the homepage, a category page, a product or article, search results, the cart, checkout steps, account pages and error pages.
2. Read the tab. Does the title describe the page? Would you know which tab to click if you had ten open?
3. Look for duplicates in a site crawl or in your search console’s page reports.
4. In apps, navigate between views and check the title changes each time.
5. Listen with a screen reader. The title should be announced first when the page loads.

Our SEO audit guide shows how to find missing and duplicate titles across a whole site.

Related Success Criteria

• 2.4.4 Link Purpose (In Context): links describe where they go.
• 2.4.6 Headings and Labels: headings describe their topic.
• 2.4.8 Location: people can tell where they are in a set of pages, at Level AAA.
• 4.1.2 Name, Role, Value: frames have accessible names.

Run a free WCAG scan to catch missing titles, then read your titles in context to make sure they describe each page.

Testing WCAG 2.4.2 With AccessBell

AccessBell's scanner runs axe-core, which includes 1 rule that catch code-level failures of this criterion. Automated checks help you spot issues quickly; a person still needs to review what they cannot judge.

• document-title: Ensure each HTML document contains a non-empty <title> element (details (opens in a new tab))

This criterion is included in: WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.

Run a free scan to spot issues on your own pages.

Example Fix

1. Add a title to every page. The title is the first thing a screen reader announces and what appears in browser tabs.
2. Make each title unique. Put the specific page topic first and the site name last.

<head>
  <title>Pricing - AccessBell</title>
</head>

Frequently Asked Questions

What level is WCAG 2.4.2 Page Titled?

Level A. It has been in WCAG since version 2.0.

Do page titles have to be unique under 2.4.2?

WCAG asks for titles that describe the topic or purpose of each page. In practice, two pages with different content need different titles, or the titles do not describe them. Unique titles are also best practice for search engines.

Should the site name come first or last in the title?

WCAG does not say, but putting the page-specific part first is more useful. Screen readers and browser tabs show the start of the title first, so people hear "Checkout: step 2 of 3" before "Trailhead Outfitters".

Can automated tools test 2.4.2 Page Titled?

Partly. Tools reliably flag pages with no title or an empty one. Whether a title actually describes the page needs a person to judge.

Can AccessBell test WCAG 2.4.2 automatically?

Yes. AccessBell runs 1 automated rule that can catch failures of this criterion, including in our WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker. A person still needs to check what automation cannot judge.

Sources

• W3C: Understanding 2.4.2 Page Titled (opens in a new tab)
• W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)

This page explains a technical standard and is not legal advice. See our disclaimer.