Accessibility MCP

Accessibility MCP

Audits web pages for WCAG 2.2 AA accessibility aligned with the GOV.UK standard using axe-core and headless Chromium, returning structured JSON, markdown reports, and GDS compliance summaries.

Category
访问服务器

README

Accessibility MCP — WCAG 2.2 AA (GOV.UK standard)

A Model Context Protocol server that audits web pages and sites for WCAG 2.2 level AA accessibility, aligned with the GOV.UK / GDS standard that UK public sector bodies are legally required to meet (since 1 October 2024).

It drives a real headless Chromium (via Playwright) and runs up to four independent accessibility enginesaxe-core, pa11y (HTML_CodeSniffer + axe), Lighthouse and IBM Equal Access — layers GOV.UK-specific checks and remediation guidance on top, and returns results as structured JSON, a human-readable Markdown report, and a GDS-style compliance summary.

It can drive interactive journeys (navigate, click, fill, log in) and audit the resulting state, and it exposes one tool per axe-core rule (~100) for fine-grained checks.

Honest by design. Automated testing detects only ~30–40% of WCAG issues. Every report separates automated failures, needs manual review, and passed checks, and any unverified AA criterion keeps the status at "partially compliant". This tool is a starting point for, not a replacement for, a full manual audit.

Tools

Bundled audits (multi-engine):

Tool Description
audit_url Audit one live page; supports engines and interaction steps.
audit_html Audit a raw HTML string / component snippet (no network fetch).
audit_site Crawl a site (same origin) and audit each page; aggregated summary.

Dedicated single-engine audits (take url, html or session_id):

Tool Description
audit_axe axe-core only (plus GOV.UK checks).
audit_pa11y pa11y only (HTML_CodeSniffer + axe runners).
audit_lighthouse Lighthouse accessibility only.
audit_ibm IBM Equal Access only.

Interactive navigation (stateful browser session):

Tool Description
browser_open Open a session; returns a session_id.
browser_navigate / browser_click / browser_fill / browser_wait Drive the page.
browser_snapshot Current url, title and visible text.
audit_current_page Audit the current post-interaction state.
browser_close Close the session.

Automated-check tools (on by default): the machine-testable WCAG surface.

Tool Description
audit_automated_checks Runs every automatable WCAG criterion at once — high-confidence pass/fail.
check_wcag_<n> (e.g. check_wcag_1_4_3) One tool per automatable WCAG criterion.
list_automated_checks WCAG criteria that can be automated, with the axe rules behind each.
list_manual_checks WCAG criteria that cannot be automated and need human review.

Each audit tool takes url, html or session_id. Disable per-criterion tools with ACCESSIBILITY_MCP_AUTOMATED_CHECK_TOOLS=0.

Grouped audit tools (on by default): run a related set of rules at once.

Tool Description
audit_perceivable / audit_operable / audit_understandable / audit_robust All axe rules under a WCAG principle.
audit_group_color, audit_group_forms, audit_group_keyboard, audit_group_aria, audit_group_structure, audit_group_tables, … All axe rules in an axe category.
list_groups Lists every group tool and the rules it runs.

Each takes url, html or session_id. Disable with ACCESSIBILITY_MCP_GROUP_TOOLS=0.

Per-axe-rule tools (~100, on by default): one tool per axe rule, e.g. axe_color_contrast, axe_image_alt, axe_label. Each takes url, html or session_id. Disable with ACCESSIBILITY_MCP_PER_RULE_TOOLS=0.

Catalogue / reporting:

Tool Description
list_engines Available engines and whether the Node runner is installed.
list_wcag_rules WCAG 2.2 criteria checked, with automation coverage.
list_axe_rules All axe rules (each also exposed as its own tool).
generate_accessibility_statement Draft a GOV.UK-format statement from an audit.

Each audit tool returns:

  • json — structured, machine-readable results (violations, severity, WCAG criteria, affected selectors, remediation);
  • markdown_report — a human-readable report grouped by severity;
  • gds_summary — a GOV.UK-flavoured compliant / partially compliant / not compliant summary with reasons;
  • audit_id — pass it to generate_accessibility_statement to reuse the result.

Engines

Choose engines per call via engines=["axe","pa11y","lighthouse","ibm"] (default ["axe"]). Findings from every engine are normalised to a common shape with WCAG criteria and labelled by source, so you can cross-check results.

Engine Language Notes
axe Python (in-process) Deque axe-core, explicit WCAG 2.2 tags. Always available.
pa11y Node HTML_CodeSniffer + axe runners. Replays steps as pa11y actions.
lighthouse Node Google Lighthouse accessibility category. Audits by URL.
ibm Node IBM Equal Access. Needs network egress to its rule archive (cdn.jsdelivr.net); in locked-down networks it returns a structured engine-error instead of crashing the run.

