WCAG 2.5.3: Label in Name
Level AQuick answer: The accessible name of a control should contain the same words users see on screen so voice commands match.
What This Means
On ecommerce sites, Label in Name 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 visible button text says 'apply coupon' but aria-label says 'redeem code now'. or the search button shows 'search' while screen readers hear 'submit query'., 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
- Visible button text says 'Apply coupon' but aria-label says 'Redeem code now'.
- The search button shows 'Search' while screen readers hear 'Submit query'.
- Voice-control users cannot activate 'Track order' because the code names it 'Lookup'.
- Icon buttons pair visible text with unrelated hidden labels.
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.
- Keep visible label text inside the accessible name, even if you add extra detail.
- Avoid replacing visible wording with clever marketing copy in aria-label values.
- Check voice-control use cases on checkout and account actions.
- Prefer native text buttons over icon-plus-ARIA combinations when possible.
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 -->
<button aria-label="Redeem code now">Apply coupon</button>
<!-- After -->
<button aria-label="Apply coupon">Apply coupon</button>FAQ
What is WCAG 2.5.3?
The accessible name of a control should contain the same words users see on screen so voice commands match.
How does WCAG 2.5.3 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with visible button text says 'apply coupon' but aria-label says 'redeem code now'. and the search button shows 'search' while screen readers hear 'submit query'. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 2.5.3 violations?
Start by auditing the live storefront, then Keep visible label text inside the accessible name, even if you add extra detail.; Avoid replacing visible wording with clever marketing copy in aria-label values.; Check voice-control use cases on checkout and account actions.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 2.5.3 → Free ADA Compliance Scan