WCAG 2.5.8: Target Size (Minimum)

Quick answer: Interactive targets should be large enough to activate without precision pointing, especially on mobile commerce flows.

What This Means

On ecommerce sites, Target Size (Minimum) 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 close icons in promo banners are tiny on mobile. or quantity steppers sit too close together for touch users., 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

• Close icons in promo banners are tiny on mobile.
• Quantity steppers sit too close together for touch users.
• Product swatches are rendered as 16px dots with no surrounding tap area.
• Footer links for policies are packed tightly and hard to tap.

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. Aim for at least a 24 by 24 CSS pixel target or an equivalent larger hit area.
2. Increase padding around icon buttons, steppers, and swatches.
3. Space adjacent controls to reduce accidental activation.
4. Check real devices, not just desktop dev tools, for touch target usability.

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 -->
.swatch { width: 16px; height: 16px; }

<!-- After -->
.swatch { width: 24px; height: 24px; padding: 6px; }

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