Agent skill

Desktop A11y Testing Coach

by Community-Access in Community-Access/accessibility-agents

Test desktop apps with NVDA, JAWS, Narrator, VoiceOver and UIA tooling.

MITAuto-check passedFrontend & Design

Install Desktop A11y Testing Coach

skills CLI
$ npx skills add Community-Access/accessibility-agents --skill desktop-a11y-testing-coach -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Community-Access/accessibility-agents desktop-a11y-testing-coach --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/desktop-a11y-testing-coach .claude/skills/desktop-a11y-testing-coach && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
desktop-a11y-testing-coach
GitHub stars
423
Token cost
~1.5k tokens
SKILL.md length
670 words
Files
2
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Test desktop apps with NVDA, JAWS, Narrator, VoiceOver and UIA tooling.

  • Works in 5 steps: Test with real assistive technology.… → Teach the testing workflow. Guide… → Document expected announcements. For… → …
  • Tasks that involve Accessibility
  • SKILL.md covers Desktop Accessibility Testing…, Core Principles, Screen Reader Quick Reference and Accessibility Insights for…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Desktop A11y Testing Coach is an agent skill from Community-Access/accessibility-agents. Test desktop apps with NVDA, JAWS, Narrator, VoiceOver and UIA tooling.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Frontend & Design, covering Accessibility and Text to speech and voice. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.

When your agent uses it

  • Tasks that involve Accessibility
  • Tasks that involve Text to speech and voice

Example prompts

  • “/desktop-a11y-testing-coach”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Test with real assistive technology. Automated catches 30-40%. Screen reader testing catches the rest.
  2. Teach the testing workflow. Guide developers through what to do, listen for, and expect.
  3. Document expected announcements. For every control, write what the screen reader SHOULD say.
  4. Keyboard first. Test keyboard navigation before screen reader testing.
  5. Cross-screen-reader testing. NVDA and JAWS behave differently. Test with at least two.

What it can do on your machine

Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Desktop A11y Testing Coach loads about 1.5k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 670 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 670 words, ~1,471 tokens.

Download SKILL.mdSave it as .claude/skills/desktop-a11y-testing-coach/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
desktop-a11y-testing-coach
description
Test desktop apps with NVDA, JAWS, Narrator, VoiceOver and UIA tooling.
license
MIT
disable-model-invocation
true
metadata.tier
specialist
metadata.domain
desktop
metadata.output
guidance
metadata.effort
medium
metadata.title
Desktop Accessibility Testing Coach

Desktop Accessibility Testing Coach

Skills: python-development

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

You receive handoffs from the Developer Hub or Desktop A11y Specialist when testing verification is needed. You also work standalone when invoked directly. You coordinate with the web Testing Coach for shared methodology when desktop apps contain web views.


Core Principles

  1. Test with real assistive technology. Automated catches 30-40%. Screen reader testing catches the rest.
  2. Teach the testing workflow. Guide developers through what to do, listen for, and expect.
  3. Document expected announcements. For every control, write what the screen reader SHOULD say.
  4. Keyboard first. Test keyboard navigation before screen reader testing.
  5. Cross-screen-reader testing. NVDA and JAWS behave differently. Test with at least two.

Screen Reader Quick Reference

NVDA (Windows -- Free)
  • Start/Stop: Ctrl+Alt+N
  • Read focus: NVDA+Tab
  • Speech Viewer: NVDA menu > Tools > Speech Viewer (shows all announcements as text)
  • Use Speech Viewer for verification without listening
JAWS (Windows -- Commercial)
  • Read focus: Insert+Tab
  • Virtual cursor for web content in desktop apps
  • Different behavior from NVDA -- test with both for production
Narrator (Windows -- Built-in)
  • Start/Stop: Win+Ctrl+Enter
  • Quick smoke tests only -- not a substitute for NVDA/JAWS
VoiceOver (macOS -- Built-in)
  • Start/Stop: Cmd+F5
  • VO key: Ctrl+Option

Accessibility Insights for Windows

Free UIA inspection tool from Microsoft:

  1. Live Inspect -- hover to see Name, Role, ControlType, Patterns, States
  2. FastPass -- automated checks (tab stops, name/role presence, focus)
  3. Assessment -- full guided accessibility assessment with pass/fail recording

Keyboard Testing Phases

  1. Tab Navigation -- Tab through every control, verify logical order
  2. Control Interaction -- Enter/Space for buttons, Space for checkboxes, arrows for lists/trees/radios
  3. Focus Management -- Dialog open/close, item deletion, panel show/hide

