audit-and-fix

Audits accessibility violations, applies source code fixes, and re-audits to verify.

3|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/langgenius/due-date-hq-jwl --skill audit-and-fix-langgenius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-and-fix
Source: https://github.com/langgenius/due-date-hq-jwl/tree/main/.claude/skills/audit-and-fix
Command: npx skills add https://github.com/langgenius/due-date-hq-jwl --skill audit-and-fix-langgenius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessibility issues are often reported but never fixed, or fixed without verification that the fix worked and introduced no regressions. This Skill closes the audit-edit-verify loop by finding WCAG violations, editing the source code, and re-auditing to confirm the fixes landed. ## Core Features & Use Cases - Dual audit flows: Runs live-DOM audits against rendered pages when a browser MCP (chrome-devtools, playwright, puppeteer) is connected, catching SPA content, web-font contrast, and post-mount ARIA state; falls back to static HTML audits otherwise. - Source-mapped fixes: Maps violations to exact JSX file and line locations via React DevTools fiber data, or locates source files by grepping for stable hooks like data-testid, id, and aria-label. - Fixability-aware editing: Applies mechanical fixes verbatim from authoritative Fix directives, leaves TODO comments for contextual or visual issues that need human judgment, and verifies results with audit_diff. - Use Case: A developer receives a report of contrast and missing-alt violations on a React page. The Skill audits the live page, edits the offending components, and re-runs the diff to confirm all targeted violations are fixed with zero new ones. ## Quick Start Ask the assistant to audit and fix the accessibility issues in your page or component, then confirm the scope of files it may edit.

Frequently Asked Questions about audit-and-fix

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

FAQPage Schema
How do I fix accessibility violations in my code automatically?

Run an accessibility audit to get violations tagged with fixability levels, then apply the authoritative Fix directives for mechanical issues directly to source files. Re-run the audit diff afterward to confirm each violation moved to the fixed bucket with no new issues introduced.

How do I audit accessibility of a React single-page application?

Use a live-DOM audit through a browser MCP such as chrome-devtools, playwright, or puppeteer, which evaluates the rendered page after mount. This catches SPA content, web-font contrast, and post-mount ARIA state that static HTML audits miss.

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

Live-DOM audits run against the rendered page in a browser and include Source file and line mappings from React DevTools fibers. Static audits analyze HTML files or strings only, cannot see rendered-only issues, and lack Source line mappings.

Can accessibility fixes be applied without a browser MCP connected?

Yes, the static fallback flow audits HTML files or strings directly and maps violations to source by grepping for stable hooks like data-testid, id, and aria-label. Rendered-only issue categories will not be caught in this mode.

When should accessibility fixes not be applied automatically?

Skip automatic fixes when the user has not confirmed scope, when more than about ten mechanical fixes are pending, or when a violation lacks a Fix directive. Contextual and visual issues need human judgment, so leave a TODO comment with the rule ID instead.