Catch accessibility regressions in your changes.
Compares a live page before and after code changes to report accessibility regressions, fixes, and pre-existing violations.
When to use it
Use to check whether uncommitted changes or a pull request introduced accessibility issues, or as a CI gate.
Give it a project and optionally a target or comparison branch; it returns an accessibility change report without editing the code.
What you provide
Requires the Node.js runtime to extract the browser port from the ensure command's JSON output.
This skill
the target web page
Reads the live target page
npx -y @accesslint/chrome@latest
Starts and stops managed Chrome
npx -y @accesslint/cli@latest
The latest accessibility scanner