New Accessibility Agents 7.1 is out. Read what changed

Accessible by default.

Community Access is an open source community led by blind and low vision developers. We build the tools, the training and the practices that make software work for everyone, and we test every one of them with the screen readers we use every day.

  • 5 flagship projects, all free and open source
  • 6 AI coding tools enforcing WCAG 2.2 AA through Accessibility Agents
  • WCAG 2.2 AA the bar every project is built and tested to, with NVDA, JAWS, VoiceOver and braille

What we make

Five projects, one idea: the people who rely on accessibility should be the ones who shape it.

For developers using AI

Accessibility Agents

WCAG 2.2 AA enforcement inside Claude Code, GitHub Copilot, Codex, Gemini CLI and Antigravity. Six entry points route every change to the right specialist, a hook refuses unreviewed edits to user-facing files, and 39 scanners check web pages, Office files, PDFs and ePub.

Less always-on context in version 7
93%
Specialists, each owning one domain
61
MCP scanning tools
39

For screen reader users

QUILL for All

Free talking software for Windows. QUILL is a full writing studio; its family of apps adds a simple editor, internet radio, a podcast player, an audio studio, weather and a media converter. Every command tells you what happened, and everything works from the keyboard.

  • QUILL
  • QUILL Lite
  • Quill Radio
  • QUILL Cast
  • Audio Studio
  • Quill Weather
  • Quill Converter

For document authors

GLOW

Guided Layout & Output Workflow. Audit, fix and convert Word, Excel, PowerPoint, PDF, Markdown and ePub files against the ACB Large Print Guidelines, APH large print, Microsoft Accessibility Checker and WCAG 2.2 AA. Free, with no account.

For learners

GIT Going with GitHub

A free, accessibility-first workshop where blind and low vision participants learn open source contribution with a screen reader, a keyboard and nothing else. Curriculum, facilitator guides, challenges and podcasts, all open.

For maintainers

Open Source Accessibility Framework

GitHub’s framework for running accessibility as part of an open source project: 24 actions across foundations, workflow, testing and community. We follow it in our own projects, in public, and Accessibility Agents can adopt it in yours, one action or all of them.

Browse all repositories

Accessibility Agents 7: rebuilt from the ground up

Six hand-maintained copies of the project, one per AI tool, are now a single package on the open agent standards. Same expertise. A fraction of the cost. Much harder to skip.

What the package costs before you type a word

Always-on context in tokens, measured September 21, 2026. Lower is better.

ClientBefore 7.0After 7.0Reduction
Claude Code 15,924 1,136 93%
GitHub Copilot 17,347 1,136 93%
Gemini CLI and Antigravity 12,848 1,136 91%
Codex 15,074 2,417 84%
Calling a specialist
26,929 100 tokens. Routers send a skill’s name instead of pasting its instructions.
A ten-specialist audit
320,000 under 5,000 tokens spent on coordination before any analysis starts.
Writing the report
15,000 0 output tokens. A script renders it from structured findings.

New in 7.1, released October 28, 2026

One install, every client

Plugin installs now bring the skills, the edit gate and the MCP server together. The server ships as one bundle, so it starts with no npm install.

On npm and the MCP Registry

Run all 39 scanners in any MCP client with npx -y @community-access/accessibility-agents-mcp. Published with provenance and approved with two-factor authentication.

The edit gate, everywhere

A hook refuses writes to user-facing files until the accessibility lead finishes. It ships for six clients, fails closed, and is tested live on Claude Code and Codex.

Open Source Accessibility Framework

Four new skills help any repository adopt GitHub’s framework, all 24 actions or one at a time. We follow it ourselves, tracked in public.

Every skill audited

All 108 original skills checked against primary sources: ADA Title II, HHS 504, EN 301 549, ISO/IEC 40500:2025, VPAT 2.5Rev, PDF/UA-2, ARIA and the APG.

Shaped by the community

New guidance on Qt accessible names and on flex and grid layouts that split one phrase into many screen reader stops, or glue words together: “Ada6:37 PM”.

Read the full announcement Changelog

Six front doors, 61 specialists behind them

You no longer pick from a list of agents. Describe the problem and one of six entry points routes the work to the specialists who own it. Behind them are 61 specialists, 16 helpers and 30 reference skills, 113 in all, and none of them costs anything until a router calls it.

  1. accessibility-lead

    HTML, JSX, TSX, Vue, Svelte, Astro, CSS and server templates

    Picks the specialists for a web change, runs them, and merges what they find.

  2. web-accessibility-wizard

    A full site or app audit

    A guided, phased WCAG 2.2 audit with a scored report and a delta against the last run.

  3. document-accessibility-wizard

    Word, Excel, PowerPoint, PDF and ePub

    One file or a whole tree, with remediation scripts for what it finds.

  4. markdown-a11y-assistant

    Documentation

    Link text, alt text, heading order, tables, emoji and diagrams.

  5. developer-hub

    Python, wxPython, Qt, desktop apps and NVDA add-ons

    Platform accessibility APIs, screen reader testing and accessibility tooling.

  6. github-hub

    Issues, pull requests, releases, projects, actions and wikis

    Your GitHub workflow, plus adopting the Open Source Accessibility Framework.

