PluginPartly tested (needs an account)

Check websites and files for access

Accessibility Agents

A free MIT plugin that checks web pages, Word, PDF and markdown files against WCAG 2.2 AA and blocks page edits until an access review has run.

Works with
Claude Code, Codex CLI, Gemini CLI
Good for
Web developers, Daily work and research

What it does

Accessibility means people with disabilities can use your site: screen-reader users, keyboard-only users and people with low vision. AI assistants often forget this when they write code. Accessibility Agents adds a team of checkers that test your work against WCAG 2.2 AA, the common standard.

Six entry skills cover web pages (buttons, forms, colour contrast, headings, keyboard use), Office files, PDFs and ePub books, markdown documents, desktop apps and GitHub work. They call about a hundred specialist skills when needed. Findings are saved in a fixed format and turned into a report with a score, so you can see if things got better since the last run.

It also has a guard. While the plugin is on, your assistant cannot change a user-facing page until the accessibility lead has reviewed the work. Scanning runs on your computer, except for the five optional GLOW tools, which send files to an outside service.

Example prompts

  • "Check my contact page for accessibility problems and explain each one in plain words."
  • "Audit this whole site for WCAG 2.2 AA and write a report."
  • "Is this PDF accessible for screen-reader users? brochure.pdf"
  • "Check the alt text and heading order in my README."

How to install

/plugin marketplace add Community-Access/accessibility-agents
/plugin install accessibility-agents@community-access

How to use it

Describe the problem, for example: Check this sign-up form for accessibility problems. The accessibility-lead skill picks the right specialist and reports findings against WCAG 2.2.

Check it works

Restart Claude Code after the install and run /plugin; accessibility-agents should show as installed. Run /mcp and check that the accessibility-agents server is connected. Then ask it to review a small HTML file. The accessibility-lead skill should answer with findings that name WCAG criteria.

Common problems

Other assistants

  • Codex: codex plugin marketplace add Community-Access/accessibility-agents then codex plugin add accessibility-agents@community-access. This gives the skills and the MCP server only, with no edit gate — https://github.com/Community-Access/accessibility-agents/blob/7597f1a2cd315f144bc6a212ecceabf0268ea044/README.md
  • Gemini CLI: gemini extensions install https://github.com/Community-Access/accessibility-agents (the same line is in the Gemini extensions gallery). From 7.1.0 it uses the archive attached to the release, which holds the skills, the AGENTS.md context file, the MCP server and Gemini hooks for the edit gate. The gallery card is out of date: it still shows 6.0.0 and "eighty agents" — https://geminicli.com/extensions/

What to watch out for

  • Hooks on seven Claude Code events run node hooks/guard.mjs on your computer. Before every Edit, Write, NotebookEdit, MultiEdit, apply_patch or Bash call it refuses a change to a user-facing file (HTML, JSX, CSS and similar, including shell writes such as sed -i, redirects and heredocs) until the accessibility-lead skill has run, and a Stop hook refuses to end a turn that edited UI without a review (hooks/hooks.json at commit 7597f1a)
  • Once per session a UserPromptSubmit hook adds a short reminder (about 60 words) to the conversation that tells the assistant to hand UI work to the accessibility lead. The hook keeps small marker files in your system temp folder (a11y-agents-guard) and makes no network calls
  • The plugin starts a local MCP server (node mcp-server/dist/stdio.mjs, needs Node.js 22 or newer). Five of its tools use an outside service: glow_health_check sends a GET to https://letitglow.app/mcp/health, and glow_audit_document, glow_fix_document, glow_convert_document and glow_generate_report upload the whole file you name (markdown, HTML or .docx) to letitglow.app/mcp, with no key. The GLOW_API_BASE_URL variable or a baseUrl argument changes the address. Use them only on files you may share
  • The web scanners open the URLs you give them in a local Playwright browser, which also loads that page's own scripts and trackers. Playwright, @axe-core/playwright, pdf-lib and the veraPDF CLI are optional extra installs. The MCP server writes .a11y-cache.json and .a11y-history/ in your project when you ask it to keep history. The README and PRIVACY.md say there is no telemetry, account or key
  • In Codex the plugin route loads only the skills and the MCP server, with no edit gate. The README's gate route for Codex is a git checkout, then npm install and npm run setup, which copies the skills to ~/.agents/skills and writes or merges ~/.codex/hooks.json; run npm run setup -- --dry-run first to see every change

Licence and author

Licence
MIT
Author
Community Access
Source code
github.com/Community-Access/accessibility-agents

How we tested it

We installed it on an empty test computer on 3 Nov 2026. Partly tested: installed in a clean test system, but its main features need an account or key we did not use.

Test level
Technical details of the test
Date
3 Nov 2026
Method
Reviewed by our team against the repository, its README and docs.

Checked again on 3 Nov 2026

Alternatives

  • Chrome DevTools MCP — lets your assistant inspect a live page, including Lighthouse checks, but has no WCAG specialists
  • Web Quality Skills — audits speed, accessibility and SEO together, with less depth on accessibility
  • Modern Web Guidance — web-platform advice skills; accessibility is one topic among many

FAQ

  • Q: Does it make my site legally compliant? A: No tool can promise that. It finds and explains WCAG problems; a person still needs to check with real assistive technology.
  • Q: Do I need an account or key? A: No. The README and PRIVACY.md say there is no account, key or telemetry.
  • Q: Does it send my files anywhere? A: Only the GLOW tools send the file you name to letitglow.app. The web scanners load the pages you ask them to check. Everything else runs on your computer.
  • Q: Can I turn the edit gate off? A: The gate is part of the plugin. To stop it, disable the plugin in /plugin for that project.

Sources

  • github.com/Community-Access/accessibility-agents
  • github.com/Community-Access/accessibility-agents/tree/7597f1a2cd315f144bc6a212ecceabf0268ea044
  • github.com/Community-Access/accessibility-agents/blob/7597f1a2cd315f144bc6a212ecceabf0268ea044/README.md
  • github.com/Community-Access/accessibility-agents/blob/7597f1a2cd315f144bc6a212ecceabf0268ea044/hooks/hooks.json
  • github.com/Community-Access/accessibility-agents/blob/7597f1a2cd315f144bc6a212ecceabf0268ea044/hooks/guard.mjs
  • github.com/Community-Access/accessibility-agents/blob/7597f1a2cd315f144bc6a212ecceabf0268ea044/mcp-server/tools/glow-tools.js
  • github.com/Community-Access/accessibility-agents/blob/7597f1a2cd315f144bc6a212ecceabf0268ea044/PRIVACY.md
  • github.com/Community-Access/accessibility-agents/releases/tag/v7.1.0
  • npmjs.com/package/@community-access/accessibility-agents-mcp
  • geminicli.com/extensions/