Accessibility audit by the agent

Overview

This MCP server lets a coding agent inspect a page, run axe-core checks, exercise keyboard focus and save the findings. The scan_page tool checks WCAG 2.0, 2.1 and 2.2 criteria and Section 508, with an optional annotated screenshot; audit_keyboard, audit_screen_reader, audit_site and scan_page_matrix cover keyboard use, the accessibility tree, several pages and several display variants.

The server also offers browser navigation and interaction tools, and can audit pages behind a login. The README states that automated checks do not certify WCAG compliance and that manual testing is still needed. Reports and screenshots are written to a local output folder.

Highlights

• scan_page runs axe-core on the open page, with filters by WCAG tag, CSS selector or rule, and “needs review” results kept separate from violations.
• Optional annotated screenshot: violating elements are outlined with the rule id (at most 50 elements per scan).
• audit_keyboard and audit_screen_reader save JSON reports; audit_site crawls several internal pages; scan_page_matrix compares variants (mobile, desktop, forced colours, reduced motion, 200% zoom).
• Audits pages behind a login, through an interactive session or a reusable storage state.
• Usable as a stdio MCP server, as an interactive REPL in the terminal, or through a Docker image.

Who it is for

For developers and teams who want automated accessibility checks in their workflow with a coding agent, alongside manual testing.

Installation

Install Google Chrome, then the npm package (with the --allow-scripts=re2 option), then declare a stdio server named accessibility-scanner in the client’s MCP configuration and restart it. A Docker image that includes Chromium also exists.

npm install -g mcp-accessibility-scanner --allow-scripts=re2

docker pull justasmonkev/mcp-accessibility-scanner

claude mcp add mcp-accessibility-scanner -s user -- docker run -i --rm justasmonkev/mcp-accessibility-scanner

Read the README on GitHub

Points of attention

• Automated checks do not certify WCAG compliance; audit_screen_reader inspects the browser’s accessibility tree and does not test with an actual screen reader.
• Google Chrome must be installed before the first audit (the npm package does not install a browser), and the native re2 dependency needs the --allow-scripts=re2 option with npm 12.
• The HTTP transport in the Docker Compose setup is unauthenticated: it is published on 127.0.0.1 only and must not be exposed to untrusted networks.

Can an agent use it?

Agent-ready

The repository is an MCP server and contains several agent-oriented files: SKILL.md, AGENTS.md, CLAUDE.md, .mcp.json and a .codex folder. The SKILL.md tells agents to use the CLI in interactive mode rather than the MCP server mode.