.agents/skills/accessibility-audit/SKILL.md
Audit UI code for WCAG compliance
npx skillsauth add itsimonfredlingjack/codex-dev-plugin accessibility-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
These issues create significant barriers for some users.
These issues may cause difficulty for some users.
These are best practice improvements.
The following WCAG criteria passed:
| Criterion | Name | Level | | --------- | ---------------------- | ----- | | 1.1.1 | Non-text Content | A | | 1.3.1 | Info and Relationships | A | | ... | ... | ... |
Add these tests to catch regressions:
// Example jest-axe test
import { axe, toHaveNoViolations } from "jest-axe";
expect.extend(toHaveNoViolations);
test("component has no accessibility violations", async () => {
const { container } = render(<Component />);
const results = await axe(container);
expect(results).toHaveNoViolations();
});
Generated by UI Design Accessibility Audit WCAG Reference: https://www.w3.org/WAI/WCAG21/quickref/
## Completion
Update `audit_state.json`:
```json
{
"status": "complete",
"completed_at": "ISO_TIMESTAMP",
"compliance_status": "needs_improvement",
"issues_found": {
"critical": 2,
"serious": 5,
"moderate": 8,
"minor": 3
}
}
Display summary:
Accessibility Audit Complete!
Target: {target}
WCAG Level: {level}
Compliance Status: {status}
Issues Found:
- {n} Critical (must fix)
- {n} Serious
- {n} Moderate
- {n} Minor
Full report: .ui-design/audits/{audit_id}.md
What would you like to do next?
1. View details for critical issues
2. Start fixing issues (guided)
3. Generate automated tests
4. Export report for stakeholders
5. Audit another component
Enter number:
If user selects "Start fixing issues":
Let's fix accessibility issues starting with critical ones.
Issue 1 of {n}: {Issue Title}
WCAG {criterion}: {criterion_name}
Location: {file}:{line}
{Show current code}
The fix is:
{Explain the fix}
Should I:
1. Apply this fix automatically
2. Show me the fixed code first
3. Skip this issue
4. Stop fixing
Enter number:
Apply fixes one at a time, re-validating after each fix.
<result>
<analysis>Brief analysis</analysis>
<solution>Implementation</solution>
<considerations>Trade-offs and notes</considerations>
</result>
development
--- name: full-stack-feature description: Orchestrate full-stack feature development across backend, frontend, and infrastructure layers with modern API-first approach: --- Orchestrate full-stack feature development across backend, frontend, and infrastructure layers with modern API-first approach: [Extended thinking: This workflow coordinates multiple specialized agents to deliver a complete full-stack feature from architecture through deployment. It follows API-first development principles,
development
Orchestrate comprehensive multi-dimensional code review using specialized review agents
tools
Expert in secure frontend coding practices specializing in XSS prevention, output sanitization, and client-side security patterns. Use PROACTIVELY for frontend security implementations or client-side security code reviews.
tools
Build React components, implement responsive layouts, and handle client-side state management. Masters React 19, Next.js 15, and modern frontend architecture. Optimizes performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.