audit

Audit and fix WCAG 2.2 accessibility issues in codebases and live web pages.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Debindenny/travelplanner-community- --skill audit-debindenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Debindenny/travelplanner-community-/tree/main/travel-planner/claude-marketplace/plugins/accesslint/skills/audit
Command: npx skills add https://github.com/Debindenny/travelplanner-community- --skill audit-debindenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web accessibility violations are hard to find and tedious to fix manually. This Skill automates WCAG 2.2 auditing across codebases, HTML files, and live web pages, then either produces a prioritized report or applies and verifies fixes directly. ## Core Features & Use Cases - Report mode: Sweep a codebase, directory, or URL and produce a prioritized accessibility report grouped by rule and severity, without editing any files. - Fix mode: Run an audit → edit → verify loop that applies mechanical fixes verbatim, leaves TODOs for contextual issues, and confirms violations are resolved. - Live-DOM auditing: Audits the rendered DOM via a debuggable Chrome instance (auto-launched headless if needed), catching issues static source analysis misses, with React source file/line attribution. - Use Case: Point it at your React app's dev-server URL to get a deduplicated list of critical contrast and ARIA violations with exact file:line pointers, then ask it to fix and verify them. ## Quick Start Ask the assistant to audit the accessibility of your components directory or a URL and produce a prioritized WCAG report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit my website for WCAG accessibility issues?▼

Provide a URL, directory, or set of files and request an audit. The skill audits the live DOM through a debuggable Chrome instance for URLs, or audits raw HTML strings for files, then produces a prioritized report grouped by rule and severity.

How do I automatically fix accessibility violations in my code?▼

Use fix mode by asking to audit and fix a target. The skill records a baseline violation set, applies mechanical fixes verbatim from the engine's Fix directives, leaves TODOs for contextual issues, then re-audits to verify every targeted violation is resolved.

Can accessibility auditing work on pages behind a login?▼

Yes. Start a headed debuggable Chrome with npx @accesslint/chrome ensure --headed, sign in manually, then run the live audit against that URL and port. The audit attaches to your authenticated session instead of launching a new browser.

What is the difference between live-DOM and static HTML accessibility audits?▼

Live-DOM audits render the page in Chrome and catch issues static source cannot show, including React source file and line attribution via DevTools fibers. Static HTML-string audits are the fallback for raw files or when Chrome cannot be launched.

What are the limitations of automated WCAG accessibility testing?▼

Automated engines only catch mechanically detectable violations. Content clarity, screen-reader announcement quality, keyboard flow coherence, and complex visual contrast require manual human review, which the report flags rather than guesses at.