What problem does it solve? Manually checking whether a web page meets accessibility standards is slow and error-prone, and generic audit reports often fail to tell you exactly where each violation lives in your source code. This Skill runs an automated WCAG audit against a live page and grounds every violation to a precise DOM selector and source file:line so fixes can start immediately. ## Core Features & Use Cases - Live-page WCAG auditing: Runs the @accesslint/core engine through a debuggable Chrome instance over CDP, returning violations with impact counts, evidence (contrast ratios, missing attributes), and fix guidance. - Flexible targeting: Accepts a URL, a named target from accesslint.config.json (e.g. dev, storybook), or nothing to use the configured default target. - Source-grounded reporting: Maps each violation to its DOM selector and, when available, the originating file:line and symbol, producing a worklist that drives fixes without editing code itself. - Use Case: After shipping a UI change, run the scan against your dev server to verify the page is accessible, then hand mechanical fixes off and re-run to verify. ## Quick Start Ask the assistant to scan your local dev page for accessibility issues, for example by saying "run an accessibility scan on http://localhost:3000 and list the violations".
