# ronantakizawa/a11ymcp [Health: Active]

**Category:** 📂 Browser Automation  
**Repository:** https://github.com/ronantakizawa/a11ymcp  
**GitHub Stars:** 94  
**npm Downloads (last month):** 756  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ronantakizawa-a11ymcp

## Description
Web accessibility testing MCP server that analyzes URLs and HTML for WCAG 2.0/2.1/2.2 compliance using axe-core. Tools for color contrast, ARIA validation, and orientation lock detection.

## Tools
Capabilities this server exposes over MCP:

- **test_accessibility** — Test a webpage for accessibility issues using Axe-core
- **test_html_string** — Test an HTML string for accessibility issues
- **get_rules** — Get information about available accessibility rules with optional filtering
- **check_color_contrast** — Check if a foreground and background color combination meets WCAG contrast requirements
- **check_aria_attributes** — Check if ARIA attributes are used correctly in HTML
- **check_orientation_lock** — Check if content forces a specific orientation

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "a11ymcp": {
    "command": "npx",
    "args": ["-y","a11y-mcp-server"]
  }
}
```

## Documentation

## What ronantakizawa/a11ymcp MCP server does

ronantakizawa/a11ymcp MCP server gives language models access to web accessibility checks through the Model Context Protocol. It uses Puppeteer to load and evaluate pages and integrates axe-core for automated rule-based analysis. The server accepts either a public URL or an HTML string, so it can inspect a deployed page or markup that is still being developed.

Results from page and HTML tests are returned as structured JSON. Findings can include violations, impact, descriptions, remediation guidance, related help URLs, affected nodes, pass counts, incomplete checks, and test-engine details. The repository identifies WCAG 2.0, 2.1, and 2.2 tags as supported test targets.

## How it works

The server runs as an MCP process that an MCP-compatible client starts with Node.js and npx. A client sends tool arguments such as a URL, HTML document, WCAG tag list, or viewport dimensions. For URL and HTML testing, the default viewport is 1280 by 800, and callers can provide their own width and height for desktop or mobile-oriented checks.

The accessibility engine is based on axe-core, with browser handling provided by Puppeteer. The project is not an official MCP server from Deque Labs, even though it uses Deque's axe-core tooling.

## Setup and configuration

Node.js 18 or later is required. Add that command to the MCP configuration for the client you use, then restart or reload the client as needed.

Documented client setup examples cover Claude Desktop, Claude Code, VS Code with Copilot, Cursor, and Windsurf. Claude Code can register the server for one project or at user scope, and its `claude mcp list` command can verify registration.

## Tools and capabilities

The available tools are:

- `test_accessibility`: analyzes a URL with optional WCAG tags and viewport dimensions.
- `test_html_string`: analyzes supplied HTML with the same tag and viewport controls.
- `get_rules`: lists axe accessibility rules, optionally filtered by tags; rule entries include identifiers, descriptions, help text, help URLs, and tags.
- `check_color_contrast`: evaluates foreground and background colors, with optional font size and bold-text inputs.
- `check_aria_attributes`: checks ARIA usage in an HTML fragment.
- `check_orientation_lock`: checks HTML for content that forces a specific screen orientation.

Supported examples include tags such as `wcag2a`, `wcag2aa`, `wcag2aaa`, `wcag21a`, `wcag21aa`, `wcag22aa`, and `best-practice`. The contrast tool accepts hexadecimal or RGB color values. The orientation and ARIA tools operate on HTML supplied directly rather than on a URL.

## Limitations and notes

URL testing is described for public pages, while local or unpublished markup can be supplied through the HTML tool. Use the returned violations and affected-node details as input for accessibility remediation, not as a description of every possible accessibility concern.

_Full upstream README: https://allmcps.com/mcp/ronantakizawa-a11ymcp/readme_