MCP.Market

Wcag Accessibility MCP server

by aditya-ariosity·io.github.aditya-ariosity/wcag-accessibility·v0.1.6·1 stars
No reviews yet

A WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits.

C65/100grade C
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
Growing

1 stars64 downloads/wk

Reviews

Write one

Nobody has reviewed Wcag Accessibility yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Wcag Accessibility tools (7)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit_file

    Render a local .html or .htm file beneath the configured allowed root and return accessibility findings and corrections. Read-only.

  • audit_html

    Render supplied HTML in an isolated headless browser and return WCAG findings plus evidence and suggested corrections. Use for generated UI before it is hosted. Read-only.

  • audit_url

    Load a public or local web page in headless Chromium, run axe-core, and return prioritized WCAG findings, DOM evidence, computed styles, and contrast corrections. Read-only.

  • check_contrast

    Calculate the WCAG contrast ratio for foreground and background colors and determine whether the pair passes for the supplied text size and weight.

  • explain_issue

    Return implementation-focused remediation steps and the axe rule reference for a rule ID found in an audit.

  • get_wcag_checklist

    Return every success criterion required by a WCAG 2.0, 2.1, or 2.2 A/AA/AAA profile, with W3C references, axe rule mappings, and explicit automated-partial versus manual coverage. Use this to plan the checks that a browser audit cannot complete.

  • suggest_contrast_fix

    Find the nearest black-or-white-directed foreground or background adjustment that reaches the selected WCAG contrast threshold. Returns a mathematical candidate, not an automatic edit.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan19 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancerepository not readable: repo not found3/15
  • Maintainer identityno repository or website to verify2/10
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Wcag Accessibility compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 20% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
64
more than 51% of 12,191 servers with a package

What its tools let an agent do: 7 read

Install Wcag Accessibility in Claude Code, Cursor or VS Code

Runs npx -y wcag-accessibility-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add wcag-accessibility -- npx -y wcag-accessibility-mcp
Add to Cursor

What the publisher says

From the Wcag Accessibility repository's README, as published. We do not edit it. Read it on GitHub

WCAG Accessibility MCP

A WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits.

WCAG Accessibility MCP gives AI coding and design agents a real accessibility feedback loop. It renders web interfaces in Chromium, runs axe-core, checks color contrast, maps findings to WCAG guidance, and returns structured evidence that an agent can use to fix accessibility issues before a UI is treated as complete.

It is designed for people building with AI: product designers, design engineers, frontend developers, AI product teams, and anyone using agents to generate or review web interfaces.

This is an automated testing aid, not a WCAG certification service. It catches many common failures, but full accessibility review still requires human testing for keyboard behavior, focus order, screen readers, zoom, motion, content quality, and assistive-technology behavior.

Why This Exists

AI-generated interfaces often look polished but fail basic accessibility checks: weak contrast, missing labels, broken semantic structure, poor ARIA usage, inaccessible forms, and hidden keyboard issues.

This MCP helps agents stop guessing. Instead of saying “follow WCAG,” it gives them testable feedback:

  • what failed
  • where it failed
  • which element was affected
  • which WCAG-related rule applies
  • what needs to be fixed
  • which checks still require manual review

What It Can Do

Standards Coverage

The server supports these profiles:

  • wcag2a
  • wcag2aa
  • wcag2aaa
  • wcag21aa
  • wcag21aaa
  • wcag22aa
  • wcag22aaa
  • best-practice

AA profiles include Level A and AA criteria. AAA profiles include Level A, AA, and AAA criteria.

The default profile is wcag22aa.

For WCAG 2.2:

  • AA includes 55 required success criteria.
  • AAA includes 86 required success criteria.

An automated axe mapping means partial automated coverage. It does not mean the whole WCAG success criterion has been fully tested.

Install

Requirements:

  • Node.js 20 or newer
  • Chrome or Edge recommended
  • Windows, macOS, or Linux

Install from npm:

npm install -g wcag-accessibility-mcp

Or run directly:

npx -y wcag-accessibility-mcp

If the server starts correctly, you should see:

wcag-accessibility-mcp is running over stdio

Use With Claude Code

Add the MCP server:

claude mcp add --scope user wcag-accessibility -- npx -y wcag-accessibility-mcp

Check that it is connected:

claude mcp list

Test prompt:

Use the wcag-accessibility MCP tool check_contrast. Check #999999 on #ffffff for WCAG AA normal text. Do not calculate manually.

Expected result:

The contrast ratio is about 2.85:1, which fails WCAG AA for normal text.

Use With Claude Desktop

Open the Claude desktop config file on Windows:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-03downgradeA → Cscore 65

Wcag Accessibility: common questions

Is Wcag Accessibility MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Wcag Accessibility safety report
How do I install Wcag Accessibility?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Wcag Accessibility need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Wcag Accessibility maintained?
The last commit was 65 days ago (2026-08-31). The latest release is v0.1.6.
How does Wcag Accessibility compare with other MCP servers?
safety score 65/100 (higher than 20% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.