Automated UIA Testing

Use pywinauto with pytest for automated desktop accessibility checks:

python
from pywinauto import Application

def test_button_accessible(app):
    win = app.window(title="My App")
    btn = win.child_window(title="Save", control_type="Button")
    assert btn.exists() and btn.is_enabled()

Cross-Team Integration

  • Fix desktop a11y issues: Route to desktop-a11y-specialist or wxpython-specialist
  • Web a11y testing: Route to testing-coach for web screen reader and axe-core testing
  • Document output testing: Route to document-accessibility-wizard for Office/PDF verification

Test Coverage Audit Mode

When asked to audit test coverage or assess testing gaps for a desktop app, produce a structured report using these rules. These evaluate testing completeness, not the app itself.

Show full SKILL.md (287 more words)Show less
Detection Rules

Each rule ID, with severity and what it detects.

Rule IDSeverityWhat It Detects
TST-A11Y-001CriticalNo automated UIA tests -- no pywinauto/comtypes test files exist
TST-A11Y-002CriticalNo screen reader testing documented -- no test plan or expected announcements
TST-A11Y-003SeriousSingle screen reader only -- testing for only one SR; production needs at least two
TST-A11Y-004SeriousNo keyboard testing plan -- no Tab order, activation, or focus management tests
TST-A11Y-005SeriousNo high contrast verification -- no Windows HC or macOS Increase Contrast testing
TST-A11Y-006ModerateMissing expected announcements -- test plan lacks Name + Role + State specifications
TST-A11Y-007ModerateNo focus management tests -- no dialog/deletion/panel focus test cases
TST-A11Y-008ModerateNo Accessibility Insights usage -- no UIA tree inspection evidence
TST-A11Y-009MinorStale test plan -- test plan not updated since UI changes
TST-A11Y-010MinorNo CI integration -- automated tests not in CI/CD pipeline

Report Format: Application name, date, test artifacts reviewed, severity summary, per-finding details (rule ID, severity, evidence, recommendation, template reference).


Behavioral Rules

  1. Never write product code -- teach testing practices and create test plans
  2. Name exact screen reader commands for each verification step
  3. Show expected vs actual announcements
  4. Always include keyboard testing before screen reader testing
  5. Route fixes to desktop-a11y-specialist or wxpython-specialist
  6. Route web testing to testing-coach
  7. Recommend NVDA + JAWS for production apps
  8. Include Accessibility Insights inspection steps
  9. Document tests in reusable test plan format
  10. Coordinate with web and document teams for cross-boundary testing

Output contract

Answer the question. Keep the answer to what was asked, cite the criterion or API by name, and stop. Do not append a checklist that was not requested.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/desktop-a11y-testing-coach of Community-Access/accessibility-agents.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Desktop A11y Testing Coach next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Desktop A11y Testing Coach compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Desktop A11y Testing Coach this skillCommunity-Access/accessibility-agents423—~1.5kAutomated safety check: PassMIT
Accessibility Generatorrshankras/claude-code-apple-skills787—~1.4kAutomated safety check: NotesMIT
iOS Accessibilitydadederk/iOS-Accessibility-Agent-Skill174—~2.4kAutomated safety check: PassMIT
AccessibilityGetStream/stream-chat-react-native1.2k—~6.5kAutomated safety check: PassCustom licence
Maui Accessibilitydavidortinau/maui-skills175—~974Automated safety check: PassMIT
iOS Higjohnrogers/claude-swift-engineering231—~705Automated safety check: PassMIT

Similar skills

  • Accessibility Generator

    rshankras/claude-code-apple-skills

    Generate accessibility infrastructure for VoiceOver, Dynamic Type, and accessibility features.

    787 GitHub stars~1.4k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check: notes
  • iOS Accessibility

    dadederk/iOS-Accessibility-Agent-Skill

    Expert guidance on iOS accessibility best practices, patterns, and implementation.

    174 GitHub stars~2.4k tokensUpdated 7 mo ago
    Frontend & DesignAuto-check passed
  • Accessibility

    GetStream/stream-chat-react-native

    Maintain VoiceOver/TalkBack-focused accessibility in stream-chat-react-native.

    1.2k GitHub stars~6.5k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Maui Accessibility

    davidortinau/maui-skills

    Guide for making .NET MAUI apps accessible — screen reader support via SemanticProperties, heading levels, AutomationProperties visibility control, programmatic focus and announcements, and…

    175 GitHub stars~974 tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • iOS Hig

    johnrogers/claude-swift-engineering

    A skill your agent uses when designing iOS interfaces, implementing accessibility (VoiceOver, Dynamic Type), handling dark mode, ensuring adequate touch targets, providing animation/haptic feedback…

    231 GitHub stars~705 tokensUpdated 8 mo ago
    Frontend & DesignAuto-check passed
  • Screen Demo Production

    calesthio/generative-media-skills

    Provider-independent workflow for producing terminal, IDE, documentation, browser, desktop, and application demonstration videos.

    197 GitHub stars~3.5k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed

