WCAG 2.2 AA
A visitor who uses a screen reader tabs into your search box at 11 p.m. looking for a deadline that won't wait. Either the screen reader announces the results and moves focus to the first one, or it says nothing and leaves them guessing. That moment is what accessibility in search comes down to. Keyspider's search interface meets WCAG 2.2 Level AA in the current production release. Not 2.1 with a roadmap. 2.2, today.
How it works
Build to the criteria
The interface is built against the full WCAG 2.2 AA checklist: operable by keyboard, perceivable by screen readers, and usable by people with low vision, motor differences, or cognitive load.
Test every release
Automated checks run in the build pipeline on every release. Major releases add manual testing with screen readers, keyboard-only navigation, and high-contrast mode.
Hand your team the proof
Request the VPAT for your records. If your accessibility office finds an issue, you get a written remediation roadmap with dates within 30 days.
Use cases
Public universities
Most public institutions fall under the earlier Title II deadline. Building to 2.2 AA now means the search page clears the bar your auditors will use, with margin to spare.
State and local government
Search is usually the first thing a resident touches. Meeting 2.2 AA there removes the most-used page from your compliance risk.
Procurement review
Evaluators scan for a real standard and real evidence. A current 2.2 AA interface with a VPAT on request answers the question before they have to ask twice.
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