Label in Name
For UI components with labels that include text, the accessible name (the name announced by assistive technology) must contain the visible text.
What it requires
WCAG 2.5.3 prevents the "voice command mismatch" failure — a user telling Siri "click Add to Cart" must succeed because the button's accessible name contains "Add to Cart". A button labeled visually "Add to Cart" but with `aria-label="Buy this item"` fails because voice control cannot match.
The fix: the visible label text must appear at the start of the accessible name. `aria-label` should match or extend the visible text, not replace it.
Common Shopify failure
Theme button visible text "Add to Cart" but `aria-label="Add this item to your shopping bag"`. Voice-control users cannot trigger it by saying "Add to Cart".
How to fix it
Ensure the accessible name contains the visible label, preferably at the start, without removing necessary context. Review computed accessible names rather than editing `aria-label` in isolation.
Merchant QA checklist
- Scan the storefront page where this pattern appears: product pages, collection pages, cart drawer, customer-account pages, and any landing page built with theme sections.
- Confirm the issue is fixed in the rendered browser output, not only in the Liquid file. Shopify section settings, app blocks, and third-party scripts can reintroduce the same 2.5.3 failure after a theme edit.
- Re-test the affected component with keyboard navigation and a screen-reader accessibility tree before publishing the theme, especially when the fix changes markup or ARIA attributes.
How AccessComply handles it
AccessComply uses automated rules to check supported patterns in the pages reached during a scan. Some WCAG requirements need human judgment, assistive-technology testing, or access to third-party content and cannot be established by an automated scan. This criterion is generally treated as a pattern that may have a supported suggested fix. If the app can safely match the issue to supported source code, the merchant must review and approve the suggested change before anything is written, and the result is checked afterward. Otherwise the merchant should use the guidance above and independent hands-on testing. The label is not a guarantee of detection, a fix, WCAG conformance, or legal compliance.
Primary source: W3C — WCAG 2.1 Understanding 2.5.3