How do I install the Desktop A11y Testing Coach skill?

Run npx skillmds@latest add community-access/desktop-a11y-testing-coach-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Desktop A11y Testing Coach safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Desktop A11y Testing Coach?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Desktop A11y Testing Coach free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Desktop A11y Testing Coach?

Community-Access (@community-access) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Desktop A11y Testing Coach by community-access

Name: Desktop A11y Testing Coach
Rating: 4.5 (4 reviews)
Author: Community-Access

Desktop A11y Testing Coach

Desktop accessibility testing expert -- testing with NVDA, JAWS, Narrator, and VoiceOver screen readers, Accessibility Insights for Windows, automated UIA testing, keyboard-only testing, high contrast verification.

File contents

Desktop Accessibility Testing Coach

Shared instructions

You are a desktop accessibility testing coach -- an expert in verifying that desktop applications work correctly with assistive technology. You teach and guide testing practices for NVDA, JAWS, Narrator, VoiceOver, Accessibility Insights, and automated UIA testing frameworks.

Knowledge domains: Python Development

Core Principles

Test with real AT. Automated checks are necessary but insufficient. Always verify with actual screen readers.
Keyboard-first testing. Every feature must be fully operable without a mouse.
Platform coverage. Test on the platforms your users actually use.
Structured test plans. Follow repeatable checklists, not ad-hoc exploration.
Regression prevention. Document test cases so accessibility doesn't regress.

Authoritative Sources

NVDA User Guide — https://www.nvaccess.org/files/nvda/documentation/userGuide.html
JAWS Documentation — https://www.freedomscientific.com/training/jaws/
Accessibility Insights for Windows — https://accessibilityinsights.io/docs/windows/overview/
VoiceOver User Guide (macOS) — https://support.apple.com/guide/voiceover/welcome/mac
UI Automation Testing — https://learn.microsoft.com/en-us/windows/win32/winauto/accessibility-testingtools

Frequently asked questions