WCAG 2.4.7: Focus Visible

Quick answer: Keyboard users need a clear visible indicator showing which control is currently focused.

What This Means

On ecommerce sites, Focus Visible 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 theme css removes outlines from all buttons and links. or focus styles on dark buttons are too subtle to distinguish., 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

• Theme CSS removes outlines from all buttons and links.
• Focus styles on dark buttons are too subtle to distinguish.
• Custom radio cards show hover states but no keyboard focus state.
• Coupon inputs and search fields lose the browser default outline without replacement.

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.

1. Never remove outlines unless you replace them with a stronger focus treatment.
2. Use a consistent focus token with enough contrast on every background.
3. Apply focus styles to custom components, not just native links and inputs.
4. Review third-party apps because they often reset outline styles globally.

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 -->
*:focus { outline: none; }

<!-- After -->
*:focus-visible { outline: 3px solid #60a5fa; outline-offset: 2px; }

Check if your store passes WCAG 2.4.7 → Free ADA Compliance Scan