WCAG 2.4.2 Page Titled

Success criterion 2.4.2 helps people know where they are without reading the whole page. The page title is the first thing a screen reader announces, it is the text on the browser tab and in bookmarks, and it helps people with cognitive disabilities and anyone with many tabs open. It is level A and part of EN 301 549 (clause 9.2.4.2).

What the criterion requires

Web pages have titles that describe topic or purpose.

In HTML this means a non-empty <title> element. W3C guidance adds:

• the title should identify the page's content so users can tell pages apart;
• in single-page applications the title should be updated when the view changes;
• matching the title to the link text or main heading that led to the page helps orientation.

A good practice (not a strict requirement) is to put the most specific information first: "Blue linen shirt – Men's shirts – Shop name", not "Shop name – Shop name – Shirt".

Typical failures on an online shop

• every page uses the same title, just the shop name;
• product pages titled with internal codes ("SKU 4471-B");
• search result pages with no query in the title;
• checkout steps or account pages in a single-page app that keep the title of the first view;
• a missing or empty <title> on landing pages built with a page builder;
• error pages (404, "out of stock") with a title that says nothing about the error.

How to check it

Automated: our checker reports pages without a <title> or with an empty one (document title rule). Whether a title is descriptive is a human judgement, so that part needs a manual check.

By hand: open the main page types — home, category, product, search, cart, each checkout step, account, 404 — and read the browser tab. Ask: would I know which page this is if it were the only thing I saw? Do two different pages have the same title? In a single-page checkout, check that the title changes with each step.

How to fix it

• Use a title template: {page or product name} – {section} – {shop name}.
• Include the search term and page number on search and paginated category pages.
• Give error and confirmation pages titles such as "Page not found – Shop name" or "Order confirmed – Shop name".
• In SPAs, set document.title on every route change.
• Most platforms (Shopify, WooCommerce, PrestaShop) let you set SEO titles; descriptive titles help search engines too.

Related criteria

• 2.4.6 Headings and Labels — headings must describe the content.
• 2.4.4 Link Purpose (In Context) — link text should tell where the link leads.
• Run a free check to see whether your pages have titles.

Frequently asked questions

What does WCAG 2.4.2 require?

Every web page must have a title that describes its topic or purpose. In HTML that is the title element in the head of the page.

Why does an accessibility checker say the title failed?

Usually because the page has no title element or it is empty. Automated tools can only detect that; they cannot judge whether an existing title is descriptive.

Do titles have to be unique?

WCAG asks for descriptive titles, and W3C guidance says titles should identify the page and help users tell pages apart. In practice, identical titles on every page make that impossible, so give each page its own.

What about single-page apps and checkout steps?

Update the title when the view changes, for example "Shipping – Checkout – Shop name", so it always reflects the current content.