axe runs in-process; the other three run in a Node subprocess (accessibility_mcp/engines_node/). If the Node runner is not installed, those engines report a clear "not installed" error and axe still works.

What it checks

  • Full axe-core WCAG 2.2 rule set (wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa) — contrast, alt text, labels, names, landmarks, etc.
  • pa11y / Lighthouse / IBM — independent rulesets for cross-checking.
  • GOV.UK custom checks — accessibility-statement link presence, "Skip to main content" skip link, a single <main> landmark, and GOV.UK Design System usage.
  • WCAG 2.2 awareness — flags the criteria new in 2.2 (2.4.11, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8) and marks non-automatable criteria as needs manual review rather than silently passing them.

Installation

python -m venv .venv && source .venv/bin/activate
pip install -e .
# Chromium: this server reuses an existing Playwright Chromium if present
# (see configuration), otherwise install one:
playwright install chromium

# Optional — pa11y, Lighthouse and IBM engines (needs Node.js):
bash accessibility_mcp/engines_node/setup.sh

axe-core is vendored in accessibility_mcp/vendor/axe.min.js — no CDN needed. The per-rule tool catalogue (vendor/axe-rules.json) is generated by python scripts/generate_axe_rules.py (only needed when updating axe-core).

The Node engines reuse the same Chromium as axe (no extra browser download). Only axe is required; the others are optional and degrade gracefully if absent.

Running

# Run directly over stdio:
accessibility-mcp
# or
python -m accessibility_mcp.server

Register with an MCP client

Add to your client config (e.g. Claude Desktop claude_desktop_config.json, or the example mcp.json in this repo):

{
  "mcpServers": {
    "accessibility": {
      "command": "accessibility-mcp"
    }
  }
}

If you installed into a virtualenv, point command at that venv's executable, e.g. /path/to/.venv/bin/accessibility-mcp.

Configuration (environment variables)

Variable Default Purpose
ACCESSIBILITY_MCP_CHROMIUM auto-detect Explicit Chromium executable path.
PLAYWRIGHT_BROWSERS_PATH (Playwright default) Searched for an installed Chromium build.
ACCESSIBILITY_MCP_PROXY / HTTPS_PROXY none Outbound proxy for audit_url / audit_site.
ACCESSIBILITY_MCP_PAGE_TIMEOUT_MS 30000 Page load timeout.
ACCESSIBILITY_MCP_MAX_PAGES 20 Default crawl page limit.
ACCESSIBILITY_MCP_MAX_DEPTH 2 Default crawl depth limit.
ACCESSIBILITY_MCP_PER_RULE_TOOLS 1 Register ~100 per-axe-rule tools. Set 0 to disable.
ACCESSIBILITY_MCP_GROUP_TOOLS 1 Register grouped tools (WCAG principle + axe category). Set 0 to disable.
ACCESSIBILITY_MCP_AUTOMATED_CHECK_TOOLS 1 Register per-WCAG-criterion automated-check tools. Set 0 to disable.
ACCESSIBILITY_MCP_NODE auto-detect Path to the Node.js executable for the engine runner.

audit_url / audit_site need outbound network access to the target site. In locked-down environments behind an egress policy, set HTTPS_PROXY (Chromium is pointed at it automatically); audit_html needs no network.

Development

pip install -e ".[dev]"
pytest                 # unit + browser-backed integration tests (local fixtures)

The integration tests drive a real headless Chromium against the HTML fixtures in tests/fixtures/, so they require a working Chromium but no network access.

Architecture

accessibility_mcp/
  server.py            FastMCP entry point — bundled + nav + ~100 per-rule tools
  audit.py             Orchestration (URL / HTML / site / single rule / open page)
  config.py            WCAG tags, engines, browser/proxy/node discovery, limits
  engine/              browser.py, axe_runner.py, crawler.py, node_bridge.py, session.py
  engines_node/        Node runner for pa11y / Lighthouse / IBM (runner.mjs, setup.sh)
  rules/               wcag22.py, govuk_checks.py, remediation.py, normalize.py, axe_rules.py
  reporting/           models.py, builder.py, json/markdown/gds renderers
  vendor/              axe.min.js, axe-rules.json (per-rule catalogue)
scripts/generate_axe_rules.py   Regenerate vendor/axe-rules.json from axe-core

Disclaimer

This server helps identify accessibility problems and draft an accessibility statement. It does not, on its own, establish legal compliance. A full manual audit (keyboard operation, screen-reader testing, focus order, captions, etc.) is required to claim conformance with WCAG 2.2 AA.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选