skills.rest
EngineerWithAI
EngineerWithAIOFFICIAL
Explore all skills by this author →
GitHub

screen-reader-testing

Validate web application accessibility with VoiceOver, NVDA, and JAWS.

4|Updated Jan 10, 2026
Search Tags:#testing#accessibility#a11y#screen reader#web development#voiceover#nvda
One-click install
npx skills add https://github.com/EngineerWithAI/engineerwith-agents --skill screen-reader-testing-engineerwithai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/EngineerWithAI/engineerwith-agents/tree/main/plugins/accessibility-compliance/skills/screen-reader-testing
Command: npx skills add https://github.com/EngineerWithAI/engineerwith-agents --skill screen-reader-testing-engineerwithai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and testers ensure web applications are usable by people with visual impairments by testing them with common screen reader technologies.

Core Features & Use Cases

  • Screen Reader Simulation: Provides guidance and commands for using VoiceOver (macOS), NVDA (Windows), and JAWS (Windows).
  • Accessibility Testing: Offers checklists and common issues for validating ARIA implementations, form accessibility, and dynamic content announcements.
  • Use Case: After developing a new feature, use this Skill to test its compatibility with NVDA on Windows to identify and fix any accessibility barriers before release.

Quick Start

Test the current web page using NVDA on Windows by following the provided commands and checklist.

Frequently Asked Questions about screen-reader-testing

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

FAQPage Schema
How do I test web accessibility with NVDA and VoiceOver?▼

Test web accessibility with NVDA and VoiceOver by following provided keyboard commands and checklists to validate ARIA implementations, form accessibility, and dynamic content announcements across your web application.

What are common screen reader testing issues for dynamic web content?▼

Common screen reader testing issues for dynamic content involve missing or incorrect announcements. Validate ARIA implementations and live regions to ensure screen readers properly announce dynamic web content updates.

Can I use this to test form accessibility with JAWS?▼

Yes, you can test form accessibility with JAWS. It provides testing guidance for JAWS on Windows, focusing on keyboard navigation and validating ARIA implementations to identify and fix form accessibility barriers.

How do screen reader modes affect keyboard navigation testing?▼

Screen reader modes affect keyboard navigation testing by changing how keystrokes are interpreted. Understanding screen reader modes and keyboard navigation is required for effective debugging of common web accessibility issues.

When should I run screen reader testing during web development?▼

You should run screen reader testing during web development after developing a new feature. Testing compatibility with major screen readers helps identify and fix accessibility barriers before release.

Why does my ARIA implementation not announce correctly in screen readers?▼

ARIA implementations fail to announce correctly in screen readers due to common accessibility issues. Use screen reader testing checklists to debug ARIA roles, properties, and dynamic content announcements effectively.

Related Skills

Explore More Software Engineering Skills→
as4584as4584
2

screen-reader-testing

Test web accessibility with VoiceOver, NVDA, and JAWS checklists and scenarios.

Community
Intermediate
daniellelooodaniellelooo

accessibility-compliance

Implement WCAG 2.2 compliant interfaces with ARIA patterns and screen reader support.

Community
Advanced
RepairYourTechRepairYourTech
6

accessibility

Audit web accessibility against WCAG 2.1 guidelines and provide code examples.

Community
Intermediate
zinohomezinohome
1

accessibility-auditor

Audit web pages for WCAG 2.1 compliance and implement accessibility fixes.

Community
Advanced