MCP WCAG Analyzer & Refactor

A React developer opens a ticket: "fix accessibility issues on the checkout component." She runs a generic linter and gets a list of HTML violations. The fixes assume vanilla markup. Her component has eighteen props, three custom hooks, and an internal state machine. The HTML she's looking at exists for about four milliseconds before React replaces it. None of the suggested fixes apply cleanly to her actual code.

mcp-wcag-accessibility, by alexanderuk82, exists for that developer. It's an MCP server that runs WCAG 2.0, 2.1, and 2.2 analysis and — critically — produces remediation in the language of your actual framework. HTML is supported. So is React. So is Vue. So is Angular. When you ask the AI to fix the issues it found, the suggestions arrive as JSX, single-file components, or template syntax, with the right props and the right idioms.

It's also fully local and free. There's no API key, no usage cap, no third-party telemetry sending your code to a SaaS. The analysis runs on your machine, against your code, and the remediation flows back into your editor through the AI you already use. For teams that can't send proprietary code to external services for compliance reasons, this is a real-world alternative.

The audience hook is for front-end developers working in component frameworks who want a11y fixes that match their stack. Not "wrap this <div> in an <button>" — but "this Button component should accept an aria-label prop and pass it through, and here's the diff."

Made by alexanderuk82 and published openly. The <span class="whitespace-nowrap">a-gnt</span> Community catalogs it because most accessibility tooling ignores the framework reality of modern front-end work, and this server doesn't.

Pair with The Design Systems Zealot when fixes reveal systemic component problems, or The Design Handoff Assistant for the spec-to-code translation.