WCAG 3.2.4: Consistent Identification
Level AAQuick answer: Components that do the same thing should be identified in the same way across pages.
What This Means
On ecommerce sites, Consistent Identification 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 the cart icon is labeled 'bag' on pdps and 'checkout basket' elsewhere. or support links alternate between 'help', 'contact', and 'need assistance' for the same destination., 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
- The cart icon is labeled 'Bag' on PDPs and 'Checkout basket' elsewhere.
- Support links alternate between 'Help', 'Contact', and 'Need assistance' for the same destination.
- Wishlist uses a heart icon on one template and a bookmark label on another.
- Return links switch names between account and footer navigation.
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.
- Choose one label and icon pattern for recurring actions like cart, help, account, and wishlist.
- Carry the same naming into accessible names, headings, and visible labels.
- Update design-system docs so new templates inherit consistent language.
- Review A/B tests to ensure experiments do not fragment core navigation labels.
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 -->
<a aria-label="Checkout basket">Bag</a>
<!-- After -->
<a aria-label="Bag">Bag</a>FAQ
What is WCAG 3.2.4?
Components that do the same thing should be identified in the same way across pages.
How does WCAG 3.2.4 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with the cart icon is labeled 'bag' on pdps and 'checkout basket' elsewhere. and support links alternate between 'help', 'contact', and 'need assistance' for the same destination. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.2.4 violations?
Start by auditing the live storefront, then Choose one label and icon pattern for recurring actions like cart, help, account, and wishlist.; Carry the same naming into accessible names, headings, and visible labels.; Update design-system docs so new templates inherit consistent language.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.2.4 → Free ADA Compliance Scan