screen-reader-testing

Test web application accessibility with screen readers like VoiceOver and NVDA.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill screen-reader-testing-jhabbig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: screen-reader-testing
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/accessibility-compliance/skills/screen-reader-testing
Command: npx skills add https://github.com/Jhabbig/Habbig --skill screen-reader-testing-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify that web interfaces remain usable and understandable when navigated with screen readers, exposing accessibility gaps that visual testing often misses.

Core Features & Use Cases

  • Screen Reader Coverage: Validate behavior in VoiceOver, NVDA, JAWS, TalkBack, and Narrator.
  • Accessibility Debugging: Find issues in headings, landmarks, labels, focus order, live regions, dialogs, and tables.
  • Use Case: Check a checkout flow, modal dialog, or form experience to confirm that assistive technology users can complete tasks without confusion.

Quick Start

Test this web page with a screen reader and summarize any accessibility issues affecting navigation, labeling, focus management, or dynamic content 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 a screen reader like NVDA or VoiceOver?

Test web accessibility by validating how screen readers announce and navigate content using semantic HTML, ARIA labeling, and keyboard-compatible interactions across NVDA, VoiceOver, JAWS, TalkBack, and Narrator.

What's the best way to find ARIA labeling and focus management issues in web forms?

Find ARIA labeling and focus management issues by testing forms, dynamic content, and custom widgets to verify that screen readers correctly announce labels, landmarks, and live regions without confusing navigation.

Does this screen reader testing approach work with TalkBack and Narrator?

Yes, this screen reader testing approach works with TalkBack and Narrator, validating content announcements, focus order, and keyboard-compatible interactions across all major assistive technologies.

How do I verify live region announcements and modal dialog behavior for assistive technology users?

Verify live region announcements and modal dialog behavior by testing dynamic content interactions to confirm screen readers properly announce changes and manage focus within dialogs without disorientation.

Why does my screen reader skip headings and landmarks during web navigation?

Screen readers skip headings and landmarks when semantic HTML and ARIA roles are missing or misapplied, requiring accessibility testing to expose navigation gaps that visual testing often misses.

Can I test custom widget accessibility for screen reader users without manual device testing?

Test custom widget accessibility by validating keyboard-compatible interactions and ARIA labeling against assistive technology expectations, exposing usability gaps in dynamic content that visual testing misses.