WCAG 2.4.2 Page Titled: what it means and how to fix it
Short answer: Every page needs a unique, descriptive title in the <title> tag, which is the first thing a screen reader announces.
What it requires
Web pages must have titles that describe their topic or purpose.
Who it affects
Screen reader users, who hear the title first and use it to tell browser tabs apart, and people with cognitive disabilities.
How it shows up in ADA website claims
Missing or duplicate page titles rarely appear alone in a complaint, but they are routinely included in the list of automated findings.
How to check your site
Look at the browser tab for each page type (home, category, product, cart, checkout). Each should be distinct and meaningful, not "Home" or the store name everywhere.
How to fix it
<title>Men's waterproof hiking boots | Harbor & Pine</title>Put the specific topic first and the brand last. Single-page apps must update document.title on every route change.
Frequently asked questions
Does this help SEO too?
Yes. The title tag is also the headline search engines usually show, so a descriptive title helps both.
Should the checkout steps have different titles?
Yes. "Shipping - Checkout" and "Payment - Checkout" tell a screen reader user where they are.
Is the h1 the same as the title?
No. They can match, but the title element is separate and required.
Automated rules that test this (axe-core): document-title. Our scanner runs these checks.
Other commonly cited criteria
- 1.1.1 Non-text Content
- 1.2.2 Captions (Prerecorded)
- 1.3.1 Info and Relationships
- 1.4.3 Contrast (Minimum)
- 1.4.4 Resize Text
- 2.1.1 Keyboard
- 2.4.1 Bypass Blocks
- 2.4.4 Link Purpose (In Context)
- 2.4.7 Focus Visible
- 3.1.1 Language of Page
- 3.3.2 Labels or Instructions
- 4.1.2 Name, Role, Value
Read the official WCAG 2.1 specification at W3C.
Proof of Access provides technical accessibility assessments. We are not a law firm and nothing on this page is legal advice. If you have received a demand letter or a lawsuit, talk to an attorney.