English Français العربية

Accessibility Agents

Official registry Search and web

WCAG 2.2 scanners for web pages, Office, PDF, ePub and Markdown: contrast, axe, veraPDF and more.

Source code Website Documentation

What can you do with Accessibility Agents?

  • Reviews web UI across ARIA, keyboard, focus, forms, contrast, modals, live
  • Scans documents for Office, PDF and ePub accessibility, one file or a
  • Audits markdown for link text, alt text, heading order, tables, emoji and
  • Blocks unreviewed edits. A hook refuses a write to a user-facing file
  • Renders reports. Findings are JSON; a script writes the report, computes
  • Supplies scanners over MCP. Thirty-nine tools: axe-core, Office, PDF,

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @community-access/accessibility-agents-mcp
Claude Code 
claude mcp add accessibility-agents -- npx -y @community-access/accessibility-agents-mcp@7.1.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "accessibility-agents": {
            "command": "npx",
            "args": [
                "-y",
                "@community-access/accessibility-agents-mcp@7.1.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Accessibility Agents
  2. Install
  3. How to use it
  4. What it does
  5. Layout
  6. Verify
  7. Standards
  8. Accessibility of this project
  9. Contributing
  10. History
  11. Licence

Accessibility Agents

WCAG 2.2 AA enforcement for agentic coding, as a set of Agent Skills. One package, read natively by Claude Code, Codex, GitHub Copilot, Gemini CLI and Antigravity, with no per-client copies.

Models forget accessibility while generating code. This package makes that harder: it routes the work to the right specialist, blocks edits to user-facing files until the accessibility lead has reviewed, and renders audit reports from structured findings rather than from memory.

Install

As a plugin (on Gemini CLI, an extension), which loads the skills, the hooks and the MCP server registration (on Codex, the skills and the MCP server only: Codex no longer loads plugin hooks, so use npm run setup there for the edit gate):

Claude Code   /plugin marketplace add Community-Access/accessibility-agents
              /plugin install accessibility-agents@community-access
Copilot CLI   copilot plugin marketplace add Community-Access/accessibility-agents
              copilot plugin install accessibility-agents@community-access
Codex         codex plugin marketplace add Community-Access/accessibility-agents
              codex plugin add accessibility-agents@community-access
              (skills and MCP server only; no edit gate, see below)
VS Code       Chat: Install Plugin From Source, with the repository URL
              (requires the chat.plugins.enabled setting)
Gemini CLI    gemini extensions install https://github.com/Community-Access/accessibility-agents
              (uses the extension archive attached to each release, from 7.1.0)

The MCP server ships as a single bundle, mcp-server/dist/stdio.mjs, so a plugin install starts it with no npm install. Only the optional scanners need installing: Playwright and @axe-core/playwright for the browser scans, pdf-lib for PDF form conversion, and the veraPDF CLI. The tools that need them say how when they are missing.

The MCP server on its own is published to npm as @community-access/accessibility-agents-mcp and listed in the MCP Registry as io.github.Community-Access/accessibility-agents, from 7.1.0 once the release is published: npx -y @community-access/accessibility-agents-mcp. See the MCP server README.

Directly from a checkout, for Antigravity, or any client without the plugin:

npm install
npm run setup -- --dry-run
npm run setup

npm run setup copies the skills to ~/.agents/skills, the personal location Codex, the Copilot CLI, VS Code and Gemini CLI read, and to ~/.gemini/config/skills when Antigravity is present. It writes the hook manifest for Codex, Gemini CLI and Antigravity when they are present. It never overwrites a hooks file or a skill you have edited, and --dry-run prints every action without doing it. Claude Code does not read ~/.agents/skills, so the installer writes nothing for it: use the plugin, or start Claude Code with --plugin-dir pointing at the checkout. For the optional scanners, run npm install --prefix mcp-server, then npx playwright install chromium in mcp-server/.

How to use it

Describe the problem. Six entry points route the rest.

You are working onSkill
HTML, JSX, TSX, Vue, Svelte, CSS, or a server templateaccessibility-lead
A full site or app audit rather than one changeweb-accessibility-wizard
Word, Excel, PowerPoint, PDF or ePub filesdocument-accessibility-wizard
Markdown documentationmarkdown-a11y-assistant
Python, wxPython, desktop apps, NVDA add-ons, accessibility toolingdeveloper-hub
Issues, pull requests, releases, projects, actions, security, teams, wikisgithub-hub

Those six dispatch a further 107 specialist, helper and reference skills by name. The other 107 are invisible to the model until a router names one, which is why the whole package costs about 1,100 tokens before you have said anything.

What it does

  • Reviews web UI across ARIA, keyboard, focus, forms, contrast, modals, live regions, headings, tables, links, cognitive load, internationalisation, performance, mobile, email, data visualisation and web components.
  • Scans documents for Office, PDF and ePub accessibility, one file or a whole tree, and generates remediation scripts.
  • Audits markdown for link text, alt text, heading order, tables, emoji and diagrams.
  • Blocks unreviewed edits. A hook refuses a write to a user-facing file until the accessibility lead completes, on every client that supports hooks.
  • Renders reports. Findings are JSON; a script writes the report, computes the score, and shows the delta against the previous run.
  • Supplies scanners over MCP. Thirty-nine tools: axe-core, Office, PDF, ePub, markdown, veraPDF, Playwright behavioural scans, audit history and report rendering.

Layout

AGENTS.md                the always-on contract, under 1,200 tokens
CLAUDE.md                one line, importing AGENTS.md
plugin.json              Agent Plugins 1.0 manifest
mcp.json                 MCP server registration
skills/                  113 skills
  a11y-core/             shared contract, findings schema, scripts
  <router>/              the six entry points
  <specialist>/          one domain each, dispatched by a router
  kb-<domain>/           reference data: rule tables, URL registries, formulas
hooks/                   one guard script and the client hook manifests
com.github.copilot/      Copilot and VS Code plugin hooks (Agent Plugins 1.0)
mcp-server/              the scanners
docs/                    conformance dossier, guides, release notes

Verify

npm run verify

Sixteen gates, each naming the standard it checks and what a failure would cost; all sixteen passed on 2026-10-28. Two are optional: the dependency advisory check, and live sessions on whichever of Claude Code, Codex and Copilot are installed. The evidence, measured results and the one documented deviation from the Agent Skills specification are in the conformance dossier.

npm run measure           # what the package costs, per client
npm run measure:dispatch  # what dispatching a specialist costs
npm run probe:mcp         # the MCP tool surface

Standards

Each standard, with what it governs.

StandardGoverns
Agent Skillsevery skill
AGENTS.mdthe always-on contract
Agent Plugins 1.0packaging
Model Context Protocolthe scanners
WCAG 2.2every criterion a finding cites
Open Source Accessibility Frameworkhow this project runs accessibility as an open source project, and what the agents help your project adopt

Accessibility of this project

How we work on our own accessibility, how to report a barrier (on GitHub or by email) and how we respond are in ACCESSIBILITY.md. We follow GitHub's Open Source Accessibility Framework; the agents can apply the same framework to your repository: ask your client to adopt the Open Source Accessibility Framework, or one of its four phases (foundational, workflow, testing, community).

Our progress, action by action, is tracked in public in our framework tracking issue.

Contributing

Edit skills/<name>/SKILL.md, keep the body under 6 KiB, put the long tail in references/, and run npm run verify. Details in CONTRIBUTING.md, and the accessibility expectations for every contribution in ACCESSIBILITY.md.

History

Version 7.0 replaced six hand-maintained per-client trees with this one package. The plan, the phases and the measured impact are in the modernization record. What comes next is in ROADMAP.md.

Licence

MIT. See LICENSE.

Frequently asked questions

What is Accessibility Agents?

WCAG 2.2 scanners for web pages, Office, PDF, ePub and Markdown: contrast, axe, veraPDF and more.

How do I install Accessibility Agents?

It runs on your machine. In Claude Code: claude mcp add accessibility-agents -- npx -y @community-access/accessibility-agents-mcp@7.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Accessibility Agents need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Accessibility Agents open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Accessibility Agents?

It is published by Community-Access. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.