2.4.2 Page Titled

1. What is the goal of this criterion?

Browser tabs are as much a part of the web today as coffee is of open-plan offices – they’re open everywhere, but nobody knows what’s where anymore. People with disabilities have a particularly hard time: if you use a screen reader, you can’t just glance across your open tabs, and people with cognitive disabilities need clear orientation about where they are.

The goal of Success Criterion 2.4.2 is therefore clear: every page needs a meaningful title that immediately reveals what it’s about. Not just “Home” or “Page 1”, but descriptive titles that make it instantly clear to everyone: “I’m in the right place – or I’m not.”

2. What exactly does it require?

Every page must have a title that describes its topic or purpose. That sounds simple, but there’s more to it:

• The title must describe the content or purpose of the page – generic words like “Welcome” or “Info” aren’t enough.
• The title goes in the <title> element in the <head>, so browsers can show it in tabs, bookmarks and history, and screen readers announce it when the page loads.
• The title should make sense out of context and be as short as possible.

Recommended, but not explicitly required: the title also names the website the page belongs to and differs from the titles of other pages on the same site.

In single-page apps, where content changes without a full page load, the title should change with every new view.

A practical example: instead of “XYZ Bank”, the title should read “Account overview – XYZ Bank” or “Transfers – XYZ Bank”, so it’s clear which section you’re in.

3. Why does it matter for accessibility?

Imagine navigating an online shop with a screen reader and having several product pages open – but they’re all just called “Product details”. You have to listen to each page to find out whether you’re on the red jumper or the blue shoes. Or you have memory problems and lose track in a multi-step checkout because every page is simply called “Order”.

Descriptive page titles improve accessibility because they:

• let blind people tell “Red jumper XL – Product details” from “Blue trainers size 9 – Product details” without listening to everything,
• show people with cognitive disabilities or memory problems where they are in a process, with titles like “Delivery address – Step 2 of 4 – Checkout”,
• tell screen reader users first thing on page load: “You’re on the contact page” or “You’re on the search results for winter jackets”,
• make it easier for people with low vision who use high magnification to find their way between tabs and windows,
• help people with attention disorders find their way around complex applications such as online banking (“Account overview” vs. “Transfers”).

And: good titles help everyone find pages again in bookmarks, history and search results.

4. How to meet the criterion

The good news: good page titles aren’t rocket science – but they need a system and consistency. Here are some proven tips:

Structure and format:

• Use a consistent format such as “Page name – Section – Site name” (for example “Contact – About us – Example Ltd”).
• Show the current step in multi-step processes: “Payment – Step 3 of 4 – Online shop”.
• Keep titles short and put the most important part first. Browser tabs often show only the first few words, and search engines truncate long titles too.

Content quality:

• Describe specifically what’s on the page – not just what it belongs to.
• Use clear, understandable language without internal abbreviations.
• Give each page its own title wherever possible.

Technical implementation:

• Use exactly one <title> element in the <head>.
• In single-page apps, update the title with JavaScript on every view change: document.title = "Cart – Online shop";. Since screen readers don’t announce a changed title on their own, also move focus sensibly, for example to the new main heading.
• Make sure the page title and the main heading (H1) match or complement each other.
• Don’t forget dynamic pages such as search results (“Search results for ‘accessibility’”) or error pages (“Page not found (404)”).
• When a form has errors, reflect that in the title too, for example “Error: Contact form”.

Related criteria are Headings and Labels and Location, which shows where you are within a website.

5. Why this criterion matters for businesses

Success Criterion 2.4.2 shows once again that accessibility isn’t an end in itself – it brings tangible benefits.

1. Better usability: Clear page titles improve orientation for everyone. People find what they’re looking for faster and can find open tabs or bookmarks again more easily – especially in complex applications or online shops.

2. Visibility in search results: Accessibility isn’t a direct ranking factor. But the page title usually appears as the clickable headline in search results. A descriptive title helps people see whether a click is worth it – an indirect benefit.

3. Stronger brand perception: Consistent, well-thought-out page titles convey care and professionalism – even in the small details.

And finally: 2.4.2 is a Level A criterion and therefore part of WCAG 2.1 AA, which the harmonised standard EN 301 549 references. Under the European Accessibility Act (EAA), many consumer services such as online shops must meet these requirements; in Germany, the EAA is implemented by the Barrierefreiheitsstärkungsgesetz (BFSG), which has applied since 28 June 2025. This is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 2.4.2 Page Titled (Level A)

Web pages have titles that describe topic or purpose.

In short: every page needs a title that describes its topic or purpose.