Summary
The accessibility pass moves from pre-release audit to the turn the component is written.
test_html_string takes markup that has never been deployed, so a component gets checked in the same turn it is generated rather than in a sweep three weeks later. check_color_contrast answers the narrow question a palette actually raises — this pair, at this font size, bold or not — without running the full suite to get it.
What it is
An accessibility checker built on Axe-core. It tests a live URL or an HTML string at a viewport you set, plus three focused checks: colour contrast against WCAG, ARIA attribute usage, and orientation locking.
What you get
- An Axe-core pass over a URL at a width and height you specify, filtered to the rule tags you care about
- The same pass over an HTML string, for markup that is not deployed anywhere yet
- The available accessibility rules listed with tag filtering, so you can see what a run covers
- A contrast verdict on one foreground and background pair, taking font size and bold state into account, against WCAG requirements
- An ARIA attribute check over a snippet
- A check for content that forces a specific orientation
Requirements
Npx on your PATH. No account and no key.
Setup effort
One command — npx -y a11y-mcp-server