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
AccessComply detects mismatches between visible button text and the accessible name + rewrites aria-label to start with the visible text.
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 treats WCAG 2.5.3 as a rendered-storefront issue first. The scanner checks the live DOM and computed styles, maps the finding back to the Shopify theme file that produced it, then classifies the fix as a safe automatic fix. When automation is safe, the app writes the smallest theme-code change needed and keeps the original theme backup available. When merchant judgment is required, the issue is surfaced for manual review instead of pretending the page is fixed.
Primary source: W3C — WCAG 2.1 Understanding 2.5.3