Plan and execute structured accessibility testing with NVDA, JAWS, VoiceOver, and TalkBack. Build AT test plans, write test scripts, and interpret assistive technology behavior for development teams.
The Assistive Technology Testing Consultant is an AI assistant for accessibility professionals, QA engineers, and development teams who need to plan, execute, and interpret testing with real assistive technologies. Automated accessibility testing tools catch an estimated 30–40% of accessibility issues — the remainder require manual testing, including testing with actual screen readers, voice control software, switch access devices, and zoom tools. This assistant bridges the gap between knowing testing is needed and knowing how to do it effectively.
The assistant helps you build comprehensive AT test plans that specify which assistive technologies to test, which browser-AT combinations reflect your user base, which test scenarios to cover, and how to prioritize test coverage given limited time and resources. It writes detailed test scripts — step-by-step procedures that tell a tester exactly what to do and what to listen for or observe at each step — for NVDA, JAWS, VoiceOver on macOS, VoiceOver on iOS, TalkBack on Android, and Windows Narrator.
When a tester encounters unexpected or confusing AT behavior during testing, this assistant helps interpret what is happening and why. It explains common screen reader modes (browse mode, forms mode, application mode), how mode switching affects keyboard behavior, and how to distinguish between a bug in the interface and a quirk of the AT being tested. It helps testers write clear, reproducible bug reports that developers can act on.
This assistant is valuable for QA teams new to accessibility testing, organizations building their first AT testing program, and accessibility specialists who need to document testing procedures for a broader team. It also covers automated testing tool integration — how to use axe, Lighthouse, IBM Equal Access Checker, and ARC Toolkit as the first layer of a testing process, and what to test manually afterward.
Expected outputs include AT test plans, step-by-step test scripts for specific components and user flows, bug report templates, AT command reference summaries, and testing process documentation.
Sign in with Google to access expert-crafted prompts. New users get 10 free credits.
Sign in to unlock