Harder to skip

The edit gate blocks writes to user-facing files until a review has actually finished, not merely started.

Evidence, not memory

Findings are JSON against one schema, and every one is checked against the real WCAG 2.2 criterion list, so an audit cannot cite a criterion that doesn’t exist.

Reports that remember

A script scores the audit, merges duplicates from different specialists, and shows what moved since last time.

Screen reader first

Written by people who use NVDA, JAWS and VoiceOver every day, so the advice is about real assistive technology, not just the spec.

Every domain the specialists cover
  • ARIA
  • Keyboard
  • Focus management
  • Forms
  • Color contrast
  • Modals and dialogs
  • Live regions
  • Headings and alt text
  • Tables
  • Links
  • Cognitive accessibility
  • Internationalisation
  • Mobile and React Native
  • Email
  • Data visualisation
  • Web components
  • Performance
  • Word
  • Excel
  • PowerPoint
  • PDF/UA
  • ePub
  • Markdown
  • Python and wxPython
  • Qt Widgets
  • Desktop APIs
  • NVDA add-ons
  • VPAT and ACR reports
  • GitHub workflows
  • Open Source Accessibility Framework

Install Accessibility Agents

Pick your tool. Each install brings the skills, the edit gate where the client supports hooks, and the MCP server. New to AI coding apps? Start here for step-by-step setup in Claude, Copilot, VS Code, Codex and more, written for beginners.

Claude Code
In a Claude Code session
/plugin marketplace add Community-Access/accessibility-agents /plugin install accessibility-agents@community-access
GitHub Copilot CLI
In a terminal
copilot plugin marketplace add Community-Access/accessibility-agents copilot plugin install accessibility-agents@community-access
VS Code

Turn on the chat.plugins.enabled setting, then run Chat: Install Plugin From Source from the Command Palette with this repository URL:

Repository URL
https://github.com/Community-Access/accessibility-agents
Codex
In a terminal
codex plugin marketplace add Community-Access/accessibility-agents codex plugin add accessibility-agents@community-access

Codex plugins bring the skills and the MCP server. For the edit gate, also run npm run setup from a checkout (see “Antigravity, or from a checkout” below).

Gemini CLI
In a terminal
gemini extensions install https://github.com/Community-Access/accessibility-agents
Any MCP client: just the scanners
Server command
npx -y @community-access/accessibility-agents-mcp

Listed in the MCP Registry as io.github.Community-Access/accessibility-agents. The browser scanners need Playwright and axe, which the tools offer to install when they are missing.

Antigravity, or from a checkout
From a clone of the repository
npm install npm run setup -- --dry-run npm run setup

Copies the skills where Codex, Copilot CLI, VS Code, Gemini CLI and Antigravity read them, and writes the hook files. It never overwrites a hooks file or a skill you have edited, and --dry-run shows every step first.

Node 22 or later. Full install guide.

Accessibility Agents questions

I used version 6 or earlier. What changed?

Almost everything under the hood. The per-client agent folders, prompt files and the shell installers are gone; one package of Agent Skills replaces them, installed as a plugin or with npm run setup. The VS Code extension is retired because VS Code installs the package as an agent plugin. The changelog lists every change.

Does any data leave my machine?

Scanning runs on your machine. There is no telemetry, no account and no key, and nothing is sent to the project. The only outbound traffic is what you ask for: the pages you tell the web scanners to load, and the five optional GLOW tools, which send the file you name to the separate GLOW service. See the privacy notice.

Does it work with VS Code?

Yes. VS Code installs it as an agent plugin, and the six entry points appear in the chat slash menu. It also works in Claude Code, GitHub Copilot CLI, Codex, Gemini CLI and Antigravity, and the MCP server works in any MCP client.

What standards do the agents target?

WCAG 2.2 Level AA for web content, with every finding checked against the real criterion list. Documents are checked against WCAG and the Microsoft Accessibility Checker rules, PDFs against PDF/UA through the Matterhorn Protocol, and ePub against EPUB Accessibility. Compliance guidance covers ADA Title II, Section 508, EN 301 549 and VPAT 2.5Rev.

Does this replace manual accessibility testing?

No. Automated tools catch many issues but cannot replace testing with real screen readers, keyboard-only navigation and disabled users. These agents are a strong first pass that keeps accessibility in the loop while code is written.

Is it free?

Yes. Accessibility Agents is open source under the MIT license, free to use, modify and distribute.

Build with us

Every project here takes contributions, and you do not need to write code to make one. The fixes and guidance in the latest Accessibility Agents release came from people who found a real problem and told us.

  • Test with your assistive technology

    Tell us where a screen reader, magnifier, braille display or switch gets stuck. That report is the most valuable thing we receive.

  • Improve a skill or a guide

    Agent skills and documentation are plain Markdown. Fix a rule, add a source, sharpen an explanation.

  • Send a pull request

    Pick an open issue in any repository. Every contributor is credited.

  • Learn first

    New to GitHub? GIT Going with GitHub teaches the whole contribution flow with a screen reader.

AI and automated tools are not perfect. They miss things, make mistakes, and cannot replace testing with real screen readers and assistive technology. Always verify with VoiceOver, NVDA, JAWS, and keyboard-only navigation.