Loading...
Loading...
One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.
npx skill4agent add accesslint/skills accessibility-scan../shared/methodology.md$ARGUMENTSdevstorybookaccesslint.config.jsonnpx @accesslint/cli initPORT=$(npx -y @accesslint/chrome@latest ensure | node -e 'process.stdin.on("data",d=>process.stdout.write(""+JSON.parse(d).port))')
npx -y @accesslint/cli@latest scan <target> --port "$PORT" --format json<target>$ARGUMENTS""--selector--wait-for "<selector>"--include-aaa--disable <rules>accesslint.config.jsonfile:line (symbol)sourcesourceNEEDS HUMANaccesslint:accessibility-fixnpx -y @accesslint/chrome@latest stop --all # skip if ensure reported "managed":falseensureaccesslint.config.json