disability-testing

Simulates and tests digital products for accessibility using disability-specific profiles.

Updated May 19, 2026
One-click install
npx skills add https://github.com/lord-vinayak/orive-reqcap --skill disability-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disability-testing
Source: https://github.com/lord-vinayak/orive-reqcap/tree/main/.claude/skills/audit/disability-testing_
Command: npx skills add https://github.com/lord-vinayak/orive-reqcap --skill disability-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires NVDA, JAWS, VoiceOver, TalkBack, Axe DevTools, Stark, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps identify and address accessibility issues in digital products by simulating and testing them through disability-specific profiles.

Core Features & Use Cases

  • Disability-Specific Testing: Simulate various disabilities such as low vision, motor impairments, and cognitive disabilities to test product accessibility.
  • Simulation Tools: Offers tools for screen reader simulation, low vision simulation, and motor control simulation.
  • Testing Methodology: Provides a structured approach to testing with real disabled users, simulation techniques, and actionable findings.
  • Recruitment of Disabled Testers: Offers guidance on finding and compensating disabled testers for usability studies.
  • Testing Priority Matrix: Helps prioritize testing based on user base and product type.
  • Output Template: Provides a structured template for documenting testing results.

Quick Start

Run the disability-testing skill to simulate low vision and perform a screen reader test on your website.

Frequently Asked Questions about disability-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I simulate low vision and motor impairments when testing website accessibility?

Simulate low vision and motor impairments by applying disability-specific profiles to your digital product, which allows you to identify accessibility barriers and prioritize fixes based on your user base.

What is the best way to test digital products with screen readers like NVDA and VoiceOver?

Screen reader testing is best executed through disability-specific simulation profiles that guide systematic accessibility evaluations, producing actionable findings using tools like NVDA, JAWS, VoiceOver, and TalkBack.

Can I use Axe DevTools and Stark for systematic disability simulation testing?

Yes, you can use Axe DevTools and Stark alongside screen readers to perform systematic disability simulation testing, generating structured results within a provided output template for usability studies.

How do I recruit and compensate disabled testers for usability studies?

Recruit disabled testers for usability studies by following structured guidance on finding participants and providing fair compensation, ensuring your accessibility testing reflects real user experiences within a priority matrix.

Does this accessibility testing approach work for mobile platforms using TalkBack?

Yes, this approach supports mobile platforms by utilizing TalkBack for screen reader simulation, enabling comprehensive disability-specific testing across both web and mobile digital products.

What are the limitations of disability simulation compared to testing real disabled users?

Disability simulation provides structured accessibility testing but has limitations compared to real disabled users, so a testing methodology combining simulation techniques with actual user recruitment yields the most actionable findings.