WCAG 2.2 Target Size: What Teams Should Test
A small icon can create a large usability problem
Imagine a customer using a narrow screen to review a financial application. The edit and delete icons sit side by side in every row. A slight movement triggers the wrong action. That experience is exactly why target size belongs in a design review and in the evidence collected during an accessibility audit.
WCAG 2.2 offers a measurable starting point, but it is easy to misstate the rule. The requirement applies to the area that responds to a pointer, not just the visible graphic.
Understand the Level AA baseline
Success Criterion 2.5.8, Target Size (Minimum), generally calls for a pointer target that can contain a 24 by 24 CSS pixel square. A smaller target may still meet the criterion if it has the specified spacing or another exception applies. The [W3C explanation] describes the exact geometry.
This is an important distinction for decision makers reviewing a report. A 16-pixel icon inside a generous button may be acceptable. A button that looks generous but only responds when the icon itself is pressed may not be.
Spacing is a measured alternative
The spacing exception is not a blanket approval for tiny controls. Around each undersized target, picture a 24 CSS pixel diameter circle centered on its bounding box. That circle must not intersect another target or another undersized target’s circle. Dense controls therefore need closer examination than an isolated icon.
Get IAAP Audit’s stories in your inbox
Join Medium for free to get updates from this writer.
Other defined exceptions include an equivalent control on the same page, inline links constrained by text, unmodified browser controls, and presentations whose compact form is essential. Each claimed exception should have a reason tied to the actual interface.
Separate the stronger aspiration from the requirement
The 44 by 44 CSS pixel Target Size (Enhanced) criterion is Level AAA. It can be a useful design aim for important actions, but it should not appear in a Level AA report as though it were the AA minimum.
Meeting the AA spacing exception also does not mean the target will feel easy for every person to use. Teams can choose more comfortable targets where space permits, especially on high-consequence journeys.
Ask the auditor for the shipped geometry
A useful finding identifies the page, viewport, target, clickable dimensions, nearby controls, exception analysis, and user consequence. The remediation note should explain whether to enlarge the hit area, increase spacing, or change a shared component. Retesting should happen after the change is published, including responsive states.
That evidence makes target size actionable for design, engineering, QA, and compliance teams. It also avoids turning a thoughtful accessibility requirement into a generic count of small icons.
Read the original guide on IAAP Audit: https://iaapaudit.com/blog/wcag-2-2-target-size-design-audit-guide
