Consistent Identification
Components that have the same functionality across pages (search, cart, "Add to wishlist", "Share") must be identified consistently — same accessible name, same icon, same role.
What it requires
WCAG 2.0 SC 3.2.4 sits alongside 3.2.3. If a "search" icon is labeled "Find" on one page and "Search" on another, screen-reader users who navigate by landmark or button list will be confused. The fix is to standardize the accessible-name string across the site.
Common failures: icon-only buttons with different aria-labels per template; "Share" button labeled "Share" on the product page and "Forward" on the blog post; cart button labeled differently in header vs cart drawer footer.
Common Shopify failure
Wishlist heart icon with aria-label="Save" on the product card and aria-label="Add to wishlist" on the product detail page. Cart button labeled "View cart" in header and "Open cart" in mobile nav.
How to fix it
AccessComply detects label-divergence across templates for visually-identical buttons and surfaces the inconsistencies. The fix agent can normalize them when the merchant approves.
Primary source: W3C — WCAG 2.0 Understanding 3.2.4