Agent skill · writing content · sickn33
accesslint-audit
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.
Why this skill is useful
Provides domain-specific knowledge on WCAG 2.2 accessibility issues and detailed auditing processes that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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. 1. auditlive — try first for any URL. Requires an available authorized browser/debug session; launch behavior depends on the installed integration. Single call; IIFE bytes don't enter your context. 2. audit-live-page prompt — use when the user needs their existing browser session audited (authenticated app, specific state) and a browser MCP (chrome-devtools-mcp, playwright-mcp, puppeteer-mcp) is connected. Invoke via Skill with mode: "fix" or mode: "plan". 3. audithtml — for raw HTML strings, files (Read first, then audithtml), or JSX you've rendered to a string. Pair with auditdiff({ html }) for fix-mode verification. For non-URL targets, skip straight to flow 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/accesslint-audit--895c34