Accessibility Testing MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WCAG_LEVEL | No | WCAG version & level (e.g., 2.0_A, 2.0_AA, 2.1_A, 2.1_AA, 2.1_AAA, 2.2_A, 2.2_AA, 2.2_AAA) | 2.1_AA |
| A11Y_ENGINE | No | Testing engine (axe or ace) | axe |
| SCREEN_SIZES | No | Comma-separated viewport sizes to test (WIDTHxHEIGHT format, e.g., 1280x1024,320x640) | 1280x1024 |
| BEST_PRACTICES | No | Include best practices/recommendations | true |
| HEADLESS_BROWSER | No | Run browser in headless mode; set to false to open visible browser | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_urlB | Run accessibility tests on a URL and return detailed violation reports. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
| analyze_url_jsonA | Run accessibility tests on a URL and return violations in raw JSON format. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
| analyze_htmlB | Run accessibility tests on raw HTML content. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
| analyze_html_jsonA | Run accessibility tests on raw HTML content and return violations in raw JSON format. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
| get_rulesA | Get information about available accessibility rules for the specified engine. [Engine: axe, WCAG: 2.1_AA, Screens: 1280x1024] |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| accessibility_review | Get guidance on performing an accessibility review |
| fix_suggestion | Get suggestions for fixing a specific accessibility issue |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| WCAG Guidelines Reference | Information about WCAG accessibility guidelines and levels |
| Common Accessibility Issues | Most common accessibility issues found in web applications |
| Engine Comparison | Comparison of Axe-core and IBM Equal Access engines |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/joe-watkins/accessibility-testing-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server