More from Community-Access/accessibility-agents

All 108 skills in this repo
  • A11y Core

    Community-Access/accessibility-agents

    Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.

    423 GitHub stars~1.2k tokensUpdated 17 days ago
    Auto-check passed
  • Kb Web Scanning

    Community-Access/accessibility-agents

    Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.

    423 GitHub stars~1.2k tokensUpdated 17 days ago
    Auto-check passed
  • Accessibility Lead

    Community-Access/accessibility-agents

    Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.

    423 GitHub stars~932 tokensUpdated 17 days ago
    Auto-check passed
  • Alt Text Headings

    Community-Access/accessibility-agents

    Alt text, SVGs, figures, charts, heading order, page titles and landmarks.

    423 GitHub stars~1.5k tokensUpdated 17 days ago
    Auto-check passed
  • Aria Specialist

    Community-Access/accessibility-agents

    ARIA roles, states and properties for custom widgets and dynamic content.

    423 GitHub stars~1.6k tokensUpdated 17 days ago
    Auto-check passed
  • Cognitive Accessibility

    Community-Access/accessibility-agents

    Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.

    423 GitHub stars~1.4k tokensUpdated 17 days ago
    Auto-check passed

Questions about Desktop A11y Testing Coach

What does Desktop A11y Testing Coach do?

Test desktop apps with NVDA, JAWS, Narrator, VoiceOver and UIA tooling. Desktop A11y Testing Coach is an agent skill from Community-Access/accessibility-agents. Test desktop apps with NVDA, JAWS, Narrator, VoiceOver and UIA tooling.

When should I use Desktop A11y Testing Coach?

Desktop A11y Testing Coach fits situations like: tasks that involve Accessibility; tasks that involve Text to speech and voice.

How do I install Desktop A11y Testing Coach in Claude Code?

Run `npx skills add Community-Access/accessibility-agents --skill desktop-a11y-testing-coach -a claude-code`. Or copy the skill folder (skills/desktop-a11y-testing-coach in Community-Access/accessibility-agents) into .claude/skills/desktop-a11y-testing-coach in your project. Claude Code loads it when a task matches its description.

How do I install Desktop A11y Testing Coach in Codex?

Run `npx skills add Community-Access/accessibility-agents --skill desktop-a11y-testing-coach -a codex`. Or copy the skill folder (skills/desktop-a11y-testing-coach in Community-Access/accessibility-agents) into .agents/skills/desktop-a11y-testing-coach in your project. Codex loads it when a task matches its description.

Can I use Desktop A11y Testing Coach in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill desktop-a11y-testing-coach -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/desktop-a11y-testing-coach, .gemini/skills/desktop-a11y-testing-coach, .github/skills/desktop-a11y-testing-coach and .opencode/skills/desktop-a11y-testing-coach in your project.

What does Desktop A11y Testing Coach need to run?

SKILL.md names no scripts, command-line tools or credentials: Desktop A11y Testing Coach is instructions for the agent only. Our summary lists: Python 3.

Does Desktop A11y Testing Coach access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Desktop A11y Testing Coach safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Desktop A11y Testing Coach use?

Desktop A11y Testing Coach is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Desktop A11y Testing Coach use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Desktop A11y Testing Coach?

Skills that share tags, products or a category with Desktop A11y Testing Coach: Accessibility Generator (rshankras/claude-code-apple-skills, 787 stars), iOS Accessibility (dadederk/iOS-Accessibility-Agent-Skill, 174 stars), Accessibility (GetStream/stream-chat-react-native, 1.2k stars) and Maui Accessibility (davidortinau/maui-skills, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Desktop A11y Testing Coach?

Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 423 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.

Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.