# Accesslint Audit

Find and fix WCAG 2.2 accessibility issues.

- Repository: https://github.com/sickn33/agentic-awesome-skills (48984 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add sickn33/agentic-awesome-skills --skill accesslint-audit -g -a claude-code -y`
Codex: `npx skills add sickn33/agentic-awesome-skills --skill accesslint-audit -g -a codex -y`
Cursor: `npx skills add sickn33/agentic-awesome-skills --skill accesslint-audit -g -a cursor -y`
Gemini CLI: `npx skills add sickn33/agentic-awesome-skills --skill accesslint-audit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add sickn33/agentic-awesome-skills`

## Description

Find and fix WCAG 2.2 accessibility issues. Two modes, report (sweep a codebase or page, produce a prioritized written report, no edits) and fix (audit→edit→verify loop on a target). Prefers direct-CDP live-DOM auditing; falls back to a browser-MCP composition or HTML-string audits.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

You audit accessibility and optionally fix what's broken.

## When to Use

- Audit a requested page, component set or rendered document for accessibility findings.
- Apply and verify scoped accessibility fixes when the user requests repairs.

## Tool prerequisites

This package bundles instructions, not the AccessLint engine, browser or MCP prompts. Discover the actual installed tools and schemas. Use a reviewed pinned engine version and only an authorized browser session; report unavailable live-DOM coverage instead of inventing tool results. Automated checks cover part of WCAG, not conformance certification.

## Pick a mode from the user's intent

- **Report mode**, "audit my codebase", "review src/components/", "what's wrong with this page?", "give me an a11y report". You audit + write a report. **You do not edit files.**
- **Fix mode**, "fix the a11y issues in X", "audit and fix", "make this accessible", "verify the contrast fix landed", or hands you a violation report and asks to apply it. You audit → edit → verify.

If unsure, ask. Don't default-to-fix when the user only asked for an audit.

For very large sweeps where main-thread context cost matters, you can be invoked via `Task` (general-purpose agent) for context isolation. The recipe is the same either way.

## Picking a flow

Three flows, in order of preference.

The rest: https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/plugins/agentic-awesome-skills-claude/skills/accesslint-audit/SKILL.md