skills.rest
ekremmkasap
ekremmkasapCOMMUNITY
Explore all skills by this author →
GitHub

screen-reader-testing

Guide screen reader testing for web accessibility across VoiceOver, NVDA, JAWS, and TalkBack.

Updated Mar 18, 2026
Search Tags:#accessibility#a11y#voiceover#talkback#nvda#jaws#screen-reader-testing
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill screen-reader-testing-ekremmkasap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/accessibility-compliance/skills/screen-reader-testing
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill screen-reader-testing-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides guidance and workflows to test web applications with major screen readers (VoiceOver, NVDA, JAWS, TalkBack), helping teams identify accessibility issues such as ARIA misconfigurations, focus management gaps, and dynamic content updates.

Core Features & Use Cases

  • Platform-agnostic SR testing guidance across VoiceOver, NVDA, JAWS, and TalkBack
  • Practical checklists and commands for focus management, navigation, forms, and dynamic content
  • Scenario-based examples and debugging tips to reproduce accessibility issues
  • Best practices for keyboard-only testing and accessibility validation

Quick Start

Install and run the screen reader testing workflow across VoiceOver, NVDA, JAWS, and TalkBack to begin validating 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 accessibility with screen readers like VoiceOver and NVDA?▼

Screen reader testing validates web accessibility by navigating web applications using tools like VoiceOver, NVDA, JAWS, and TalkBack to identify ARIA misconfigurations, focus management gaps, and dynamic content update issues.

What are the essential screen reader commands for testing web navigation and forms?▼

Essential screen reader commands for testing navigation and forms include specific keystrokes for traversing headings, landmarks, and form fields across VoiceOver, NVDA, JAWS, and TalkBack to ensure proper focus management and keyboard-only operability.

How do I debug ARIA implementations and focus management issues during screen reader testing?▼

Debug ARIA implementations and focus management issues by reproducing accessibility barriers using scenario-based testing steps and screen reader commands, which help pinpoint dynamic content update failures and incorrect ARIA roles.

Can I use this screen reader testing workflow across both desktop and mobile platforms?▼

Yes, this screen reader testing workflow applies across desktop and mobile platforms, providing platform-agnostic guidance for VoiceOver, NVDA, JAWS, and TalkBack to validate web accessibility.

Why does my dynamic web content not announce updates when using JAWS or TalkBack?▼

Dynamic web content fails to announce updates on JAWS or TalkBack due to missing ARIA live regions or incorrect focus management, requiring specific screen reader testing scenarios to diagnose and fix.

What is the best way to validate keyboard-only navigation for web accessibility?▼

The best way to validate keyboard-only navigation for web accessibility is to follow structured checklists and best practices that test focus order, form interaction, and dynamic content without a mouse.

Related Skills

Explore More Software Engineering Skills→
drgaciwdrgaciw

screen-reader-testing

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

Community
Intermediate
bovinphangbovinphang
21

fec-accessibility-check

Identify frontend accessibility issues and generate a WCAG 2.2 AA review report.

Community
Intermediate
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate
RepairYourTechRepairYourTech
6

accessibility-compliance

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

Community
Advanced