Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
“Fix accessibility issues.”
Install Fixing Accessibility
$ npx skills add kapishdima/soundcn --skill fixing-accessibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kapishdima/soundcn fixing-accessibility --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fixing-accessibility .claude/skills/fixing-accessibility && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fixing-accessibility" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-accessibility into .claude/skills/fixing-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-accessibility", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-accessibilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kapishdima/soundcn --skill fixing-accessibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kapishdima/soundcn fixing-accessibility --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/fixing-accessibility .agents/skills/fixing-accessibility && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fixing-accessibility" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-accessibility into .agents/skills/fixing-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-accessibility", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kapishdima/soundcn --skill fixing-accessibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kapishdima/soundcn fixing-accessibility --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/fixing-accessibility .cursor/skills/fixing-accessibility && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fixing-accessibility" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-accessibility into .cursor/skills/fixing-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-accessibility", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kapishdima/soundcn.git --path .agents/skills/fixing-accessibility--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kapishdima/soundcn --skill fixing-accessibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kapishdima/soundcn fixing-accessibility --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/fixing-accessibility .gemini/skills/fixing-accessibility && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fixing-accessibility" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-accessibility into .gemini/skills/fixing-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-accessibility", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kapishdima/soundcn fixing-accessibilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kapishdima/soundcn --skill fixing-accessibility -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/fixing-accessibility .github/skills/fixing-accessibility && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fixing-accessibility" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-accessibility into .github/skills/fixing-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-accessibility", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kapishdima/soundcn --skill fixing-accessibility -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kapishdima/soundcn fixing-accessibility --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kapishdima/soundcn.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/fixing-accessibility .opencode/skills/fixing-accessibility && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fixing-accessibility" agent skill from https://github.com/kapishdima/soundcn/tree/main/.agents/skills/fixing-accessibility into .opencode/skills/fixing-accessibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fixing-accessibility", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fixing-accessibility- GitHub stars
- 862
- Token cost
- ~982 tokens
- SKILL.md length
- 525 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
- Works in 9 steps: accessible names (critical) → keyboard access (critical) → focus and dialogs (critical) → …
- SKILL.md covers how to use, when to apply, rule categories by priority and quick reference, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
About this skill
Fixing Accessibility is a skill in kapishdima/soundcn (862 stars). Its SKILL.md is about 982 tokens. Licence: MIT.
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7cbfbb3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fixing Accessibility loads about 982 tokens when it runs. Until then it costs about 12 tokens; SKILL.md has 525 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from kapishdima/soundcn at commit 7cbfbb3, republished under its MIT licence (© kapishdima). 525 words, ~982 tokens.
Download SKILL.mdSave it as
.claude/skills/fixing-accessibility/SKILL.md (or your agent's skills folder).- name
- fixing-accessibility
- description
- Fix accessibility issues.
fixing-accessibility
Fix accessibility issues.
how to use
/fixing-accessibilityApply these constraints to any UI work in this conversation./fixing-accessibility <file>Review the file against all rules below and report:- violations (quote the exact line or snippet)
- why it matters (one short sentence)
- a concrete fix (code-level suggestion)
Do not rewrite large parts of the UI. Prefer minimal, targeted fixes.
when to apply
Reference these guidelines when:
- adding or changing buttons, links, inputs, menus, dialogs, tabs, dropdowns
- building forms, validation, error states, helper text
- implementing keyboard shortcuts or custom interactions
- working on focus states, focus trapping, or modal behavior
- rendering icon-only controls
- adding hover-only interactions or hidden content
rule categories by priority
| priority | category | impact |
|---|---|---|
| 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 |
quick reference
1. accessible names (critical)
- every interactive control must have an accessible name
- icon-only buttons must have aria-label or aria-labelledby
- every input, select, and textarea must be labeled
- links must have meaningful text (no “click here”)
- decorative icons must be aria-hidden
2. keyboard access (critical)
- do not use div or span as buttons without full keyboard support
- all interactive elements must be reachable by Tab
- focus must be visible for keyboard users
- do not use tabindex greater than 0
- Escape must close dialogs or overlays when applicable
3. focus and dialogs (critical)
- modals must trap focus while open
- restore focus to the trigger on close
- set initial focus inside dialogs
- opening a dialog should not scroll the page unexpectedly
4. semantics (high)
- prefer native elements (button, a, input) over role-based hacks
- if a role is used, required aria attributes must be present
- lists must use ul or ol with li
- do not skip heading levels
- tables must use th for headers when applicable
Show full SKILL.md (209 more words)Show less
5. forms and errors (high)
- errors must be linked to fields using aria-describedby
- required fields must be announced
- invalid fields must set aria-invalid
- helper text must be associated with inputs
- disabled submit actions must explain why
6. announcements (medium-high)
- critical form errors should use aria-live
- loading states should use aria-busy or status text
- toasts must not be the only way to convey critical information
- expandable controls must use aria-expanded and aria-controls
7. contrast and states (medium)
- ensure sufficient contrast for text and icons
- hover-only interactions must have keyboard equivalents
- disabled states must not rely on color alone
- do not remove focus outlines without a visible replacement
8. media and motion (low-medium)
- images must have correct alt text (meaningful or empty)
- videos with speech should provide captions when relevant
- respect prefers-reduced-motion for non-essential motion
- avoid autoplaying media with sound
9. tool boundaries (critical)
- prefer minimal changes, do not refactor unrelated code
- do not add aria when native semantics already solve the problem
- do not migrate UI libraries unless requested
review guidance
- fix critical issues first (names, keyboard, focus, tool boundaries)
- prefer native HTML before adding aria
- quote the exact snippet, state the failure, propose a small fix
- for complex widgets (menu, dialog, combobox), prefer established accessible primitives over custom behavior
© kapishdima, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/fixing-accessibility of kapishdima/soundcn.
Open the folder on GitHubat commit 7cbfbb3
Compare with similar skills
Fixing Accessibility next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fixing Accessibility this skillkapishdima/soundcn | 862 | — | ~982 | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 98 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.5k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Wcag Audit PatternsvmDeshpande/ai-agent-automation | 178 | 11 repos | ~610 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
More from kapishdima/soundcn
Generate Creative Ideas
kapishdima/soundcn
Creative problem-solving and ideation using SCAMPER, First Principles, Random Word, and AI-optimized techniques.
Fixing Metadata
kapishdima/soundcn
Ship correct, complete metadata.
Fixing Motion Performance
kapishdima/soundcn
Fix animation performance issues.
Related
Categories
Questions about Fixing Accessibility
How do I install Fixing Accessibility in Claude Code?
Run `npx skills add kapishdima/soundcn --skill fixing-accessibility -a claude-code`. Or copy the skill folder (.agents/skills/fixing-accessibility in kapishdima/soundcn) into .claude/skills/fixing-accessibility in your project. Claude Code loads it when a task matches its description.
How do I install Fixing Accessibility in Codex?
Run `npx skills add kapishdima/soundcn --skill fixing-accessibility -a codex`. Or copy the skill folder (.agents/skills/fixing-accessibility in kapishdima/soundcn) into .agents/skills/fixing-accessibility in your project. Codex loads it when a task matches its description.
Can I use Fixing Accessibility in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kapishdima/soundcn --skill fixing-accessibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fixing-accessibility, .gemini/skills/fixing-accessibility, .github/skills/fixing-accessibility and .opencode/skills/fixing-accessibility in your project.
What does Fixing Accessibility need to run?
SKILL.md names no scripts, command-line tools or credentials: Fixing Accessibility is instructions for the agent only.
Does Fixing Accessibility access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Fixing Accessibility safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fixing Accessibility use?
Fixing Accessibility is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fixing Accessibility use?
About 982 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fixing Accessibility?
Skills that share tags, products or a category with Fixing Accessibility: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fixing Accessibility?
kapishdima (a GitHub user) maintains it in kapishdima/soundcn, which has 862 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on June 9, 2026.
Source: kapishdima/soundcn on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.