- Home
- Skills
- UX & UI Design
- Fixing Accessibility: Minimal Repairs That Pass the Audit
More screenshots
Works with the AI Agents you already use
Fixing Accessibility: Minimal Repairs That Pass the Audit
Audit HTML interfaces for accessibility and fix what's broken: accessible names, keyboard access, focus and dialogs, semantics, forms, announcements, contrast, and media.
$5
Fixing Accessibility: Minimal Repairs That Pass the Audit
Example session with this skill installed
Audit our settings page for accessibility: three icon-only buttons, a save control built from a div, a modal, and an email field with an error message.
- Read your context and instructions
- Compiled the fixing accessibility
Settings page — audit produced with the skill
Seven violations found, quoted verbatim with rule, reason, and minimal fix:
- Three icon-only buttons with no names (rule 1, critical) — each gets an
aria-label; the decorative icons getaria-hidden="true". An unnamed button is a button the user cannot identify. - A
divacting as the save button (rule 2, critical) — replaced with a realbutton, not patched with keyboard handlers. The bolt-on version is a re-implementation, and re-implementations miss edge cases. - A modal that does not return focus on close (rule 3, critical) — focus return added, verified by keyboard-only testing of the full cycle: open, tab through, Escape, focus back on the trigger.
- Two skipped heading levels (rule 4, high) — corrected; the heading outline is the page's table of contents.
- An email error not linked to its field (rule 5, high) —
aria-describedbyandaria-invalid="true"added. - A toast as the only channel for the save confirmation (rule 6, medium-high) — a persistent status line added beside it. Toasts disappear; critical information needs a channel that does not.
- A disabled state shown by color alone (rule 7, medium) — paired with text.
No unrelated code touched, no redundant ARIA added, no library migration. Rubric score: 9/10 — one point held back because dark-mode contrast was not checked in this pass; it is recorded as a follow-up, not assumed.
Connects securely to your tools. The creator never sees your data.
About this skill
Accessibility bugs are usability bugs experienced through a different input device. This skill is a review pass: run it against a file or apply its rules as a standing constraint on UI work, fix what's broken with the smallest change that works, and prefer native HTML over ARIA every time. The nine rules run in priority order — accessible names, keyboard access, and focus/dialogs first (critical), then semantics and forms (high), then announcements, contrast, and media — with the boundary rule guarding the whole pass: minimal changes, no refactoring unrelated code, no ARIA where native semantics already solve it, no library migration smuggled into the fix.
You get the four common repairs as before/after code (icon-only button, div button, orphaned error, custom dropdown), a violation-report template, an audit decision table, an eleven-item checklist, and a scoring rubric with a ship threshold of 8/10. Edge cases cover dynamically injected controls, over-eager focus traps, live regions that never stop talking, and contrast that passes in one theme and fails in another. A worked example audits a settings page end to end — seven violations, seven minimal fixes, verified keyboard-only.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for UX & UI Design.
- It is a review pass, not a rewrite — large-scale UI restructuring is a different task.
- It does not migrate UI libraries or add ARIA where native semantics already apply.
- Automated checkers catch some violations; keyboard-only testing catches the rest, and the skill requires it.
- It covers HTML interfaces; native mobile accessibility has its own platform rules.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 days ago
Permissions
No special permissions declared or detected