TastefulKit 2 views · 24h
← AI skills

Accessibility Regression Diff — AccessLint

Compares live-DOM accessibility findings before and after a code change, separating newly introduced violations, fixes and pre-existing issues instead of reporting a full audit again.

accessibilityregression-reviewlive-domui-review
View skill source ↗ Repository ↗

114 GitHub stars (repository-wide; checked Oct 29, 2026)

skills.sh installs: not checked

When to use it

Use when reviewing a UI change or guarding a component against accessibility regressions. Uses Chrome/CDP and the AccessLint CLI against a rendered page. The upstream procedure stashes changes or switches branches: review workspace safety and restoration, and ensure each build is ready before scanning. Selector drift, delayed rebuilds and changed target configuration can invalidate comparisons. Mechanically detectable WCAG issues only; not a conformance certificate or substitute for assistive-technology testing. MIT is declared in the upstream README; no standalone license file was present in the inspected tree. Not installed, executed or runtime-tested during discovery. GitHub stars are repository-wide, not a skill-specific rating.

Compatible agents

Claude CodeCursorCodexCopilotWindsurfGeminiClineAmp

Installation

Upstream skills-CLI installation: npx skills add AccessLint/skills; select accessibility-diff. Keep the shared methodology alongside the skill. Requires Node/npx, Git, a running target page and Chrome/CDP; it invokes @accesslint/chrome and @accesslint/cli. Configure a URL or accesslint.config.json, then ask for an accessibility diff or use /accessibility-diff --branch main. Review the stash/checkout steps before use.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 29, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.