skills.rest
duanbiao2000
duanbiao2000COMMUNITY
Explore all skills by this author →
WebsiteGitHub

screen-reader-testing

Test web app screen-reader compatibility using VoiceOver, NVDA, and JAWS.

3|1|Updated Feb 3, 2026
Search Tags:#accessibility#a11y#screen-reader#web-accessibility#assistive-technology
One-click install
npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill screen-reader-testing-duanbiao2000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/duanbiao2000/obsidianDoc26/tree/main/agents-main/plugins/accessibility-compliance/skills/screen-reader-testing
Command: npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill screen-reader-testing-duanbiao2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Screen-reader compatibility is often overlooked, leaving web content inaccessible to users who rely on assistive technology; this Skill provides a practical guide to verify perceivability and navigability for screen readers across platforms.

Core Features & Use Cases

  • Setup and validation guidance for VoiceOver, NVDA, JAWS, TalkBack, and Narrator.
  • Hands-on checklists for navigation, focus management, and dynamic content announcements.
  • Use cases include accessibility audits during development, pre-release QA, and regression testing for assistive technology support.

Quick Start

Open the target web page and perform the recommended screen reader checks to verify basic announcements.

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?▼

Screen reader testing verifies perceivability and navigability for assistive technology users by applying hands-on checklists for navigation, focus management, and dynamic content announcements across major platforms.

How do I set up JAWS and VoiceOver for accessibility audits?▼

You can configure JAWS and VoiceOver for accessibility audits using provided setup guidance, which covers environment configuration for VoiceOver, NVDA, JAWS, TalkBack, and Narrator across platforms.

What screen reader checks should I perform during pre-release QA?▼

During pre-release QA, perform screen reader checks for basic announcements, focus management, and dynamic content updates to verify perceivability and navigability for assistive technology users.

Does this screen reader testing cover TalkBack and Narrator?▼

Yes, screen reader testing covers TalkBack and Narrator alongside VoiceOver, NVDA, and JAWS, providing setup and validation guidance for each platform to verify web content accessibility.

Why does my dynamic web content fail screen reader announcements?▼

Dynamic web content fails screen reader announcements when focus management and ARIA live regions are improperly configured, which you can identify using hands-on screen reader testing checklists for dynamic updates.

Related Skills

Explore More Software Engineering Skills→
coreyjacoreyja
6

Frontend Accessibility

Ensure semantic HTML, ARIA attributes, keyboard navigation, and screen reader compatibility.

Community
Basic
hypeJunctionhypeJunction
1

accessibility-review

Audit UI components and layouts for WCAG 2.1 AA accessibility issues.

Community
Advanced
RepairYourTechRepairYourTech
6

accessibility-compliance

Audit web applications for WCAG 2.1/2.2 compliance with axe-core.

Community
Advanced
TMHSDigitalTMHSDigital
2

mobile-accessibility-testing

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

Community
Advanced