skills.rest
AI-Foundry-Core
AI-Foundry-CoreOFFICIAL
Explore all skills by this author →
GitHub

screen-reader-testing

Guide manual web accessibility testing with screen readers like VoiceOver and NVDA.

4|Updated Mar 3, 2026
Search Tags:#accessibility#a11y#aria#manual-testing#web-accessibility#assistive-technology#screen-reader-testing
One-click install
npx skills add https://github.com/AI-Foundry-Core/ril-agents --skill screen-reader-testing-ai-foundry-core
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/AI-Foundry-Core/ril-agents/tree/main/plugins/accessibility-compliance/skills/screen-reader-testing
Command: npx skills add https://github.com/AI-Foundry-Core/ril-agents --skill screen-reader-testing-ai-foundry-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams validate accessibility by guiding practical testing of web apps with screen readers (VoiceOver, NVDA, JAWS) to identify and fix accessibility issues.

Core Features & Use Cases

  • VoiceOver, NVDA, JAWS, TalkBack, and Narrator testing across desktop and mobile browsers.
  • ARIA and dynamic content validation, keyboard navigation checks, and focus management verifications.
  • Use Case: A developer checks a form with screen readers to ensure labels are announced and errors are read.

Quick Start

Run a screen-reader compatibility test on your web app by following the VoiceOver, NVDA, JAWS, TalkBack, and Narrator checklists.

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 a screen reader?▼

Screen reader testing validates web accessibility by guiding manual checks with VoiceOver, NVDA, JAWS, TalkBack, and Narrator across desktop and mobile browsers. It specifies setup guidance, checks, and example test scripts to follow.

How do I validate ARIA implementations and dynamic content changes for accessibility?▼

Validating ARIA implementations and dynamic content changes requires manual screen reader testing to verify dynamic updates are announced correctly. This ensures dynamic content changes are properly read by assistive technologies.

Does this screen reader testing approach work for both desktop and mobile browsers?▼

Yes, screen reader testing works across both desktop and mobile browsers. It includes checklists for desktop tools like VoiceOver, NVDA, and JAWS, alongside mobile tools like TalkBack and Narrator.

What's the best way to check form accessibility and keyboard navigation with screen readers?▼

Checking form accessibility and keyboard navigation involves using screen readers to ensure labels are announced and errors are read. This verifies focus management and keyboard navigation work in real-world app scenarios.

When do I need manual screen reader testing instead of automated checks?▼

Manual screen reader testing is needed to validate real-world app scenarios like ARIA implementations, dynamic content updates, and focus management that automated checks cannot fully verify.

Why does my screen reader not announce form errors correctly?▼

Screen readers may not announce form errors correctly if ARIA implementations and dynamic content changes are not properly configured. Manual testing with VoiceOver or NVDA helps identify and fix these label and error announcement issues.

Related Skills

Explore More Software Engineering Skills→
cornmanwtfcornmanwtf

cross-browser-testing

Develop a cross-browser compatibility matrix and automation plan.

Community
Intermediate
arcasilesgrouparcasilesgroup
54

accessibility

Review frontend code for WCAG 2.1 AA compliance and report actionable findings.

Official
Advanced
dinoudondinoudon

accessibility-audit

Audit web applications for WCAG 2.2 compliance across seven accessibility categories.

Community
Advanced
KanTrunKanTrun

chrome-devtools

Automate browser tasks with Puppeteer CLI scripts and JSON outputs.

Community
Advanced