skills.rest
wesleyegberto
wesleyegbertoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

frontend-screen-reader-testing

Automate screen reader compatibility testing for web applications across VoiceOver, NVDA, JAWS, and TalkBack.

3|2|Updated Mar 23, 2026
Search Tags:#accessibility#screen-reader#aria#qa-testing#web-accessibility#assistive-tech
One-click install
npx skills add https://github.com/wesleyegberto/software-engineering-skills --skill frontend-screen-reader-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-screen-reader-testing
Source: https://github.com/wesleyegberto/software-engineering-skills/tree/main/plugins/frontend/skills/frontend-screen-reader-testing
Command: npx skills add https://github.com/wesleyegberto/software-engineering-skills --skill frontend-screen-reader-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps QA and accessibility engineers validate screen reader compatibility across major platforms and ensure keyboard navigability.

Core Features & Use Cases

  • Comprehensive coverage of major screen readers (VoiceOver, NVDA, JAWS, TalkBack, Narrator) across platforms.
  • Guided setup and testing procedures for VoiceOver (macOS), NVDA (Windows), JAWS (Windows), and TalkBack (Android).
  • Practical test scripts and checklists for common scenarios like modals, live regions, tab interfaces, and forms.
  • Best practices and debugging tips to ensure reliable keyboard navigation and ARIA semantics.

Quick Start

Use the screen reader testing workflow to validate focus management and landmark navigation on your web application.

Frequently Asked Questions about frontend-screen-reader-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test web apps for screen reader compatibility across different platforms?▼

Test web apps for screen reader compatibility by validating keyboard navigation and ARIA semantics using guided test scripts and checklists. This process ensures assistive tech compatibility across VoiceOver, NVDA, JAWS, and TalkBack on macOS, Windows, iOS, and Android.

What is the best way to set up VoiceOver and NVDA for web accessibility testing?▼

The best way to set up VoiceOver and NVDA for web accessibility testing is following guided setup procedures for each platform. This prepares your environment to evaluate focus management, landmark navigation, and dynamic content interactions effectively.

How do I validate ARIA roles and keyboard navigation in dynamic web content?▼

Validate ARIA roles and keyboard navigation in dynamic web content by applying practical test scripts for modals, live regions, and tab interfaces. These scripts check focus management and semantic structures to ensure assistive technologies interpret updates correctly.

Can I use these test scripts for accessibility regression checks on forms and modals?▼

Yes, you can use these test scripts for accessibility regression checks on forms and modals. The checklists evaluate common scenarios like live regions and tab interfaces, ensuring continuous keyboard navigability and ARIA semantics validation across updates.

Does this screen reader testing workflow cover JAWS and TalkBack environments?▼

Yes, this screen reader testing workflow covers JAWS on Windows and TalkBack on Android. It provides specific testing procedures, best practices, and debugging tips tailored to ensure reliable keyboard navigation and ARIA semantics on each platform.

Why does my screen reader fail to announce dynamic content in live regions?▼

Screen readers fail to announce dynamic content in live regions when ARIA semantics are improperly implemented. Debugging tips and best practices help identify incorrect focus management and missing ARIA roles, ensuring dynamic updates are properly vocalized.

Related Skills

Explore More Software Engineering Skills→
bipinksbipinks
3

accessibility-patterns

Apply WCAG 2.1 AA/AAA patterns to improve UI accessibility.

Community
Advanced
zinohomezinohome

accessibility-auditor

Audits and implements web accessibility following WCAG 2.1 guidelines with ARIA patterns.

Community
Intermediate
CrazyDubyaCrazyDubya

accessibility-auditor

Audit web applications for WCAG 2.1 Level AA accessibility compliance.

Community
Intermediate
ariesanhthuariesanhthu

accessibility-expert

Audits WCAG 2.1/2.2 compliance and fixes accessibility violations in web projects.

Community
Advanced