screen-reader-testing

Test web applications with VoiceOver, NVDA, JAWS, and TalkBack screen readers.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Eng-suso/BK-GPT --skill screen-reader-testing-eng-suso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/Eng-suso/BK-GPT/tree/main/.claude/skills/screen-reader-testing
Command: npx skills add https://github.com/Eng-suso/BK-GPT --skill screen-reader-testing-eng-suso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web applications often fail for assistive technology users because developers cannot verify how screen readers announce content, forms, and dynamic updates. This Skill provides structured testing procedures, keyboard command references, and checklists to validate screen reader compatibility across major platforms. ## Core Features & Use Cases - Multi-Platform Testing Guides: Covers VoiceOver (macOS/iOS), NVDA, JAWS, Narrator (Windows), and TalkBack (Android) with essential commands and setup steps. - ARIA Pattern Validation: Provides accessible markup and JavaScript for modals, live regions, tab interfaces, and focus management. - Use Case: After building a checkout form, run the NVDA test script to verify labels are announced, errors trigger alerts, and focus moves correctly to invalid fields before release. ## Quick Start Ask the assistant to walk you through testing your page's form validation and modal dialogs with NVDA or VoiceOver using the provided 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 a website with a screen reader?▼

Screen reader testing starts with keyboard-only navigation, then uses tools like NVDA on Windows or VoiceOver on macOS to navigate by headings, landmarks, and form fields. Follow structured checklists covering page load announcements, link purpose, form labels, and dynamic content updates.

Which screen readers should I test with for accessibility?▼

Minimum coverage includes NVDA with Firefox on Windows, VoiceOver with Safari on macOS, and VoiceOver on iOS. Comprehensive coverage adds JAWS with Chrome, TalkBack on Android, and Narrator with Edge, since each combination announces content differently.

How do I make dynamic content announcements work with screen readers?▼

Use ARIA live regions: role="status" with aria-live="polite" for status messages, and role="alert" with aria-live="assertive" for urgent errors. Screen readers announce content injected into these regions without moving user focus.

Why is my form error message not announced by screen readers?▼

Errors are missed when they lack programmatic association with inputs. Add aria-invalid="true" to the field, link the message with aria-describedby, and give the error container role="alert" so it is announced immediately when it appears.

What is the difference between browse mode and focus mode in NVDA?▼

Browse mode lets arrow keys read page content line by line, while focus mode passes keystrokes directly to interactive controls like text fields. NVDA switches automatically, but elements with role="application" force focus mode, which can confuse users if misused.