2.5.8Target Size (Minimum)
Operable › 2.5 Input Modalities › WCAG 2.2
Overview
The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where spacing, equivalent, inline, user agent control, or essential exceptions apply.
Understanding
The W3C Web Accessibility Initiative (WAI) provides detailed guidance on understanding and implementing this criterion. The Understanding document covers the intent, benefits, and supporting techniques in depth.
Read Understanding 2.5.8 on W3C WAITechniques
W3C provides documented techniques for meeting this criterion. Each technique links to the full specification with code examples and test procedures.
How to Test
Measure all interactive targets — verify each is at least 24×24 CSS pixels (including padding).
For targets smaller than 24px, verify the surrounding offset area (spacing to adjacent targets) brings the total to 24px.
Use browser DevTools computed styles to confirm padding is included in the hit area.
Exceptions: inline text links, targets with an equivalent 24px+ control, user-agent controls, and essential targets.
Failing & Passing Examples
Fails this criterion
/* Icon close button 16×16px with only 4px gap to adjacent button;
total offset area < 24px — fails 2.5.8 */
.close-btn {
width: 16px;
height: 16px;
margin: 2px; /* total spacing only 4px — insufficient */
}Passes this criterion
/* Option A: size the target to at least 24×24px */
.close-btn {
width: 24px;
height: 24px;
}
/* Option B: keep small icon but add padding to reach 24px */
.close-btn {
width: 16px;
height: 16px;
padding: 4px; /* 16 + 4 + 4 = 24px total */
}How VPATify tests this
The 24×24px minimum (new in WCAG 2.2) is the Level AA floor; smaller targets must have at least 24px spacing around them so nearby targets cannot be accidentally tapped at the same time.
VPATify runs automated WCAG checks against every page you scan and flags violations against individual success criteria. Our deep scan combines axe-core, contrast analysis, and structural checks to catch criterion-level failures that single-tool scans miss. See the full testing methodology and features for what's covered at each level.
Run a deep scanWant deeper accessibility insights?
Scan your entire website and generate an official VPAT document — free, in minutes.
Scan Your Site — It's Free