wcagcMCPExplore WCAGC
MCP server for accessibility testing

Accessibility checks,
inside your AI workflow.

Give your assistant real WCAG test results—not guesses. Scan pages, crawl sites, inspect PDFs, follow trends, and verify fixes through WCAGC.

See example prompts ↓Visit wcagc.com
Deterministic checks No compliance score Evidence you can inspect
● WCAG Compliance Connected
Scan https://example.com for accessibility issues.
w
WCAGC

Running deterministic axe-core checks…

Done
Machine-detected findingsWCAG 2.1 AA
2 Critical
5 Serious
8 Moderate
01
Elements must meet minimum color contrast

color-contrast · 6 affected nodes

02
Images must have alternative text

image-alt · 3 affected nodes

Single URL scans✦Full-site crawls✦PDF/UA checks✦Saved journeys✦Fix verification

One connection. Real evidence.

Ask in plain language.
Get structured accessibility data.

The Model Context Protocol (MCP) gives your assistant a direct, permissioned path to WCAGC. The checks run in WCAGC; your assistant turns the results into a clear next step.

01

Scan any public page

Run deterministic axe-core checks against a URL and return rule IDs, severity, selectors, and affected elements.

scan_url · get_scan · get_findings
02

Crawl registered sites

Scan reachable pages across a site, follow progress, and review deduplicated findings mapped to WCAG criteria.

scan_site · get_run · get_run_findings
03

Inspect accessible PDFs

Run machine-verifiable PDF/UA-1 checks for document structure, tags, and other testable requirements.

check_pdf · get_pdf_check
04

Test real user journeys

Replay reviewed, saved flows—such as sign-in or checkout—and checkpoint accessibility at every step.

run_journey · get_journey_run
05

Track change over time

Read completed scan history, severity counts, and added or resolved markers without inventing a score.

get_trends
06

Move from finding to fix

Group repeated patterns, inspect their blast radius, track remediation, and re-check representative pages.

get_root_causes · get_fixes · verify_fix

From question to evidence

Not another dashboard
you have to babysit.

Stay in the conversation where the work already happens. WCAGC handles the scan; your assistant handles the orchestration and explanation.

  1. 1
    Ask naturally

    Describe the page, site, PDF, journey, or history you need.

  2. 2
    WCAGC runs the checks

    Tools return structured results from axe-core and veraPDF—not an AI opinion.

  3. 3
    Act on clear evidence

    Review rules, impact, affected elements, trends, and verification scope.

Try saying this

Prompts that turn into real tests.

Be precise about whether you want to start a scan or only read saved data. The assistant calls the right WCAGC tools for the job.

QUICK PAGE CHECK01
“Scan https://example.com now. Poll until the scan is complete and summarize the machine-detected findings.”
w WCAG Compliance
NO-CHANGES LOOKUP02
“List my registered sites. Do not start a new scan.”
w WCAG Compliance
ACCESSIBILITY TREND03
“Show the recent accessibility trend for example.com. Do not calculate or report a compliance score.”
w WCAG Compliance

A meaningful distinction

A scan is evidence.
It is not a compliance verdict.

Automated testing detects only a portion of accessibility barriers. WCAGC reports what its checks can verify and keeps the scope visible.

Results are not certification, a guarantee, or proof of conformance. Manual evaluation—including keyboard, screen reader, cognitive, and usability testing—is still required.

w

Accessibility work, connected

Bring real accessibility
testing into the conversation.

Connect WCAG Compliance, sign in to your WCAGC account, and start with a single URL.

Get started with WCAGC