Assistive Technology Testing

Description

Usability testing with disabled participants using their own screen readers, switch access, magnification or voice control to find barriers automated checkers miss.

Assistive technology testing evaluates a product as experienced through NVDA, JAWS, VoiceOver, TalkBack, switch devices, screen magnifiers, voice control and alternative keyboards. Automated tools catch roughly a third of accessibility issues at best; the remainder concern focus order, meaningful announcements, live region behaviour, gesture alternatives and cognitive load that only emerge when an experienced AT user attempts real tasks. Rigour comes from testing with habitual AT users on their own configurations (not sighted testers switching a screen reader on), from covering the browser and AT combinations your audience actually uses, and from separating code-level defects from interaction-level usability problems. Sessions record task success, time, and the specific announcement or interaction that failed, so engineers can reproduce each issue.

Attributes

Loss type
Active
Effort
Days

Steps

  1. Identify the AT and browser combinations your users rely on (for example JAWS with Chrome, NVDA with Firefox, VoiceOver with Safari on iOS) from analytics, support data or WebAIM survey benchmarks.
  2. Run an automated scan and an expert manual audit first so participant time is spent on issues tools cannot find.
  3. Recruit 5-8 experienced AT users per major technology, testing remotely on their own devices and settings where possible.
  4. Give realistic end-to-end tasks and ask participants to think aloud, capturing screen-reader speech output and screen recording.
  5. Log each failure with the AT, browser, element, what was announced or required, and whether the participant recovered.
  6. Rate severity by task blocking versus friction, map issues to WCAG success criteria, and retest fixes with the same AT combination.

Sources

  • ISO Standard on Ergonomics
  • Web Content Accessibility Guidelines (WCAG) 2.2 (W3C)
  • Inclusive Design Patterns (Heydon Pickering)

Also known as

  • Screen reader testing
  • AT usability testing
  • Accessibility usability testing

Categories

  • User Research
  • Usability & Evaluation