fixing-accessibility skill (ibelick): audit and fix HTML accessibility

Makes your agent audit UI code for accessibility problems and propose small, targeted fixes.

Installs: 22.6K; on skills.sh
Stars: 10.5K; on GitHub
Updated: Nov 2026; last repo commit

fixing-accessibility makes your agent check UI code against a short rule list: accessible names, keyboard access, focus and dialogs, semantics, form errors, announcements, contrast and motion. Use /fixing-accessibility to apply the rules to all UI work in the conversation. Use /fixing-accessibility <file> to get a review of one file.

A review quotes each violating line, says why it matters in one sentence and gives a code-level fix. The skill tells the agent to avoid large rewrites. It bundles one file and no scripts.

Good for

Front-end developers building forms, dialogs and menus
Reviewers checking a component against WCAG-style rules
Designers who want keyboard and screen reader basics checked

Install fixing-accessibility

Claude Code

Copy this prompt.

Install the fixing-accessibility skill in Claude Code. Run this command:

npx skills add https://github.com/ibelick/ui-skills --skill fixing-accessibility

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.

Sections in SKILL.md

how to use
when to apply
rule categories by priority
quick reference
1. accessible names (critical)
2. keyboard access (critical)
3. focus and dialogs (critical)
4. semantics (high)
5. forms and errors (high)
6. announcements (medium-high)
7. contrast and states (medium)
8. media and motion (low-medium)
9. tool boundaries (critical)
common fixes
review guidance

Key facts

Author: ibelick (ui-skills)
Repository: ibelick/ui-skills (skills/fixing-accessibility)
Installs on skills.sh: 22,606 as of 2026-11-02
GitHub stars: 10,454 for the whole ibelick/ui-skills repo, 2026-11-02
License: MIT (as detected by GitHub)
Last commit to the repo: 2026-11-01
What is inside: 1 file (SKILL.md only)

What it includes

Apply the rules to any UI work in this conversation
The agent follows the accessibility constraints while it builds or edits UI.
Try: “/fixing-accessibility Build a modal for deleting a project.”
Write · /fixing-accessibility
Review one file and report violations, reasons and fixes
For each problem the agent quotes the line, says why it matters in one sentence, and suggests a concrete fix.
Try: “/fixing-accessibility src/components/SignupForm.tsx”
Read · /fixing-accessibility <file>
Names, keyboard, focus, semantics, forms, announcements, contrast, media, tool boundaries
Ranked by priority. Accessible names, keyboard access, focus and dialogs, and tool boundaries are marked critical.
Read · Nine rule categories
Three before and after examples
Adding aria-label to an icon-only button, using a native button instead of a div, and linking a form error to its field with aria-describedby.
Read · Common fixes
Critical issues first, native HTML before ARIA
Quote the snippet, state the failure, propose a small fix. For complex widgets, prefer established accessible primitives.
Read · Review guidance

From the official docs

Questions

What does the fixing-accessibility skill do?

It makes your agent follow a set of accessibility rules for UI code. It can apply them while building, or review a single file and list violations with fixes.

How do I use it?

Type /fixing-accessibility to apply the rules to the current conversation. Type /fixing-accessibility <file> to review one file. The description also lists adding interactive controls, forms and dialogs as triggers.

How do I install it in Claude Code, the Claude app or Codex?

Use the install box at the top of this page. The ui-skills README documents the ui-skills command and does not name which clients this skill works in.

Does it check color contrast automatically?

The skill bundles no scripts. Its contrast rule says to ensure sufficient contrast for text and icons, and your agent applies that by reading the code.

Will it rewrite my whole UI?

No. The skill says not to rewrite large parts of the UI, to prefer minimal targeted fixes, and not to migrate UI libraries unless you ask.

Does it replace a real accessibility audit?

No. It is a short rule list read by your agent. Test with a keyboard and a screen reader for anything that matters.

Is it safe to install?

It is one markdown file that bundles no scripts and lists no shell commands. The changes your agent makes to your code are the risk, so review the diff.

Information

updated Nov 2, 2026

Repository: ibelick/ui-skills
Folder: skills/fixing-accessibility

ibelick/ui-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2

fixing-accessibility SKILL.md · github.com
ibelick/ui-skills README · github.com