wcag-compliance-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_html_snippetA | Run 18 static WCAG 2.2 checks against an HTML snippet or full page and return findings with the failing success criterion, the offending markup, and a corrected example. Covers alt text, accessible names for links and buttons, form labels, language, title, heading order, duplicate ids, tabindex, aria-hidden, list structure, iframe titles, table headers, video captions, viewport zoom, and autocomplete purpose. Static analysis only: it cannot judge contrast, keyboard traps, focus visibility, or reading order in a rendered page. |
| lookup_wcag_criterionA | Search the 87 WCAG 2.2 success criteria by number (1.4.3), name (Contrast), keyword, or axe-core rule name. Returns level, principle, guideline, whether it applies to U.S. ADA Title II entities, the practical test, the axe-core rules that target it, and links to the W3C specification and Understanding document. |
| get_verified_fix_exampleA | Return a failing HTML snippet and its corrected version for a WCAG 2.2 defect, with an explanation of the impact on assistive technology and a manual test step. Every pair was executed in headless Chromium against axe-core 4.14.0, and the detection method is reported so you know whether automation catches this defect or a human must. Look up by criterion number (2.4.7), pair id (wcag-1-4-3-01), or keyword (focus indicator). |
| check_ada_compliance_deadlinesA | Return the dated web accessibility obligations that apply to an entity type, from the 1990 ADA statute through the 2027 and 2028 deadlines in the DOJ Title II final rule and the HHS Section 504 rule. Reports what is binding now, what is upcoming within the horizon with days remaining, and the primary source URL for every date. Entity types: title_ii_large, title_ii_small, title_iii_business, federal_contractor, hhs_recipient, eu_business, ontario. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| wcag-automation-coverage | How much of WCAG 2.2 a scanner can actually test, measured against 64 browser-verified cases. |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct operation: static auditing, criterion lookup, verified fix examples, and ADA deadline checking. Although audit_html_snippet and get_verified_fix_example both involve defects and corrections, their descriptions distinguish audit results from a curated remediation library.
All four tools use a consistent snake_case verb_noun pattern: audit_html_snippet, lookup_wcag_criterion, get_verified_fix_example, and check_ada_compliance_deadlines. The naming is predictable and readable.
Four tools is a well-scoped set for this domain, with each tool covering a substantial but distinct compliance function. There is no filler or redundant tool.
The surface covers static auditing, WCAG reference lookup, remediation examples, and legal deadlines, which are the core needs for WCAG/ADA compliance support. The main gap is the acknowledged lack of rendered-page checks such as contrast, keyboard traps, and focus visibility, but that limitation is explicit rather than hidden.