What problem does it solve? When you change code, you need to know whether your changes introduced new accessibility violations or fixed old ones, without wading through a full audit report. This Skill compares a live page's accessibility violations against a baseline (uncommitted changes via git stash, or another branch) and reports only what changed. ## Core Features & Use Cases - Stash-based diffing: Stashes uncommitted changes to capture a baseline scan, restores your working tree, then reports new, fixed, and pre-existing violations. - Branch diffing: Checks out a target branch (defaulting to the repo's default branch) to capture the baseline, with --wait-for support to gate audits on rebuilds. - Actionable reporting: Each new violation includes the selector, source location when available, evidence, and a mechanical fix or a NEEDS HUMAN flag. - Use Case: Before committing a UI change, run the diff to confirm your new component did not introduce color-contrast or missing-alt violations compared to main. ## Quick Start Ask the AI to diff the accessibility violations of your local page against the main branch, for example: "Run an accessibility diff of http://localhost:3000 against main and show only new violations."