A11Y Toolkit

a11y-toolkit — the accessibility layer for AI coding agents

🌐 English · Español

WCAG 2.2 for your coding agent — audit, fix, document and watch. Zero dependencies, es/en.

37 MCP tools, 5 prompts and a skill covering the whole WCAG 2.2 loop: audit, fix, document, watch, hand off — and now blindfold usability testing, where the agent attempts real tasks perceiving only what a screen reader exposes. 51 of 55 A/AA criteria carry automated signals (93%), every finding ships with a concrete remediation your agent can apply, and the rendered tools run on whichever browser you have — Chromium, Firefox, WebKit, Chrome or Edge.

The European Accessibility Act is in force since June 2025, ADA suits keep landing, and AI agents now write most of the web. A scan is not a defence: the machine finds, the human signs.

Quickstart

# MCP — one line, any MCP client (Claude, Cursor, Codex, Windsurf, …)

claude mcp add a11y-toolkit -- uvx --from a11y-toolkit a11y-toolkit-mcp

CLI — same engine, one command

pip install a11y-toolkit a11ytoolkit audit --url https://example.com a11ytoolkit pair "#1f2328" "#fbfaf7"

Static audits, contrast math, PDF/DOCX screening and the evidence pack run with zero dependencies. The rendered tools (real contrast over images, keyboard traps, reflow, forms) additionally need Playwright: pip install playwright && playwright install chromium.

Features

The tools (37)

Full reference — descriptions, arguments, return shapes and behavior — in docs/tools.md. All tools accept lang (en|es) unless noted; output is JSON unless noted. Generated from server.TOOLS by scripts/gen_readme.py.

The 5 prompts

• `audit-page` (url*, language): Full accessibility audit workflow for a URL: automated tools + what to verify manually (keyboard, screen reader, zoom). Every prompt exists in English and Spanish.

• `fix-contrast` (fg*, bg*, context): Guided contrast fix: verify the pair (or the text-over-image region), get the nearest passing color, apply it to the code. Every prompt exists in English and Spanish.

• `pre-deploy-check` (url*, baseline): Pre-deploy regression check: express audit of the URL plus snapshot diff against a baseline snapshot. Every prompt exists in English and Spanish.

• `declaration-eaa` (entity*, url*, status): Generate a European Accessibility Act / RD 1112/2018 accessibility statement, collecting any missing legal fields from the user. Every prompt exists in English and Spanish.

• `blindfold-task` (url*, goal*, kind, language): Blindfold usability test — the agent attempts a real task perceiving ONLY the accessibility tree and acting only by accessible name and keyboard, logging friction per step; closes with a11y_journey_verdict. The capability no other accessibility tool has: task-based non-visual testing where the agent IS the screen-reader user. Every prompt exists in English and Spanish.

Install

mcp-name: io.github.kinti/a11y-toolkit · PyPI: a11y-toolkit · Zenodo DOI: 10.5281/zenodo.22843722

Works with any MCP-capable client — Claude Code/Desktop, Cursor, Windsurf, VS Code, Codex CLI, OpenCode, ZCode, Zed, Cline, Continue, Kimi Code… See docs/clients.md for every verified config format. Node-native? npx -y @kinti/a11y-toolkit mcp… — the npm launcher runs the same engine (npm/). Composing it with the popular servers (Playwright, GitHub, Filesystem, Fetch…) — docs/interop.md. Start-to-finish recipes (audit → fix → seal → CI): docs/cookbook.md.

claude mcp add a11y-toolkit -- uvx --from a11y-toolkit a11y-toolkit-mcp

Or with JSON config:

{

"mcpServers": { "a11y-toolkit": { "command": "uvx", "args": ["--from", "a11y-toolkit", "a11y-toolkit-mcp"], "timeoutMs": 60000 } } }

Rendered tools use Playwright if present and accept a browser parameter (auto, chromium, firefox, webkit, chrome, msedge — auto-detects the first available). Accept auth_state (Playwright storage_state path) to audit behind login. Everything else works with zero dependencies.

The skill

git clone https://github.com/kinti/a11y-toolkit && cd a11y-toolkit

./skills/install-skill.sh # → ~/.zcode