skills.rest
ArogyaReddy
ArogyaReddyCOMMUNITY
Explore all skills by this author →
GitHub

screen-reader-testing

Validate screen reader accessibility across VoiceOver, NVDA, JAWS, and TalkBack.

Updated Apr 19, 2026
Search Tags:#accessibility#a11y#usability#web-testing#screen-reader#aria#assistive-technology
One-click install
npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill screen-reader-testing-arogyareddy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/ArogyaReddy/https-github.com-wshobson-agents/tree/main/plugins/accessibility-compliance/skills/screen-reader-testing
Command: npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill screen-reader-testing-arogyareddy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications often fail screen reader accessibility checks, making content inaccessible to users relying on VoiceOver, NVDA, JAWS, TalkBack, or Narrator. This skill provides a structured guide to validate compatibility, debug ARIA implementations, and ensure assistive technology support across major screen readers.

Core Features & Use Cases

  • Practical, cross-platform SR testing guidance for macOS (VoiceOver), Windows (NVDA, JAWS), and Android (TalkBack).
  • Step-by-step workflows for evaluating navigation, forms, live regions, focus management, and dynamic content.
  • Use cases include QA verification, accessibility audits, and regression checks during UI changes.

Quick Start

Run the screen-reader-testing technique on your web app to verify keyboard navigation, element labeling, and live region updates across VoiceOver, NVDA, and JAWS.

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 validate keyboard navigation, ARIA implementations, and focus management across major tools like VoiceOver, NVDA, and JAWS using structured workflows and practical checklists.

What is the best way to validate ARIA live regions for accessibility audits?▼

The best way to validate ARIA live regions is to evaluate dynamic content updates and live-region behavior using step-by-step screen reader workflows to ensure dynamic changes are properly announced to assistive technologies.

Does this screen reader testing guidance cover Windows JAWS and Android TalkBack?▼

Yes, this screen reader testing guidance covers Windows JAWS and Android TalkBack, providing cross-platform evaluation for macOS VoiceOver, Windows NVDA and JAWS, and Android TalkBack.

How do I debug keyboard navigation and focus management issues in web apps?▼

You debug keyboard navigation and focus management issues by applying structured screen reader testing workflows to verify element labeling, focus order, and dynamic content interactions during QA verification.

When do I need to perform a screen reader regression check during UI changes?▼

You need a screen reader regression check during UI changes when verifying that updated dynamic content, forms, and live regions maintain assistive technology support and do not introduce new accessibility barriers.

Related Skills

Explore More Software Engineering Skills→
drgaciwdrgaciw

screen-reader-testing

Test web application accessibility with VoiceOver, NVDA, JAWS, and TalkBack.

Community
Intermediate
kensauruskensaurus
8

accessibility-audit

Identify and remediate accessibility issues for WCAG compliance in web applications.

Community
Advanced
VanhPokerVanhPoker

accessibility-expert

Identify and fix WCAG 2.1/2.2 accessibility violations in web interfaces.

Community
Advanced
mtsatryanmtsatryan
1

accessibility-auditor

Audit web applications for WCAG compliance using axe-core and Playwright.

Community
Advanced