Compare accessibility violations across branches
accesslint-diffskillsetup L2★0
Sheshiyer/skill-clusters ↗What it does
Compare accessibility violations across versions
Best for
Proving a UI change introduces no new accessibility regressions before merging to main.
Inputs
- · file|module|project scope
- · live page URL
- · git branch name (optional)
- · DOM selector or file selector
Outputs
- · prioritized violation report
- · code fixes or worklist
- · JSON results
- · accessibility audit findings
- · UI snapshot or visual comparison
Requires
- · GitHub API
- · @accesslint/cli
- · @accesslint/chrome
- · AST-Grep
- · Chrome DevTools
- · Git
Preconditions
Live development server running; Chrome available for live-DOM audit
Failure modes
- · Tool invocation error or resource unavailable
Trust signals
- · Cites WCAG 2.2 standards and Level AA conformance
- · Includes regression test safety gates
- · Leverages LSP and AST-based code analysis
- · Includes post-execution verification step
- · Provides precise file:line source mapping