|
1 | 1 | --- |
2 | 2 | id: accessibility-mcp-server |
3 | 3 | title: Accessibility MCP Tool |
4 | | -sidebar_label: Accessibility MCP Tool |
5 | | -description: Use the Accessibility MCP Tool for supported AI-assisted accessibility analysis workflows. |
| 4 | +sidebar_label: Accessibility |
| 5 | +description: Run accessibility checks on hosted URLs or local React apps and get detailed remediation guidance using the Accessibility MCP Tool. |
6 | 6 | slug: accessibility-mcp-server/ |
7 | 7 | url: https://www.testmuai.com/support/docs/accessibility-mcp-server/ |
8 | 8 | site_name: TestMu AI |
9 | 9 | canonical: https://www.testmuai.com/support/docs/accessibility-mcp-server/ |
| 10 | +keywords: |
| 11 | + - accessibility testing |
| 12 | + - accessibility mcp |
| 13 | + - a11y |
| 14 | + - testmu ai |
| 15 | + - MCP |
| 16 | + - MCP server |
10 | 17 | --- |
11 | 18 |
|
12 | | -# Accessibility MCP Tool |
| 19 | +import CodeBlock from '@theme/CodeBlock'; |
| 20 | +import BrandName, { BRAND_URL } from '@site/src/component/BrandName'; |
| 21 | + |
| 22 | +<script type="application/ld+json" |
| 23 | + dangerouslySetInnerHTML={{ __html: JSON.stringify({ |
| 24 | + "@context": "https://schema.org", |
| 25 | + "@type": "BreadcrumbList", |
| 26 | + "itemListElement": [{ |
| 27 | + "@type": "ListItem", |
| 28 | + "position": 1, |
| 29 | + "name": "Home", |
| 30 | + "item": BRAND_URL |
| 31 | + },{ |
| 32 | + "@type": "ListItem", |
| 33 | + "position": 2, |
| 34 | + "name": "Support", |
| 35 | + "item": `${BRAND_URL}/support/docs/` |
| 36 | + },{ |
| 37 | + "@type": "ListItem", |
| 38 | + "position": 3, |
| 39 | + "name": "Accessibility MCP Tool", |
| 40 | + "item": `${BRAND_URL}/support/docs/accessibility-mcp-server/` |
| 41 | + }] |
| 42 | + }) |
| 43 | + }} |
| 44 | +></script> |
| 45 | + |
| 46 | +# Getting Started with Accessibility MCP Tool |
| 47 | + |
| 48 | +Accessibility MCP Tool is part of the [TestMu AI MCP Server](/support/docs/testmu-mcp-server/). It runs accessibility checks on publicly hosted URLs and local React applications, and returns a detailed report with remediation guidance. |
| 49 | + |
| 50 | + |
| 51 | +## Key Features |
13 | 52 |
|
14 | | -Accessibility MCP Tool enables supported AI-assisted Accessibility workflows for public URLs and selected local app analysis flows. It is a tool within the [TestMu AI MCP Server](/support/docs/testmu-mcp-server/). |
15 | | - |
16 | | -This page describes what the Accessibility MCP Tool is, when an MCP-connected, AI-assisted analysis flow makes sense, and how that surface differs from DevTools, Automation, and Web Scanner. Use it to orient prerequisites and boundaries before connecting a client or routing work into an MCP-based accessibility review. |
17 | | - |
18 | | -## When to use this |
19 | | - |
20 | | -Use the Accessibility MCP Tool when you want an AI-assisted workflow that can request Accessibility analysis through supported MCP-compatible clients and tools. |
21 | | - |
22 | | -## What it is good for |
23 | | - |
24 | | -- analyzing supported public URLs through an MCP-based workflow |
25 | | -- supporting selected local-app analysis flows where MCP support is available |
26 | | -- routing users into an AI-assisted accessibility review flow instead of a browser-extension or framework-execution flow |
27 | | - |
28 | | -## Prerequisites |
29 | | - |
30 | | -- access to the Accessibility MCP Tool feature |
31 | | -- an MCP-compatible client or workflow that can connect to the server |
32 | | -- a public URL or supported local application flow you are authorized to test |
| 53 | +--- |
33 | 54 |
|
34 | | -## Onboarding checklist (first connection) |
| 55 | +- Identifies accessibility issues in your application. |
| 56 | +- Generates an accessibility report you can share with your team. |
| 57 | +- Provides remediation guidance for a11y issues in locally hosted applications. |
35 | 58 |
|
36 | | -1. Install and verify the **platform** MCP prerequisites from [Introducing TestMu AI MCP Server](/support/docs/testmu-mcp-server/) if your client expects the shared endpoint model. |
37 | | -2. Confirm with your admin that **Accessibility MCP** is enabled for the workspace (feature flag or contract). |
38 | | -3. In your MCP client (for example Cursor, VS Code extension, or internal agent), add the **Accessibility MCP server definition** supplied in your account documentation—endpoint, auth mode, and scopes differ by release; copy from the in-product help or support article your CS team provides. |
39 | | -4. Start with a **single public URL** smoke test authorized for scanning; avoid sensitive or authenticated pages until tunnel or auth patterns are validated. |
40 | | -5. Compare MCP output with a **DevTools or automation report** for the same URL so you trust the interpretation before relying on it in compliance conversations. |
41 | | -6. Escalate gaps to support with **client name**, **server version**, and **timestamp** if tool calls fail. |
| 59 | +## Capabilities |
42 | 60 |
|
43 | | -## Product boundary |
| 61 | +--- |
44 | 62 |
|
45 | | -Accessibility MCP Tool is a dedicated product surface. It is not the same as: |
| 63 | +1. **getAccessibilityReport** - Fetches a detailed accessibility report for a public URL. You can view the report in your browser to analyze the issues. |
| 64 | +2. **buildLocalAppForAnalysis** - Builds and serves your local React application via TestMu AI and identifies accessibility issues. |
| 65 | +3. **analyseAppViaTunnel** - Tests a local app already running via TestMu AI tunnel for accessibility failures. |
46 | 66 |
|
47 | | -- **Accessibility DevTools**, which is for browser-based manual and assisted testing |
48 | | -- **Accessibility Automation**, which is for framework-driven automated execution |
49 | | -- **Web Scanner**, which is an integrated URL-scanning surface |
| 67 | +## How to Invoke |
50 | 68 |
|
51 | | -## Related docs |
| 69 | +--- |
52 | 70 |
|
53 | | -- [Introducing TestMu AI MCP Server](/support/docs/testmu-mcp-server/) (platform-wide MCP setup) |
54 | | -- [Choosing the Right Accessibility Tool](/support/docs/accessibility-choosing-the-right-tool/) |
55 | | -- [Accessibility DevTools (Overview)](/support/docs/accessibility-devtools/) |
56 | | -- [Accessibility Automation (Overview)](/support/docs/accessibility-automation/) |
57 | | -- [Starting an Accessibility Scan with Web Scanner](/support/docs/web-scanner-accessibility-scan/) |
| 71 | +Once your MCP client is connected, use natural language to interact with the Accessibility tool. Example prompts: |
| 72 | + |
| 73 | +- "Run an accessibility report on `https://example.com`." |
| 74 | +- "Build my local React app and check it for accessibility issues." |
| 75 | +- "I have a local app running on port 3000 via TestMu AI tunnel, check it for a11y failures." |
| 76 | +- "Show me the accessibility violations on the homepage and how to fix them." |
| 77 | + |
| 78 | +Your AI client will route the request to the appropriate capability and return the report or remediation guidance inline. |
| 79 | + |
| 80 | +<nav aria-label="breadcrumbs"> |
| 81 | + <ul className="breadcrumbs"> |
| 82 | + <li className="breadcrumbs__item"> |
| 83 | + <a className="breadcrumbs__link" href={BRAND_URL}> |
| 84 | + Home |
| 85 | + </a> |
| 86 | + </li> |
| 87 | + <li className="breadcrumbs__item"> |
| 88 | + <a className="breadcrumbs__link" target="_self" href={`${BRAND_URL}/support/docs/`}> |
| 89 | + Support |
| 90 | + </a> |
| 91 | + </li> |
| 92 | + <li className="breadcrumbs__item breadcrumbs__item--active"> |
| 93 | + <span className="breadcrumbs__link"> |
| 94 | + Accessibility MCP Tool |
| 95 | + </span> |
| 96 | + </li> |
| 97 | + </ul> |
| 98 | +</nav> |
0 commit comments