skills.rest
civictechdc
civictechdcOFFICIAL
Explore all skills by this author →
WebsiteGitHub

screen-reader-testing

Tests screen-reader accessibility in web apps across major platforms and browsers using VoiceOver, NVDA, JAWS, TalkBack checklists.

1|Updated Jul 24, 2025
Search Tags:#testing#accessibility#a11y#web#screen-reader#assistive-technology
One-click install
npx skills add https://github.com/civictechdc/votecatcher --skill screen-reader-testing-civictechdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/civictechdc/votecatcher/tree/main/frontend/.agent/skills/screen-reader-testing
Command: npx skills add https://github.com/civictechdc/votecatcher --skill screen-reader-testing-civictechdc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Screen-reader accessibility is often neglected in web apps, causing barriers for users who rely on assistive technologies.

Core Features & Use Cases

  • Provides a practical framework for validating SR compatibility across VoiceOver, NVDA, JAWS, and TalkBack.
  • Includes checklists for navigation, focus management, forms, dynamic content, and error handling.
  • Use Case: A QA engineer uses the guide to confirm SR support before a release.

Quick Start

Open the web app in a browser and run the SR test checklist to verify live region announcements, focus management, and form accessibility.

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 apps for screen reader accessibility?▼

To test screen reader accessibility, open your web app in a browser and run a test checklist to verify live region announcements, focus management, and form accessibility across your target platforms. This validates SR compatibility before release.

Does this screen reader testing approach support VoiceOver, NVDA, JAWS, and TalkBack?▼

Screen reader testing supports VoiceOver, NVDA, JAWS, and TalkBack across macOS, Windows, iOS, and Android. It provides a practical framework to validate compatibility for web apps and SPAs on all these major assistive technologies.

What navigation and focus management issues should I check during screen reader testing?▼

During screen reader testing, check navigation, focus management, forms, dynamic content, and error handling. The included checklists help identify and fix SR issues within your development workflow to ensure barriers are removed.

What is the best way to validate screen reader compatibility for single page applications?▼

The best way to validate screen reader compatibility for SPAs is to use a practical guide and test checklists focusing on dynamic content, live region announcements, and focus management to identify and fix SR issues.

Why does my screen reader fail to announce dynamic content updates in my web app?▼

Screen readers fail to announce dynamic content when live regions are improperly configured. Testing checklists help verify live region announcements, ensuring dynamic updates in web apps are correctly read by VoiceOver, NVDA, JAWS, and TalkBack.

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
kensauruskensaurus
8

accessibility-audit

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

Community
Advanced
esneiderbravoesneiderbravo
1

accessibility-standards

Audit UI accessibility for WCAG 2.2 AA compliance with automated and manual checks.

Community
Intermediate
wojonswojons
4

testing-accessibility

Test web applications for WCAG compliance using automated tools.

Community
Intermediate