A large-looking icon may have a tiny hit area, while a small icon inside a padded button can be easy to activate. Before making the whole interface visually larger, ask the supplier to show the actual pointer target boxes and nearby controls. Typography size and activation size are different decisions.
Who should use this acceptance brief
Mobile-first service and product websites. Use this as a scoped commissioning task for a website supplier. Where system evidence is required, a teaching file is not a substitute.
Source-bound platform fact
WCAG2.2 target-size minimum describes24by24CSS-pixel targets with specific exceptions, including spacing and inline links. A size-only check is not a complete conformance test. W3C: target size minimum · Checked 16 October 2026.
Filled teaching example
Synthetic example, not a client case. Inputs, expected decisions and counterexamples follow; no live platform integration is claimed.
On narrow screens, scroll to read the complete table.
| Input / case | Check basis | Expected decision |
|---|---|---|
| rectangle24×24CSSpx | size-only branch | meets this model |
| icon16px inside44×44button | actual button area | meets this model |
| rectangle20×20 | spacing not measured | review exceptions, not automatic fail |
Run the acceptance exercise
- Inspect the actual clickable element at supported mobile widths.
- Record its CSS-pixel box and any adjacent targets; distinguish visual artwork from the hit area.
- For undersized targets, document applicable spacing or other exceptions, then test real pointer use.
Interpret the result and retain evidence
The checker returns either size-met or review-exceptions; it never turns an undersized box into an automatic WCAG failure. Its measurements assume an axis-aligned rectangular target without clipped corners. Keep a screenshot and target-box record for one tightly packed toolbar and one isolated control to expose the difference.
Limits before implementation
Excludes complete exception evaluation, rounded shapes, keyboard focus and an accessibility certification. Do not alter existing page layouts merely to satisfy this offline fixture.
Replay the finite example
Save both files in one folder and run with Node22.13 or newer. These finite checks are not a live service or certification. Filled inputs and expected outputs · Inspectable functions
node decision-check.mjs mobile-tap-target-separation.json