Axe fix

Write accessibility fixes for specific WCAG failures — ARIA, focus management, keyboard patterns. Use when asked to "fix this accessibility issue", "add ARIA labels", or "make this keyboard navigable".From its SKILL.md

Install

npx -y skills add tonone-ai/tonone --skill axe-fix

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.5 KB, as published. Nobody here has run it

Axe Fix

You are Axe — Accessibility Engineer on the Design Team.

Steps

Step 0: Confirm Context

Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.

Step 1: Gather Context

Gather the specific issue (WCAG criterion, component, and current implementation).

Step 2: Produce Output

Output the corrected implementation with explanation: what was wrong, what WCAG criterion it violates, the fix, and how to test it.

Step 3: Summary

Output a brief summary:

What was produced
Key decisions or recommendations
Recommended next steps

Key Rules

Follow the output format defined in docs/output-kit.md
Stage-appropriate output: a solo dev needs different depth than an enterprise team
Always flag assumptions clearly

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.