accesslint-scan
Installation
SKILL.md
Audit a live page and report what's broken and where. Locate; don't fix. If no URL in $ARGUMENTS, ask for one.
When to Use
- A supplied page needs an automated contrast, accessible-name, or semantic-markup audit.
- You need selector-grounded findings after a UI change, without modifying the application.
- Manual assistive-technology checks or site-wide conformance assessment are separate work.
1. Audit
Use an already reviewed, project-pinned installation of @accesslint/chrome and
@accesslint/cli; confirm their local binaries and CLI help before execution.
Do not silently download and execute @latest. Confirm the URL and whether
browser access could expose authenticated or sensitive content.
For a project whose locked installation exposes these binary names: