24px Touch Targets
A facet checkbox the size of a grain of rice is fine until you're on a bus, on a phone, with a hand that doesn't hold perfectly still. Then every mis-tap is a small failure. WCAG 2.2 added a rule for exactly this: tap targets have to be at least 24 by 24 CSS pixels. Keyspider's search controls meet it, so filters, tabs, pagination, and result links are big enough to hit the first time.
How it works
Size every control
Each tappable element in the search interface is drawn to meet the 24-pixel minimum, including the small ones that usually get overlooked like facet toggles and page numbers.
Space them apart
Targets get enough room between them that a slightly off tap hits nothing instead of the control next door. Size and spacing together are what make a page usable one-handed.
Hold the line in your theme
The starter templates carry the sizing, so when your team restyles the search page the targets stay large enough instead of shrinking to fit a tighter design.
Use cases
Mobile-first audiences
Residents and students search on phones far more than on desktops. Proper target sizes mean they filter and tap results without the frustration of repeated mis-taps.
Motor and dexterity differences
A visitor with a tremor or limited fine motor control can operate the search page reliably, because the controls give them room to land the tap.
WCAG 2.2 conformance
Target size is a criterion many sites miss because it's new. Meeting it on the search page removes one of the easiest findings for an auditor to flag.
Ready to give your users better answers?
AI Search, AI Assistant, and Workplace Search. Deployed in days, not months. See it live on your own content.
No credit card required · Live in 2 weeks · Cancel anytime