Target Size (Minimum)
Pointer input targets — buttons, links, controls — must be at least 24×24 CSS pixels, with documented exceptions for inline links and equivalent alternatives.
What it requires
WCAG 2.2 introduced this criterion specifically for mobile and touch interfaces. The 24×24 CSS-pixel threshold prevents users with motor impairments or imprecise touch input from missing controls.
Exceptions: inline text links inside a paragraph, controls that have an equivalent larger target elsewhere on the page, controls in user-customized layouts.
Common Shopify failure
Mobile-nav hamburger and cart icons rendered at 16×16. Quantity steppers (+/-) on cart drawer at 18×18. Cookie banner close button at 14×14.
How to fix it
Increase tap-target padding so the hit area is ≥24×24 even when the visible icon is smaller. AccessComply's TouchTargetAgent rewrites theme padding rules.
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.8 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.8 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.2 Understanding 2.5.8