screen-reader-scripting

Generate NVDA, JAWS, and VoiceOver test scripts with bug reporting templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complex challenge of testing and scripting for accessibility, ensuring screen readers like NVDA, JAWS, and VoiceOver provide accurate and accessible user experiences.

Core Features & Use Cases

  • Tailored Test Scripts: Provides scripts for NVDA, JAWS, and VoiceOver, detailing specific steps, expected announcements, and pass/fail criteria.
  • Component-Specific Guides: Delivers in-depth tests for components like accordions, comboboxes, and date pickers.
  • AT Quirks Documentation: Offers a reference to common screen reader quirks for accurate testing.
  • Bug Reporting Templates: Supplies a structured template for bug reporting and communication.
  • Use Case: Ideal for quality assurance teams, web developers, and accessibility professionals needing to create or validate screen reader scripts.

Quick Start

Use the screen-reader-scripting skill to generate a test script for an 'accordion' component on a web page.

Frequently Asked Questions about screen-reader-scripting

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

FAQPage Schema
How do I write test scripts for screen readers like NVDA and VoiceOver?

Screen reader test scripts are generated by detailing specific interaction steps, expected announcements, and pass/fail criteria for web components. This Skill automates creating those tailored scripts for NVDA, JAWS, and VoiceOver.

What is the best way to document accessibility testing for interactive web components?

Documenting accessibility testing involves using structured bug reporting templates and component-specific guides. This Skill supplies those templates alongside in-depth tests for components like accordions, comboboxes, and date pickers.

Does this screen reader scripting approach handle quirks for JAWS and NVDA?

Yes, handling screen reader quirks is supported through included reference documentation. The Skill offers a dedicated reference guide to common screen reader quirks to ensure accurate testing and feedback.

Can I use these test scripts to validate an accordion component on my web page?

Yes, you can validate an accordion component by generating a tailored test script. The Skill provides component-specific guides that detail the exact steps and expected announcements for testing accordions.

Why do I need structured pass/fail criteria for screen reader accessibility tests?

Structured pass/fail criteria are needed to ensure screen readers provide accurate and accessible user experiences. The generated test scripts detail specific steps and expected announcements to validate accessibility accurately.