GitScrum/MCP Partner Directory/Accessibility Prover MCP

Official Vinkius Partner Grade A+ · 1 tools

Accessibility Prover MCP + Claude: Guarantee WCAG Compliance Upfront.

You don't have time for costly production audits. When you connect Accessibility Prover to your GitScrum board, Claude acts as a proactive quality gate. It forces AI agents and developers to satisfy semantic HTML rules and contrast ratios before the code even leaves their machine, saving weeks of rework on every sprint.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

Start a Compliance Task in GitScrum Get Accessibility Prover MCP on Vinkius →

Connected via Vinkius catalog · No credit card

PRO Annual

$106.80/year · 50 users · no per-seat

Get PRO Annual

workflow

task.delegate()

Create a task. Delegate to Claude. Get the result on your board.

Create a task in GitScrum

You draft a ticket, detailing the UI component (e.g., 'User Profile Card') and asking Claude to check its full accessibility compliance against WCAG 2.2 AA.

Claude runs the Accessibility Prover MCP

Claude autonomously invokes the MCP, forcing a structured validation of semantic HTML, keyboard navigation paths, and contrast ratios on the component's design specification.

Outcome lands in your GitScrum board

The result is an auditable compliance report attached to the ticket. It flags any violations—like 'Div Soup' or failing contrast ratios—allowing you to address them immediately.

templates

task.create()

Accessibility Prover MCP + Claude: 3 Templates for Your Project Backlog

Copy. Paste into a Claude-aware GitScrum task. Done.

Sprint boardtemplate1

Review Component for Keyboard Traps using Accessibility Prover

A developer completes a complex modal dialog and hands it over for peer review.

Claude prompt

I need you to validate this new modal component design. Use the accessibility checking tools to ensure that focus is correctly trapped inside, the tab order is logical, and every element is reachable via keyboard navigation. Check for any potential traps before I write the final code in Cursor.

Backlogtemplate2

Validate Semantic Structure of New Landing Page with Claude

A marketing team provides a new landing page wireframe and needs it to pass WCAG compliance immediately.

Claude prompt

Review this entire landing page specification. Please use the Accessibility Prover MCP to verify that all sections correctly utilize semantic HTML5 elements (like <header> and <main>) instead of generic divs, and confirm alt text is present for every image.

Client portaltemplate3

Check Form Input Accessibility Before QA Handoff

A developer finishes a multi-step form (e.g., checkout) and it's ready to be tested by QA.

Claude prompt

I need an audit of this entire checkout flow. Claude, please use the MCP to confirm that every input field has explicit labels associated with it, that error messages are live announced for screen readers, and that color contrast ratios meet the 4.5:1 minimum across all states.

01 · workflow

Accessibility Prover MCP + Claude: Preventing Design Flaws in Your Project Backlog

Think about the typical process. A designer hands over a mockup, and you spend hours manually checking if the color contrast is compliant or if the structure relies on non-semantic divs. This manual back-and-forth wastes sprint time and introduces human error right at the start of the development cycle.

Now, Claude reads that initial design specification through the Accessibility Prover MCP. It doesn't just check; it forces compliance validation against WCAG 2.2 AA standards immediately within GitScrum. You stop chasing bugs in QA and start building compliant features on day one.

Open this workflow in GitScrum →

02 · outcome

Accessibility Prover MCP + Claude: Auditing Complex UI Components During Code Review

Code reviews used to be a mess of pointing out missing alt texts or improperly nested divs. You'd wait until the end, find 30 tickets needing rework, and then re-prioritize your whole backlog just for accessibility fixes.

With this MCP, Claude takes over that review. It analyzes the component specification against its full set of standards—semantic HTML, focus traps, ARIA attributes—and generates a fixable report right in GitScrum. This makes sure your AI agents and developers can move faster while staying compliant.

prompts

claude.ask()

Claude prompts that fire once Accessibility Prover MCP is live

I'm building a new feature with custom components; Claude, can you use the Accessibility Prover MCP to audit this specification and give me a compliance score? I want to ensure we don't hit any WCAG roadblocks later.

Before I commit this UI component to GitScrum, please run it through the Accessibility Prover MCP. Focus specifically on motion safety and contrast ratios because those are usually overlooked in quick sprints.

Can Claude help me map out a user flow for an administrative dashboard? Use the MCP to guide me on semantic structuring so that my AI agents can build compliant code easily.

Run this entire sprint's requirements document through the Accessibility Prover MCP. I want to know which tickets are at risk of failing WCAG compliance based purely on their description.

specs

tools.list()

What Claude can call on Accessibility Prover MCP: 1 tool for sprint automation

Each tool is one operation Claude runs on your behalf.

tool_name	operation
validate_accessibility	Claude uses this tool to conduct a structured reflection, validating whether the UI design meets WCAG 2.2 AA standards. It checks for correct semantic landmarks, logical keyboard tab orders, color contrast ratios (4.5:1 minimum), proper ARIA annotations, and motion safety settings.

grade

A+

tools

auth

Required

catalog

Vinkius

faq

faq.read()

Accessibility Prover MCP + Claude, answered for GitScrum users

How does the Accessibility Prover MCP work with Claude Desktop versus Claude Pro?

It works through your AI client, whether that's Claude Desktop or Claude Pro. The key is the MCP connection; it provides Claude access to structured validation tools. This means you get the same powerful compliance checks directly within GitScrum tasks.

Is Accessibility Prover reliable when working with AI agents like Cursor?

Yes, absolutely. The MCP is designed to act as a guardrail for AI agents. When Claude runs the validation, it forces semantic checks that most generative models might skip, ensuring your resulting code meets WCAG standards.

Will using this MCP require extensive setup in GitScrum?

No. Once connected via Vinkius and integrated into Claude, you simply add the task to your sprint board. The system handles calling the complex validation logic; all you do is provide the component specification.

Can I use Accessibility Prover MCP across multiple projects in GitScrum?

Yes, because it's integrated into GitScrum tasks, you can apply this compliance check to any project or client board. Claude handles the context switching for you, making governance consistent.