- Content & schema
- 50tests fired in this category
- modules
- 8dedicated content & schema checks
- every scan
- 299+tests across all categories
Why it matters
A control that looks neat in a desktop layout can become a frustrating target on a phone.
How it works
FixWeb inventories visible links, buttons, form controls, button roles, and tabindex elements on representative phone pages. A target fails when either rendered dimension is below 24 CSS pixels and nearby spacing does not meet the documented exception.
Site impact
Small or crowded targets slow navigation and can cause accidental actions. This is a geometry check from a passive render, not a usability study or a claim about real tap error rates.
How to improve
Give interactive controls a 24 × 24 CSS-pixel hit area at minimum, or separate smaller controls with enough space. Use padding and an accessible name so the visible design does not need to grow.