Touch and Pointer

A touch target that is too small to hit reliably is inaccessible for users with motor impairments — and frustrating for everyone else on a touchscreen.

What the standard requires

WCAG 2.2 Success Criterion 2.5.8 (Target Size, Minimum) requires that touch targets are at least 24×24 CSS pixels, unless the element is inline in text, or adequate spacing surrounds it. This is the minimum. Apple’s Human Interface Guidelines and Google’s Material Design both recommend 44×44px as the target size for comfortable touch interaction. The 44px recommendation is not a WCAG requirement, but it is the industry standard for reason — smaller targets require more precision than many users can reliably provide.

Who this affects

Users with motor impairments, tremors, or limited dexterity have difficulty hitting small targets consistently. The same is true for users on large phones holding the device in one hand, users wearing gloves, and users on any device in a moving environment. Undersized targets create errors — triggering the wrong element — which is a usability failure that compounds for users with fewer alternatives.

Spacing counts

Target size and spacing are related. A 20×20px icon surrounded by 12px of padding on all sides creates an effective hit area of 44×44px. The CSS min-width, min-height, and padding properties can be used to increase the hit area without changing the visual size of the element. This means there is rarely a visual design reason to have undersized targets — the spacing is invisible.

Pointer gestures

Complex gestures — pinch, swipe, two-finger tap — require motor capability that not all users have. WCAG requires that all functionality operable by a path-based gesture (like a swipe) is also operable by a single pointer action. Provide tap or button alternatives for every swipe interaction.

Motor accessibility beyond touch targets

Touch target size is the most visible motor accessibility requirement, but motor impairment spans a wider range than pointer precision.

Tremors and involuntary movement affect accurate tapping and clicking. The implication for design: adequate target size (44px minimum), sufficient spacing between adjacent targets so a missed tap doesn’t activate the wrong element, and no interactions requiring a sustained held tap without a timer-override option.

One-handed use is both situational (carrying something, holding a rail) and permanent (limb difference, injury). Implications: primary actions should be reachable in the bottom half of the screen on mobile (within the natural thumb arc), and no critical gesture should require two hands or simultaneous inputs.

Alternative input devices — switch control, eye tracking, head pointer, mouth stick — each generate pointer events but with very different precision and speed characteristics. Switch control navigates by highlighting interactive elements sequentially; reducing the number of interactive elements and grouping related ones reduces the scanning burden significantly. Eye tracking requires larger targets and dwell-time confirmation rather than precise clicks.

These users are not edge cases in frequency — they are edge cases in design attention. The same target size, spacing, and navigation decisions that serve users with motor impairments measurably improve usability for everyone on a touchscreen.

The takeaway

Audit your interactive elements against a 44×44px target size as part of your design specification. Use padding to achieve the required size without changing the visual design. For gesture-based interactions, always provide a non-gesture alternative.