Summary
An accessibility check runs in the same loop that is writing the markup.
Two tools, one argument each: a URL goes in and findings come back, with rule tags to narrow which families run and includeHtml when a selector alone is not enough to act on. Auditing is the whole scope — nothing here rewrites markup, and confirming a fix means auditing the changed page again, which is cheap enough that it fits inside an edit loop.
What it is
An accessibility auditing server for a URL: a full audit and a summary of the issues on a page.
What you get
- An accessibility audit of a URL, scoped by rule tags when only part of the ruleset applies
- The offending HTML alongside each finding when includeHtml is set, so a fix does not start with hunting for the element
- A summary of a page's issues, short enough to compare before and after a change
Requirements
A URL the server can reach. No account and no key. MPL-2.0.
Setup effort
One command — npx a11y-mcp