WCAG 2.2 success criterion 2.5.8, Target Size (Minimum), is a Level AA requirement: pointer targets are large enough.
Read the criterion in the W3C Recommendation, WCAG 2.2 (opens in a new tab).
How BearScan checks it
Pointer targets are large enough
Checked automatically: loads the page in a browser. Severity: medium. Small targets are hard to hit for users with tremor or limited dexterity and are a frequent complaint subject.
An approximation: Delegated to axe-core's target-size rule, which measures rendered boxes. The spacing alternative is not machine-checked and needs a manual pass.
How to fix it. Give interactive targets at least 24 by 24 CSS pixels, or provide equivalent spacing so that a 24-pixel circle centred on each target does not overlap another target.
All WCAG 2.2 criteria · Next: 3.1.1 Language of Page
Questions
Is WCAG 2.5.8 required by the ADA?
The ADA doesn't name a technical standard for businesses. 2.5.8 was added in WCAG 2.2, so it isn't part of WCAG 2.1 Level AA, the version the Justice Department's 2024 rule adopted for state and local governments. WCAG 2.2 has been the current W3C Recommendation since October 5, 2023.
Can an automated tool check WCAG 2.5.8?
Mostly. BearScan checks it automatically (loads the page in a browser). A clean result still isn't proof every page passes, only the pages scanned.
How do I fix a WCAG 2.5.8 failure?
Give interactive targets at least 24 by 24 CSS pixels, or provide equivalent spacing so that a 24-pixel circle centred on each target does not overlap another target.