In this WCAG Fix It guide, we’re breaking down one of the simplest but most important accessibility requirements: making sure every page has a descriptive title.
It’s one short line in your code but without it, users can quickly become lost, especially when navigating with assistive technology, and fixing it is one of the fastest accessibility improvements you can make.
What Is WCAG 2.4.2?
WCAG 2.4.2 – Page Titled requires that web pages have titles that describe the topic or purpose of the page.
In simple terms: Every page must have a clear, meaningful <title> element.
The page title appears:
- In the browser tab
- In search engine results
- In bookmarks
- In screen reader announcements
If the title is missing, vague, or duplicated, the page fails this criterion.
What Is a Page Title?
A page title is defined in the <head> of your HTML:
<head>
<title>Accessibility Services | Recite Me</title>
</head>
This is not the same as your visible page heading (<h1>).
The <title> element is used by browsers and assistive technologies to identify the page.
Why Page Titles Matter
Screen reader users often navigate between open tabs or browser windows.
When switching tabs, the screen reader announces the page title.
If multiple pages are titled:
- “Home”
- “Page 1”
- “Untitled”
- “Document”
Navigation becomes confusing immediately.
Clear titles help users:
- Understand where they are
- Identify open tabs
- Navigate search results
- Bookmark content effectively
Without meaningful titles, context is lost.
The Human Impact of Missing or Vague Titles
Imagine opening several tabs from the same website.
Each tab says:
“Home – Company Name”
Even though one is:
- A product page
- A blog article
- A checkout page
- A contact form
Now imagine relying on screen reader announcements to distinguish them. You can’t.
Poor page titles create disorientation. Users should never have to guess what page they’re on.
Common WCAG 2.4.2 Failures
Here’s what we typically see when scanning websites:
- Missing <title> element
- Multiple pages using identical titles
- Titles that only say “Home” or “Welcome”
- Auto-generated titles like “Untitled Page”
- Titles that don’t match page content
- Titles that are overly long and truncated
All of these can fail WCAG 2.4.2.
How to Fix Missing or Poor Page Titles
Add a Descriptive <title> Element
If your page has no title:
<head>
<title></title>
</head>
Update it to something meaningful:
<head>
<title>Digital Accessibility Audit Services | Company Name</title>
</head>
The title should clearly describe the page purpose.
Make Titles Unique
Every page should have a distinct title.
Instead of:
- Home | Company Name
Use:
- Accessibility Audit Services | Company Name
- WCAG Compliance Guide | Company Name
- Contact Our Accessibility Team | Company Name
This improves clarity for users and search engines.
Keep Titles Clear and Concise
Best practice:
- 50–60 characters where possible
- Primary topic first
- Brand name last
For example:
“WCAG 2.4.2 Page Titled Explained | Accessibility Guide”
Avoid:
- Keyword stuffing
- Repeating brand name first on every page
- Vague phrases
If You’re Using a CMS
In platforms like WordPress, Shopify, Wix, or Squarespace:
- Use the page title field in page settings
- Use SEO plugins to customise title tags
- Ensure dynamic pages (like blogs or products) generate unique titles
Always check by:
Right-click → View Page Source → Locate <title>
How to Test WCAG 2.4.2
After updating page titles:
- Re-run your accessibility scan
- Open multiple tabs and check clarity
- Use a screen reader and switch between tabs
- Verify titles match page content
Ask:
- Does the title clearly describe this page?
- Would it make sense out of context?
- Is it unique?
If yes, you’ve fixed it.
Why WCAG 2.4.2 Matters Beyond Compliance
Clear page titles:
- Improve accessibility
- Improve SEO
- Improve user orientation
- Reduce confusion
- Improve bookmark usability
- Reduce legal risk
Titles are often the first thing users encounter.
If the title is unclear, the journey starts with confusion. One line of code makes a massive navigation and seo improvement.
WCAG 2.4.2 Quick Fix Checklist
To meet the compliance requirements of WCAG 2.4.2, follow this simple checklist:
- Every page includes a <title> element
- Titles clearly describe page purpose
- Titles are unique across the site
- Titles are concise and readable
- Titles match visible page content
- Updates re-tested after changes
WCAG 2.4.2 Page Titled FAQs
Looking for a quick recap? Here are answers to some of the most frequently asked questions on this topic:
WCAG 2.4.2 requires that each web page has a title that describes its topic or purpose.
No. The page title is defined in the tag in the head section of the HTML, while the H1 is visible on the page.</p>
Yes. If multiple pages use the same title and do not clearly describe their purpose, they may fail WCAG 2.4.2.
Yes. Clear, descriptive page titles improve search engine rankings and click-through rates while also supporting accessibility.