Testing Coach

Guide accessibility testing for web applications with screen readers and automated tools.

387|42|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Community-Access/accessibility-agents --skill testing-coach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Testing Coach
Source: https://github.com/Community-Access/accessibility-agents/tree/main/.gemini/extensions/a11y-agents/skills/testing-coach
Command: npx skills add https://github.com/Community-Access/accessibility-agents --skill testing-coach

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between code that looks accessible and code that actually works for people with disabilities, by teaching and guiding effective accessibility testing methodologies.

Core Features & Use Cases

  • Screen Reader Testing Guidance: Provides detailed instructions and commands for NVDA, VoiceOver, and JAWS.
  • Keyboard Navigation Training: Teaches essential keyboard-only testing workflows and best practices.
  • Automated Testing Setup: Guides users on integrating tools like axe-core, Pa11y, and Lighthouse into their development process.
  • Use Case: A developer is unsure how to properly test a new modal dialog with a screen reader. They ask the Testing Coach for guidance on using VoiceOver to verify the modal's accessibility.

Quick Start

Guide me through testing a new modal dialog using VoiceOver.

Frequently Asked Questions about Testing Coach

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?

Screen reader testing with NVDA, VoiceOver, or JAWS involves navigating web applications using specific keyboard commands to verify content is announced correctly. This Skill provides detailed instructions and commands for conducting these accessibility tests effectively.

What's the best way to test keyboard navigation for web applications?

Keyboard navigation testing ensures users can access all interactive elements without a mouse. This Skill teaches essential keyboard-only testing workflows and best practices to verify that web application navigation meets accessibility standards.

How do I set up automated accessibility testing tools like axe-core and Pa11y?

Automated accessibility testing setup involves integrating tools like axe-core, Pa11y, and Lighthouse into your development process. This Skill guides users on configuring these tools and interpreting their test results for web applications.

How do I verify modal dialog accessibility using VoiceOver?

Testing modal dialog accessibility with VoiceOver requires verifying focus management and screen reader announcements when the dialog opens and closes. This Skill provides guidance on using VoiceOver commands to validate these interactions.

Can I use this Skill to learn WCAG compliance testing methodologies?

WCAG compliance testing is covered through comprehensive guidance on accessibility testing methodologies. This Skill focuses on teaching practical testing practices using screen readers, keyboard navigation, and automated tools rather than writing product code.

What is the difference between automated accessibility testing and screen reader testing?

Automated accessibility testing uses tools like axe-core to detect code-level issues, while screen reader testing with NVDA or JAWS evaluates the actual user experience. This Skill teaches both approaches to ensure comprehensive coverage of web accessibility.