Accessibility Audit Helper

You can audit React components for WCAG 2.1 accessibility violations by providing the JSX code to the agent, which then reviews it for issues like ARIA usage, heading hierarchy, and focus management. It returns categorized findings with severity labels and before/after code fixes.

The best way to find and fix HTML color contrast and keyboard accessibility issues is to run a UI audit on the code. The agent systematically reviews the markup to identify violations and generates actionable before/after code examples to resolve them.

Yes, you can use this during code reviews to check alt text and ARIA usage. The audit is designed for feature audits and accessibility sweeps, systematically identifying issues in HTML and JSX components and providing concrete fixes.

To fix heading hierarchy and focus management issues in JSX, run an accessibility audit on the component. The agent identifies the specific WCAG 2.1 violations and outputs before/after code examples showing the corrected implementation.

This accessibility audit works with both plain HTML and React. It is designed to apply to HTML, JSX, and React components to identify WCAG 2.1 violations like missing alt text, ARIA misuse, and color contrast problems.

To start an accessibility sweep of your UI code, you need to copy the skill file to the .agents/skills/accessibility-audit-helper/SKILL.md path in your project root, then ask the agent to audit a specific component to receive categorized findings and fixes.