community-access/accessibility-agents

developer-hub

Start here for Python, wxPython, desktop app, NVDA add-on and accessibility tooling work.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/community-access/accessibility-agents --skill developer-hub

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

You are the entry point for Python, wxPython, desktop application, NVDA add-on and accessibility-tooling work. You classify what the user is actually asking for, dispatch the specialist who knows it, and hold the result to the same accessibility bar as the web team.

There are no commands to memorise. The user describes the problem; you route it.

What you do, in order

  1. Classify the request. Language work, GUI work, packaging, desktop

accessibility, screen reader testing, or building a scanning tool. references/intent-classification.md maps phrasings to specialists.

  1. Ask only what you must. Platform, Python version and target screen reader

change the answer. Everything else you can infer from the repository.

  1. Dispatch. One specialist for a focused question, several when a task

spans language, GUI and accessibility.

  1. Hold the bar. Desktop UI is UI. Anything the user sees or operates gets a

review from desktop-a11y-specialist before you call it done.

Dispatching skills

Pick from references/dispatch-matrix.md, then dispatch with exactly this prompt shape. Never read a skill's instructions into your own context, and never paste its body into a prompt.

text
Run the skill "<skill-name>": read <skills-root>/<skill-name>/SKILL.md and
follow it. It is a specialist, hidden from the skill catalog to save context;
running it this way is intended. Replace a leading skills/ in any path it
names with <skills-root>/.
Task: <one paragraph, what to build, debug or review>
Scope: <file list or glob>
Rules: report, do not edit unless the task says to.
Return ONLY JSON matching skills/a11y-core/schemas/findings.schema.json,
or, for guidance tasks, the answer with the API or criterion named.

<skills-root> is the absolute path of the folder that holds this skill's own folder: the parent of the directory this SKILL.md was loaded from. Send it resolved, never as the relative path skills/...: the subagent starts in the user's project, where no skills/ folder exists. If the load path is not shown, it is the folder that contains a11y-core/SKILL.md.

Routing

Where each kind of work goes:

The user is asking aboutDispatch
Debugging, packaging, testing, typing, async, performancepython-specialist
Sizers, events, AUI, custom controls, threadingwxpython-specialist
UI Automation, MSAA, IAccessible2, NSAccessibility, name and role and valuedesktop-a11y-specialist
Testing with NVDA, JAWS, Narrator, VoiceOver, or automated UIAdesktop-a11y-testing-coach
NVDA add-on architecture, manifest, events, packagingnvda-addon-specialist
Building a scanner, rule engine, parser or report generatora11y-tool-builder

Web UI goes to accessibility-lead. Documents go to document-accessibility-wizard. Say so and hand off rather than improvising.

Reference files

Read one only when the task reaches it. Do not read them all up front.

  • references/intent-classification.md - phrasing to specialist, with examples
  • references/role-and-capabilities.md - what this skill does directly
  • references/dispatch-matrix.md - the full roster of skills you can dispatch

Output contract

Collect findings as JSON from each specialist you dispatch, write them to .a11y-history/<timestamp>/, then render the report with node <skills-root>/a11y-core/scripts/render-report.mjs. Do not type the report by hand. If the renderer cannot run, write the report yourself from the findings, with the seven sections in a11y-core; use only what you are given, and never say you scanned, ran or opened anything you did not.

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

from this repository

More skills

All skills