MR
Mayur Rathi
@mayurrathi
⭐ 40.7k GitHub stars

Screen Reader Testing

Screen Reader Testing is an code AI skill with a core value of Test web applications with screen readers including VoiceOver, NVDA, and JAWS. It helps developers solve real-world problems in the code domain, boosting efficiency, automating repetitive tasks, and optimizing workflows.

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology supp...

Last verified on: 2026-07-07

Quick Facts

Category code
Works With Claude
Source sickn33/antigravity-awesome-skills
Stars ⭐ 40.7k
Last Verified 2026-07-07
Risk Level Low
mkdir -p ./skills/screen-reader-testing && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/screen-reader-testing/SKILL.md -o ./skills/screen-reader-testing/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# Screen Reader Testing


Practical guide to testing web applications with screen readers for comprehensive accessibility validation.


Use this skill when


- Validating screen reader compatibility

- Testing ARIA implementations

- Debugging assistive technology issues

- Verifying form accessibility

- Testing dynamic content announcements

- Ensuring navigation accessibility


Do not use this skill when


- The task is unrelated to screen reader testing

- You need a different domain or tool outside this scope


Instructions


- Clarify goals, constraints, and required inputs.

- Apply relevant best practices and validate outcomes.

- Provide actionable steps and verification.

- If detailed examples are required, open `resources/implementation-playbook.md`.


Resources


- `resources/implementation-playbook.md` for detailed patterns and examples.

🎯 Best For

  • Debugging engineers
  • QA teams
  • QA engineers
  • Developers writing unit tests
  • Claude users

💡 Use Cases

  • Tracing runtime errors in production logs
  • Identifying memory leaks
  • Generating test cases for edge conditions
  • Writing integration test suites

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Screen Reader Testing to Your Work

    Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.

  4. 4

    Review and Refine

    Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.

❓ Frequently Asked Questions

Can this debug production issues?

Yes, but always ensure you have proper logging and monitoring in place first.

Does this generate test mocks?

Many testing skills include mock generation. Check the install command and skill content for details.

Is Screen Reader Testing compatible with Cursor and VS Code?

Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.

Do I need specific dependencies for Screen Reader Testing?

Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.

How do I install Screen Reader Testing?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/screen-reader-testing/SKILL.md, ready to use.

⚠️ Common Mistakes to Avoid

Debugging without context

Always provide the full error stack and surrounding code context for accurate debugging.

Not testing edge cases

AI tends to generate happy-path tests. Manually review for boundary conditions.

Skipping validation

Always test AI-generated code changes, even for simple refactors.

Missing dependency updates

Check if the skill requires updated dependencies or new packages.

🔗 Related Skills