Target Size (Minimum Size for Clickable Elements, WCAG 2.2)
WCAG 2.2 success criterion 2.5.8 “Target Size (Minimum)”, at level AA, requires clickable or tappable elements to measure at least 24×24 CSS pixels, unless an exception applies, such as inline links in running text, sufficient spacing from neighbouring elements, an equivalent alternative or a legally mandated presentation. The aim is to let people with motor impairments, tremor or limited fine motor control, as well as touchscreen users, hit controls accurately. As an alternative to the minimum size, spacing is also sufficient if notional 24-pixel circles around each element do not overlap.
In practice
For agencies this mainly concerns buttons, icon links, form fields, checkboxes, pagination and mobile navigation elements – classic weak points are tiny social media icons in the footer or tightly packed basket symbols in online shops. Before launch, measure the actual click area (not just the visible icon) with browser dev tools or a WCAG 2.2 target size checker, and enlarge it with CSS padding where needed without changing the design visually. The state of the standard is worth a closer look: the version cited in the Official Journal of the EU, EN 301 549 V3.2.1 (2021-03), points to WCAG 2.1 – SC 2.5.8 only arrived with WCAG 2.2 and is not yet contained there. Final draft EN 301 549 V4.1.0 from June 2026 adopts WCAG 2.2 but is not yet harmonised; the ETSI voting procedure has been running since 25 June 2026. Target size is therefore not currently mandatory in law; as a quality benchmark, and with the coming version of the standard in view, it nevertheless belongs in every accessibility audit and every design system component. In mobile checkout flows the minimum size pays off twice over: fewer mis-taps mean fewer abandoned purchases.