| name | axe-a11y |
| description | Automated web accessibility scanning (axe-core) driven by patchright + real Google Chrome — audits sites behind bot walls and behind auth |
Axe Accessibility Testing Skill
Automated testing via the axe-a11y MCP server. Not a framework, not a manual-testing helper — the server executes automated scans and returns actual WCAG violation JSON.
What This Skill Runs Under the Hood
- Real Google Chrome Stable installed inside the container (not Playwright-bundled Chromium)
- Patchright — a Playwright fork that patches CDP-level detection leaks, so bot walls (Amazon, Cloudflare, DataDome, Akamai) don't fire on well-known Playwright signals
- Persistent Chrome profile bind-mounted from the host — cookies + Login Data survive container restarts, so authenticated audits work after a one-time manual sign-in
- Xvfb + VNC on :5900 — Chrome is headed (headed is required for realistic fingerprinting); operators can watch it via VNC
- axe-core WCAG 2.0/2.1 A/AA/AAA compliance checking with node-level details and remediation guidance
Tools
You have access to the following tools via the axe-a11y MCP server:
1. audit_page
Run a full accessibility audit on a given URL.
- Inputs:
url (required), tags (optional, e.g. ["wcag2aa"]), include_passes (optional boolean), ignore_https_errors (optional boolean)
- Use when: You need a comprehensive list of accessibility violations on a page.
2. check_specific_rules
Check specific axe-core rules on a page.
