Web Accessibility-Testing MCP Server (A11y MCP)

by ronantakizawa

89 stars
359 downloads
Not rated
GitHub Website

About

Test web pages and HTML for accessibility issues and WCAG compliance using Axe-core and Puppeteer.

Details

Author
ronantakizawa
GitHub stars
89
Downloads
359
Categories
Developer Tools, Automation, Other

- Test any public URL for accessibility issues.
- Test raw HTML strings for accessibility issues.
- Check content against WCAG 2.0, 2.1, and 2.2 standards.
- Explore and filter available accessibility rules.
- Analyze color combinations for WCAG contrast compliance.
- Validate correct usage of ARIA attributes.
- Detect content that forces specific screen orientations.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Web Accessibility-Testing MCP Server (A11y MCP)
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Install Node.js 18 or later, then configure the server in your MCP-compatible client (e.g., Claude Desktop, Claude Code, VS Code, Cursor, Windsurf) by adding "command": "npx", "args": ["-y", "a11y-mcp-server"] to the client's MCP configuration.

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 / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "web accessibility-testing mcp server (a11y mcp)": {
            "a11y-accessibility": {
                "command": "npx",
                "args": [
                    "-y",
                    "a11y-mcp-server"
                ]
            }
        }
    }
}

McpServers

{
    "a11y-accessibility": {
        "command": "npx",
        "args": [
            "-y",
            "a11y-mcp-server"
        ]
    }
}

Web Accessibility-Testing MCP Server (A11y MCP)

<a href="https://www.producthunt.com/products/web-accessibility-testing-mcp?embed=true&utm_source=badge-featured&utm_medium=badge&utm_campaign=badge-web-accessibility-testing-mcp" target="_blank" rel="noopener noreferrer">Web Accessibility Testing MCP - Give LLMs access to web accessibility testing APIs | Product Hunt</a>

MseeP.ai Security Assessment Badge

Verified on MseeP

<a href="https://glama.ai/mcp/servers/@ronantakizawa/a11ymcp">

</a>

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

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.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
- Linux: ~/.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-server

This 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-server

Verify the server is registered:

claude mcp list

> Note: 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 |
|-----------|----------|-------------|
| url | Yes | The URL of the web page to test |
| tags | No | Array of WCAG tags to test against (e.g., ["wcag2aa"]) |
| width | No | Viewport width in pixels (default: 1280) |
| height | 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 |
|-----------|----------|-------------|
| html | Yes | The HTML content to test |
| tags | No | Array of WCAG tags to test against (e.g., ["wcag2aa"]) |
| width | No | Viewport width in pixels (default: 1280) |
| height | No | Viewport height in pixels (default: 800) |

Example — default viewport:

{
  "html": "<div></div>",
  "tags": ["wcag2aa"]
}

Example — mobile viewport:

{
  "html": "<div></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 |
|-----------|----------|-------------|
| tags | No | Filter rules by tags (e.g., ["wcag2a", "wcag2aa", "best-practice"]) |

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 |
|-----------|----------|-------------|
| foreground | Yes | Foreground color (e.g., "#000000", "rgb(0,0,0)") |
| background | Yes | Background color (e.g., "#FFFFFF", "rgb(255,255,255)") |
| fontSize | No | Font size in pixels (default: 16) |
| isBold | 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 |
|-----------|----------|-------------|
| html | 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 |
|-----------|----------|-------------|
| html | 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 |
|-----|-------------|
| wcag2a | WCAG 2.0 Level A |
| wcag2aa | WCAG 2.0 Level AA |
| wcag2aaa | WCAG 2.0 Level AAA |
| wcag21a | WCAG 2.1 Level A |
| wcag21aa | WCAG 2.1 Level AA |
| wcag22aa | WCAG 2.2 Level AA |
| best-practice | Best practices (not strictly WCAG) |

Dependencies

- @modelcontextprotocol/sdk
- puppeteer
- @axe-core/puppeteer
- axe-core

License

MIT

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.