How to Use the Accessibility Prover MCP in Claude

Stop shipping broken UIs. Use the Accessibility Prover MCP Server to force Claude Desktop to write compliant code before you commit.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Accessibility Prover MCP to Claude Desktop

Create your Vinkius account to connect Accessibility Prover to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Accessibility Prover with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Validate semantic markup in Claude Desktop

The `validate_accessibility` tool forces Claude Desktop to audit your HTML landmarks and form labels against WCAG 2.2 AA standards. It rejects non-semantic layouts that fail to map elements correctly. Your agent checks for keyboard tab order and focus indicators before generating the final component. This stops focus trap failures during the initial drafting phase.

Enforce contrast ratios for Claude Desktop

You can rely on `validate_accessibility` to flag insufficient contrast ratios before they make it into your CSS files. The tool mandates specific numerical values like 4.5:1 for text elements. It also reviews your motion media queries to ensure users with vestibular disorders aren't triggered by transitions. Your UI design gets a hard pass or fail based on these technical constraints.

Define ARIA and motion specs in Claude Desktop

Every modal or interactive element must include explicit ARIA labels when processed through `validate_accessibility`. The tool verifies that your code handles screen readers properly. It forces the inclusion of `prefers-reduced-motion` overrides for all animated transitions. This ensures your components adhere to EAA 2025 requirements immediately.

Setup guide

Set up Accessibility Prover MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Accessibility Prover MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Accessibility Prover MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under accessibility-prover-mcp.

json

{
  "mcpServers": {
    "accessibility-prover-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Accessibility Prover. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Accessibility Prover now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Accessibility Prover MCP in Claude Desktop

It acts as a technical gatekeeper for your UI code. You call the tool to verify semantic structure and contrast before Claude Desktop pushes the final block to your file.

Yes, you connect it via the config file or extensions menu. Once active, Claude Desktop treats accessibility checks as a mandatory step in the coding process.

The server identifies contrast and motion risks, forcing the agent to rewrite the CSS. You get actionable feedback on specific ratios and media query failures.

It runs as a local subprocess, so latency is non-existent. You get immediate validation results the moment the agent processes your component.

Your UI markup stays local to your machine when using the stdio transport. The server only touches the DOM structure and CSS properties you choose to submit for audit.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript