Skip to main content

Test for Accessibility

Testing for accessibility means evaluating digital products and experiences to ensure that people with disabilities can perceive, operate, understand, and interact with them. This includes both manual and automated evaluations, ideally conducted by or with disabled users.

Role in the ENABLE Model​

This is the fifth step in the ENABLE model of pre-launch care. It ensures that accessibility isn't just intended in design or assumed in development -- it is verified. Without testing, undetected barriers remain, undermining equity.

Why Testing Matters​

Even with good intentions and inclusive designs, accessibility bugs frequently slip through. Testing catches these issues early -- before they reach users and require burdensome compensations. Skipping testing often results in preventable harm, loss of trust, and legal risk.

Examples​

  • Use screen readers (e.g., NVDA, VoiceOver) to navigate your site
  • Conduct keyboard-only testing to ensure navigation without a mouse
  • Run automated accessibility audits (e.g., axe, Lighthouse)
  • Perform user testing with people with disabilities

Care Sounds Like​

“We must perform user studies to test how well our speech recognition AI works for people who stutter.”
“We tested the signup form with a screen reader before shipping it.”
“We included blind and motor-impaired testers in our usability test.”

Neglect Sounds Like​

“It looks fine, so we assumed it works.”
“We didn't have time for a full accessibility audit.”
“We'll fix any issues after launch if someone complains.”

Real-world Scenario​

Larry was locked out of his bank account during a fraud prevention call because the automated phone system couldn't understand his stutter. It's likely that no pre-launch accessibility testing had been conducted with people who stutter. A simple real-world test with such a user would have revealed this failure -- and potentially prevented the barrier entirely.

Manifestations​

  • Fable allows product teams to hire disabled testers to run usability sessions before shipping new features, directly integrating disabled user feedback into the pre-launch phase.
  • Aspiritech contracts autistic QA teams to find a11y bugs before shipping, showcasing proactive, expert-led accessibility testing.