skills.rest
udsy19
udsy19COMMUNITY
Explore all skills by this author →
GitHub

accesslint-diff

Compare live web page accessibility violations against a Git baseline.

Updated Jun 24, 2026
Search Tags:#code review#accessibility#a11y#web development#git integration
One-click install
npx skills add https://github.com/udsy19/.claude --skill accesslint-diff-udsy19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accesslint-diff
Source: https://github.com/udsy19/.claude/tree/main/skills/accesslint-diff
Command: npx skills add https://github.com/udsy19/.claude --skill accesslint-diff-udsy19

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @accesslint/cli, @accesslint/chrome, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of checking a live page's accessibility violations against a baseline, ensuring compliance and identifying new issues.

Core Features & Use Cases

  • Baseline Comparison: Compares a live page's accessibility violations against a baseline, either uncommitted changes or a specified branch.
  • Diffing: Reports only new violations introduced, violations fixed, and pre-existing count.
  • Audit: Provides a full audit with no diffing for comprehensive analysis.
  • Target Flexibility: Can target a URL, a config target name, or use the default target from accesslint.config.json.

Quick Start

Run the accesslint-diff skill to scan the current page for accessibility issues against the default branch.

Frequently Asked Questions about accesslint-diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check web page accessibility violations against a git branch baseline?▼

To check web page accessibility violations against a baseline, this Skill compares a live page's audit results against a specified Git branch or uncommitted changes, reporting newly introduced and fixed issues.

How do I diff accessibility issues introduced by uncommitted changes?▼

To diff accessibility issues from uncommitted changes, the Skill scans the live page and compares violations against the baseline, isolating only new issues and resolved violations while tracking pre-existing counts.

Do I need @accesslint/cli to scan live pages for accessibility compliance?▼

Yes, you need both @accesslint/cli and @accesslint/chrome installed, as the Skill relies on these dependencies to scan live web pages and ensure compliance with accessibility standards.

Can I generate a full accessibility audit without comparing it to a baseline?▼

Yes, you can generate a full accessibility audit without baseline comparison, which provides a comprehensive analysis of all current violations on the target web page without diffing.

What is the best way to automate accessibility checks for a specific URL?▼

To automate accessibility checks for a specific URL, the Skill uses a configurable target approach, allowing you to pass a URL directly, use a config target name, or default to accesslint.config.json.

Why should I use an accessibility diff instead of a full audit during code review?▼

An accessibility diff is ideal for code review because it filters out pre-existing violations and reports only new issues introduced or fixed, reducing noise and focusing on branch-specific changes.

Related Skills

Explore More Software Engineering Skills→
chaimtchaimt

speckit-git-initialize

Initialize a Git repository with an initial commit in the current directory.

Community
Intermediate
pacphipacphi
6

accessibility-testing

Perform WCAG 2.2 accessibility testing on web applications with axe-core.

Community
Advanced
jpaddison3jpaddison3

ci

Stage git changes and commit with automatic branch creation from CLAUDE.md policies.

Community
Intermediate
yonetim258852yonetim258852

accesslint-diff

Diff live accessibility violations against a stored baseline to identify new issues.

Community
Advanced