Keyboard & ARIA
Press Tab into most search pages, hit Enter, and listen. The screen reader says nothing. Results loaded, and nobody was told. That silence is where accessibility quietly fails. Keyspider's search works start to finish from the keyboard, and ARIA live regions announce what changed, so a person using a screen reader hears 'twelve results found' the moment the page updates, not after they've given up.
How it works
Operate from the keyboard
Tab moves through the controls in a sensible order. Arrow keys drive typeahead and facets. Enter selects. Nothing on the page depends on a hover or a click a keyboard can't produce.
Announce what changed
When results load, a filter applies, or an AI answer appears, an ARIA live region speaks it. The screen reader user hears the update instead of wondering whether anything happened.
Keep it that way in your build
The starter templates for the Drupal module and the API carry the roles, labels, and live regions already in place, so your team keeps the behavior as it customizes the look.
Use cases
Screen reader users
Someone who relies on a screen reader searches for a deadline and hears the result count and the first answer immediately, finishing the task in seconds instead of guessing in silence.
Motor-impairment accessibility
A visitor who can't use a mouse completes a full search, filters it, and opens an answer with the keyboard alone, the way they get around everything else.
Accessibility audits
Keyboard operation and live-region announcements are two of the first things an auditor checks. Having them built in means the search page passes instead of generating findings.
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