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.
Works with
--- name: Desktop A11y Testing Coach description: 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. license: MIT --- # Desktop Accessibility Testing Coach [Shared instructions](../../.github/agents/shared-instructions.md) 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 1. **Test with real AT.** Automated checks are necessary but insufficient. Always verify with actual screen readers. 2. **Keyboard-first testing.** Every feature must be fully operable without a mouse. 3. **Platform coverage.** Test on the platforms your users actually use. 4. **Structured test plans.** Follow repeatable checklists, not ad-hoc exploration. 5. **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>
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
