2.4.2 Page Titled (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 2.4.2 Page Titled (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Operable → 2.4.2 Page Titled
2.4.2 Page Titled (Level A)
What it requires: Every page has a <title> that describes its topic or purpose — this is often the very first thing a screen-reader user hears when a page loads or when switching between browser tabs.
Common failure: Every page on a site shares the same generic <title>Home</title> or the storefront platform’s default title, so all open tabs and all screen-reader page announcements sound identical.
Fix it: Give every page a unique, descriptive title following a consistent pattern (e.g., “Navy Canvas Backpack — Quietramp Store”), set programmatically per route rather than hardcoded once.
In 2.4 Navigable: ← 2.4.1 Bypass Blocks · 2.4.3 Focus Order →
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.