skills.rest
wshobson
wshobsonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

screen-reader-testing

Test web applications for accessibility compliance with VoiceOver, NVDA, and JAWS.

38.6k|4.1k|Updated Jul 24, 2025
Search Tags:#testing#accessibility#a11y#screen reader#voiceover#nvda#jaws
One-click install
npx skills add https://github.com/wshobson/agents --skill screen-reader-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/wshobson/agents/tree/main/plugins/accessibility-compliance/skills/screen-reader-testing
Command: npx skills add https://github.com/wshobson/agents --skill screen-reader-testing

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, NVDA, and JAWS.
  • Accessibility Validation: Offers checklists and common issue fixes for ARIA, forms, and dynamic content.
  • Use Case: After developing a new feature, use this Skill to test its compatibility with NVDA on Windows and VoiceOver on macOS to catch and fix accessibility bugs before release.

Quick Start

Use the screen-reader-testing skill to validate the accessibility of the current web page using NVDA on Windows.

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 screen readers like VoiceOver and NVDA?▼

To test web accessibility with screen readers, you navigate web applications using keyboard commands in VoiceOver, NVDA, or JAWS to validate ARIA implementations and ensure dynamic content is properly announced to visually impaired users.

What keyboard navigation commands do I use for screen reader testing on macOS and Windows?▼

Keyboard navigation commands for screen reader testing involve specific VoiceOver shortcuts on macOS and NVDA or JAWS commands on Windows to traverse web elements, switch between browse and focus modes, and verify form interactions.

How do I debug ARIA implementation issues caught during screen reader testing?▼

To debug ARIA implementation issues caught during screen reader testing, you use checklists to identify common problems in dynamic content and forms, applying fixes to ARIA roles, states, and properties until screen readers announce them correctly.

Does this screen reader testing guidance cover both macOS VoiceOver and Windows NVDA?▼

Yes, this screen reader testing guidance covers both macOS VoiceOver and Windows NVDA, along with JAWS, providing specific commands, validation techniques, and accessibility compliance checklists for each major assistive technology platform.

Why does my screen reader skip dynamic content on my web application?▼

Your screen reader skips dynamic content on your web application when ARIA live regions are missing or misconfigured, requiring you to validate screen reader modes and implement proper ARIA attributes so dynamic updates are announced correctly.

Related Skills

Explore More Software Engineering Skills→
SAPSAP
294

a11y-audit

Audit UI components for WCAG AA accessibility compliance.

Official
Advanced
MinhDuyDEVMinhDuyDEV

accessibility-audit

Audit web interfaces for WCAG compliance issues and remediation recommendations.

Community
Intermediate
TMHSDigitalTMHSDigital
2

mobile-accessibility-testing

Audit iOS and Android apps for WCAG violations and screen reader issues.

Community
Advanced
HouseofmvpsHouseofmvps
115

a11y

Detect and fix deterministic WCAG 2.2 A/AA accessibility violations in HTML files.

Community
Advanced