WCAG 2.4.2: Page Titled
Level AQuick answer: Every page needs a descriptive title so users know where they are in the store, support center, or checkout flow.
What This Means
On ecommerce sites, Page Titled usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like collection pages all use the same title like 'altorlab store'. or product pages omit the product name and variant in the title element., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Collection pages all use the same title like 'AltorLab Store'.
- Product pages omit the product name and variant in the title element.
- Checkout steps share one generic title across shipping, payment, and review.
- Search results do not include the search query in the browser title.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Write unique titles for PDPs, collections, articles, account pages, and checkout steps.
- Front-load the specific page topic, then add the brand name.
- Include query or state context when it helps orientation, such as search or order history.
- Audit template inheritance because duplicate titles often come from base layouts.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<title>Store</title>
<!-- After -->
<title>Canvas Tote — Black — AltorLab</title>FAQ
What is WCAG 2.4.2?
Every page needs a descriptive title so users know where they are in the store, support center, or checkout flow.
How does WCAG 2.4.2 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with collection pages all use the same title like 'altorlab store'. and product pages omit the product name and variant in the title element. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 2.4.2 violations?
Start by auditing the live storefront, then Write unique titles for PDPs, collections, articles, account pages, and checkout steps.; Front-load the specific page topic, then add the brand name.; Include query or state context when it helps orientation, such as search or order history.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 2.4.2 → Free ADA Compliance Scan