A11y MCP Server
The A11y MCP Server enables LLMs to perform comprehensive web accessibility testing using Axe-core and Puppeteer. Key capabilities include:
Test live web pages - Analyze any public URL for accessibility issues and WCAG compliance violations
Test HTML snippets - Evaluate raw HTML strings for accessibility problems without needing a live URL
WCAG compliance testing - Check content against various WCAG standards (2.0, 2.1, 2.2 at levels A, AA, AAA) with customizable tag filtering
Color contrast analysis - Verify if foreground/background color combinations meet WCAG contrast requirements for different font sizes and weights
ARIA attribute validation - Ensure ARIA attributes are being used correctly in HTML content
Orientation lock detection - Identify if content forces specific screen orientations (portrait/landscape)
Rule exploration - Get detailed information about available Axe-core accessibility rules with optional filtering
Detailed violation reports - Receive comprehensive JSON-formatted results including violations, passes, affected nodes, impact levels, descriptions, and remediation guidance
Click on "Install 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., "@A11y MCP Servertest our homepage https://example.com for WCAG 2.1 compliance"
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.
Web Accessibility-Testing MCP Server (A11y MCP)
https://github.com/user-attachments/assets/316c6d44-e677-433e-b4d5-63630b4bab2b
A11y MCP is an MCP (Model Context Protocol) server that gives LLMs access to web accessibility testing APIs.
This server uses the Deque Axe-core API and Puppeteer to allow LLMs to analyze web content for WCAG compliance and identify accessibility issues.
Note: This is not an official MCP server from Deque Labs.
Features
Test web pages: Test any public URL for accessibility issues with customizable viewport dimensions
Test HTML snippets: Test raw HTML strings for accessibility issues
WCAG compliance testing: Check content against various WCAG standards (2.0, 2.1, 2.2)
Customizable tests: Specify which accessibility tags/standards to test against
Rule exploration: Get information about available accessibility rules
Color contrast analysis: Check color combinations for WCAG compliance
ARIA validation: Test proper usage of ARIA attributes
Orientation lock detection: Identify content that forces specific screen orientations
Related MCP server: @accesslint/mcp
Installation
Prerequisites
Node.js 18 or later
An MCP-compatible client (Claude Desktop, Claude Code, VS Code, Cursor, etc.)
Claude Desktop
Edit your MCP configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Add the server to the mcpServers object:
{
"mcpServers": {
"a11y-accessibility": {
"command": "npx",
"args": ["-y", "a11y-mcp-server"]
}
}
}Claude Code (CLI)
claude mcp add a11y-accessibility -- npx -y a11y-mcp-serverThis registers the server for the current project. To make it available across all projects:
claude mcp add --scope user a11y-accessibility -- npx -y a11y-mcp-serverVerify the server is registered:
claude mcp listNote: MCP tools become available after restarting your Claude Code session.
VS Code (Copilot)
Add to your VS Code settings.json or .vscode/settings.json:
{
"mcp": {
"servers": {
"a11y-accessibility": {
"command": "npx",
"args": ["-y", "a11y-mcp-server"]
}
}
}
}Cursor
Add to your Cursor MCP configuration (.cursor/mcp.json):
{
"mcpServers": {
"a11y-accessibility": {
"command": "npx",
"args": ["-y", "a11y-mcp-server"]
}
}
}Windsurf
Add to your Windsurf MCP configuration (~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": {
"a11y-accessibility": {
"command": "npx",
"args": ["-y", "a11y-mcp-server"]
}
}
}Available Tools
test_accessibility
Tests a URL for accessibility issues.
Parameters:
Parameter | Required | Description |
| Yes | The URL of the web page to test |
| No | Array of WCAG tags to test against (e.g., |
| No | Viewport width in pixels (default: 1280) |
| No | Viewport height in pixels (default: 800) |
Example — desktop viewport (default):
{
"url": "https://example.com",
"tags": ["wcag2aa"]
}Example — mobile viewport (iPhone 12/13):
{
"url": "https://example.com",
"tags": ["wcag2aa"],
"width": 390,
"height": 844
}test_html_string
Tests an HTML string for accessibility issues.
Parameters:
Parameter | Required | Description |
| Yes | The HTML content to test |
| No | Array of WCAG tags to test against (e.g., |
| No | Viewport width in pixels (default: 1280) |
| No | Viewport height in pixels (default: 800) |
Example — default viewport:
{
"html": "<div><img src='image.jpg'></div>",
"tags": ["wcag2aa"]
}Example — mobile viewport:
{
"html": "<div><img src='image.jpg'></div>",
"tags": ["wcag2aa"],
"width": 375,
"height": 812
}get_rules
Get information about available accessibility rules with optional filtering. Returns an array of rule objects, each containing ruleId, description, help, helpUrl, and tags.
Parameters:
Parameter | Required | Description |
| No | Filter rules by tags (e.g., |
Example — filter rules by WCAG 2.1 AA:
{
"tags": ["wcag21aa"]
}Example — get all rules (no filter):
{}check_color_contrast
Check if a foreground and background color combination meets WCAG contrast requirements.
Parameters:
Parameter | Required | Description |
| Yes | Foreground color (e.g., |
| Yes | Background color (e.g., |
| No | Font size in pixels (default: 16) |
| No | Whether the text is bold (default: false) |
Example:
{
"foreground": "#777777",
"background": "#EEEEEE",
"fontSize": 16,
"isBold": false
}check_aria_attributes
Check if ARIA attributes are used correctly in HTML.
Parameters:
Parameter | Required | Description |
| Yes | HTML content to test for ARIA attribute usage |
Example:
{
"html": "<div role='button' aria-pressed='false'>Click me</div>"
}check_orientation_lock
Check if content forces a specific orientation.
Parameters:
Parameter | Required | Description |
| Yes | HTML content to test for orientation lock issues |
Example:
{
"html": "<html><head><meta name='viewport' content='width=device-width, orientation=portrait'></head><body>Content</body></html>"
}Response Format
The server returns accessibility test results in structured JSON:
{
"violations": [
{
"id": "color-contrast",
"impact": "serious",
"description": "Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds",
"help": "Elements must meet minimum color contrast ratio thresholds",
"helpUrl": "https://dequeuniversity.com/rules/axe/4.10/color-contrast",
"affectedNodes": [
{
"html": "<div style=\"color: #aaa; background-color: #eee;\">Low contrast text</div>",
"target": ["div"],
"failureSummary": "Fix any of the following: Element has insufficient color contrast of 1.98 (foreground color: #aaa, background color: #eee, font size: 12.0pt, font weight: normal)"
}
]
}
],
"passes": 1,
"incomplete": 0,
"inapplicable": 2,
"timestamp": "2025-04-25T16:45:33.655Z",
"url": "about:blank",
"testEngine": {
"name": "axe-core",
"version": "4.10.3"
}
}WCAG Tags Reference
Common tags you can use with the tags parameter:
Tag | Description |
| WCAG 2.0 Level A |
| WCAG 2.0 Level AA |
| WCAG 2.0 Level AAA |
| WCAG 2.1 Level A |
| WCAG 2.1 Level AA |
| WCAG 2.2 Level AA |
| Best practices (not strictly WCAG) |
Dependencies
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP (Model Context Protocol) server for performing accessibility audits on webpages using axe-core. Use the results in an agentic loop with your favorite AI assistants (Cline/Cursor/GH Copilot) and let them fix a11y issues for you!Last updated243548Mozilla Public 2.0

@accesslint/mcpofficial
Alicense-qualityFmaintenanceAn 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.Last updated5246MIT- Alicense-qualityAmaintenanceAn MCP server that lets an AI agent scan a web page for WCAG accessibility issues and get back findings it can act on.Last updated195MIT
- AlicenseAqualityBmaintenanceMCP server for axe-core accessibility audits. Enables scanning URLs or HTML for WCAG violations with impact levels and fix guidance.Last updated4201MIT
Related MCP Connectors
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
MCP server for Pentest-Tools.com: run scans, manage findings and reports via your preffered LLM.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ronantakizawa/a11ymcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server