Web Accessibility-Testing MCP Server

Created By
ronantakizawaa year ago
MCP server for testing accessibility on websites
Overview

What is AccessibilityMCP?

AccessibilityMCP is a Model Context Protocol (MCP) server designed for testing the accessibility of websites and HTML content using the Deque Axe-core API.

How to use AccessibilityMCP?

To use AccessibilityMCP, install it globally via npm and run the server. You can then test public URLs or raw HTML strings for accessibility issues.

Key features of AccessibilityMCP?

  • Automated testing of web pages for accessibility issues.
  • WCAG compliance testing against standards 2.0, 2.1, and 2.2.
  • Customizable tests for specific accessibility tags.
  • Color contrast analysis and ARIA validation.
  • Orientation lock detection for content.

Use cases of AccessibilityMCP?

  1. Testing websites for compliance with accessibility standards.
  2. Analyzing HTML snippets for accessibility issues.
  3. Ensuring color contrast meets WCAG requirements.

FAQ from AccessibilityMCP?

  • Can AccessibilityMCP test any website?

Yes! It can test any public URL for accessibility issues.

  • Is there a command-line interface?

Yes! You can run it as a command-line tool after installation.

  • What standards does it check against?

It checks against WCAG 2.0, 2.1, and 2.2.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ronantakizawa
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Voyei

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago