accessibility-scanner-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@accessibility-scanner-mcpAudit https://example.com for accessibility issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
accessibility-scanner-mcp
An MCP server that lets an AI agent scan a web page for WCAG accessibility issues and get back findings it can act on. The agent calls one tool with a URL; it gets every violation grouped by severity, each with the exact element selector, the offending HTML, the specific failure, the WCAG success criterion, and a fix-guide link — plus the items that still need human review.
It runs the real axe-core engine in your local Chrome
(via playwright-core), so nothing about the pages you scan leaves your machine. It scrolls the page
first so lazy-loaded content is actually checked rather than silently skipped, and it resolves
color contrast over CSS gradients, which most tools leave as "needs review."
Upgrading from 0.1.x? 0.2.0 sees more of each page and returns more findings for the same URL. See CHANGELOG.md.
Part of accessibilityscanner.app.
Requirements
Node.js 18+
Google Chrome installed (or set the
CHROME_PATHenvironment variable to a Chromium binary)
Related MCP server: A11y Expert MCP
Install
Add it to your MCP client's config. No global install needed — npx fetches it on first run.
Claude Desktop (claude_desktop_config.json), Cursor, Claude Code, or any MCP client:
{
"mcpServers": {
"accessibility-scanner": {
"command": "npx",
"args": ["-y", "accessibility-scanner-mcp"]
}
}
}If Chrome is not auto-detected, add an env block:
{
"mcpServers": {
"accessibility-scanner": {
"command": "npx",
"args": ["-y", "accessibility-scanner-mcp"],
"env": { "CHROME_PATH": "/usr/bin/google-chrome" }
}
}
}The tool
scan_accessibility
Input | |
| The http(s) URL to scan. |
Returns a report grouped by severity. For each rule: the WCAG criterion, a fix-guide link, and per element the selector, HTML, and exact failure. Example flow with an agent:
You: Audit https://example.com for accessibility and fix what you can. Agent: (calls
scan_accessibility) → reads the findings → edits the code → re-scans.
Honest about limits
Automated testing covers the machine-checkable subset of WCAG (most of the issues on a typical page, but not all of it). Items that need human judgement are returned under "Needs manual review." It never claims a page is "compliant."
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
- RampifyOAuthdev.rampify
SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent.
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables LLMs to perform web accessibility testing against WCAG standards using Deque Axe-core API and Puppeteer.6140 npm91MIT
- AlicenseAqualityDmaintenanceAn accessibility expert MCP server that provides AI coding assistants with real-time access to WAI-ARIA patterns, code review, contrast checking, and WCAG guidance for writing accessible code from the start.4MIT

@accesslint/mcpofficial
AlicenseAqualityFmaintenanceAn MCP server for WCAG accessibility auditing in AI coding agents, providing tools to audit HTML, files, URLs, and diffs, plus a prompt for React component auditing.5711 npm6MIT- AlicenseAqualityDmaintenanceAn MCP server for web accessibility testing that enables scanning, auditing, and fixing WCAG, ADA, and other compliance issues directly from your IDE, with free local scans, AI-generated framework-aware fixes, and verification capabilities.1474 npmMIT