1. Identify controls that need attention
List compact controls across the templates: menu buttons, close icons, pagination, search actions, and controls repeated on cards. Include states that appear after interaction, such as an expanded menu. Prioritize places where selecting the wrong neighbor would interrupt work or trigger a consequential action.
Record the route, component name, state, and intended action for each example. Keep a screenshot or other permitted reference with the review record when useful. Do not count a quick look at the homepage as coverage of every dialog, category page, or mobile variation.
2. Measure the interactive area
Inspect the area that actually responds to the pointer, rather than measuring only the visible artwork. Keep the measurement unit and environment in the record. A large decorative icon can still be attached to an unexpectedly small control, while padding may make a small-looking symbol easier to activate.
W3C’s explanation of WCAG 2.2 criterion 2.5.8, Level AA, specifies a 24 by 24 CSS-pixel minimum with exceptions. Its size interpretation requires an axis-aligned square of that size to fit within the target; a bounding-box measurement alone can mislead for some shapes.
Sources: [1]
3. Assess an exception precisely
The stated exceptions concern qualifying spacing, an equivalent control on the same page, inline content, unmodified browser controls, or essential presentation. For spacing, center a 24 CSS-pixel-diameter circle on each undersized target’s bounding box; it must not intersect another target or another undersized target’s circle.
Record which exception applies and the evidence supporting it. Do not use “mobile,” “icon,” or “looks fine” as an exception label. If the case is unclear, flag it for an accessibility specialist and consider a simpler layout change. A narrow exception should not become permission to make the rest of the interface difficult to use.
Sources: [1]
4. Review the controls in their real layout
Check the supported desktop and mobile arrangements, including menus that wrap, card rows that stack, and labels that become longer. Verify that an enlarged interactive area does not cover a neighboring control. Use a controlled test environment for actions that would submit data or change an account.
Inspect keyboard access and visible focus as separate checks alongside pointer operation. They answer different questions and should have separate results in the review record. If you only inspected source dimensions, state that scope plainly rather than reporting that touch or keyboard behavior has been tested on devices.
5. Record corrections and recheck affected components
For each issue, name the component change, the routes that use it, and the conditions that need another check. Shared controls deserve broader sample coverage than a one-off element. Revisit the neighboring controls after an adjustment, because increasing one area may create a new overlap.
Record the environment, result, and unresolved question after the change is checked. Avoid turning a single criterion review into a claim of complete WCAG conformance or an accessibility certification. Keep the record connected to the design system so future compact variants do not silently reintroduce the same problem.
Your quick checklist
- Small controls and their states are inventoried.
- Measurements concern the actual interactive area.
- Any claimed exception has specific evidence.
- Relevant layouts and input methods have separate check results.
- Shared component changes receive a targeted recheck.
Sources & scope
W3C supports the stated criterion, measurement interpretation, and exceptions. The component inventory and review record are ATN editorial guidance. This article is not an accessibility certification and does not claim device or visual testing of ATN.
- W3C: Understanding Target Size (Minimum) (opens in a new tab)Source checked October 9, 2026
Published October 10, 2026. No affiliate links or paid placements in this guide.
