ui-review
Audits web UI components for accessibility and UX against WCAG 2.1 AA, reporting each violation as `[CRITICAL|IMPORTANT|MINOR] — file:line` with a specific fix. Use when the user asks about accessibility, a11y, WCAG, screen readers, keyboard navigation, or color contrast, or wants a UX pass over components.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- ui-review
- description
- Audits web UI components for accessibility and UX against WCAG 2.1 AA, reporting each violation as `[CRITICAL|IMPORTANT|MINOR] — file:line` with a specific fix. Use when the user asks about accessibility, a11y, WCAG, screen readers, keyboard navigation, or color contrast, or wants a UX pass over components.
- allowed-tools
- Read, Grep, Glob
02 资源文件 2
- 参考文档agents/openai.yaml113 B
- 参考文档checklist.md1.7 KB
03 SKILL.md 正文
UI Review
Audit web components (HTML, CSS, or framework code) against WCAG 2.1 AA and report each violation with its severity, location, and fix.
Three rules carry the most weight:
- Every interactive element is keyboard-accessible: anything clickable is reachable with Tab and activates with Enter or Space.
- Focus rings stay visible: keep a
:focus-visibleoutline such asoutline: 2px solid;outline: nonehides focus from keyboard users. - Color is never the only signal: status, errors, and links also carry text or an icon.
1. Check the components
Read the components in scope and check each against checklist.md, which covers:
- Forms: labels, validation, autocomplete
- Keyboard navigation: tab order, visible focus
- Color and contrast: WCAG AA ratios
- Semantic HTML: headings, lists, navigation
- Images and icons: alt text,
aria-hidden - Loading states: no layout shift, announcements
- Motion:
prefers-reduced-motion, transitions
Done when every component in scope has been checked against every checklist category.
2. Report
Give each violation a severity: CRITICAL blocks release, IMPORTANT is needed before the PR, MINOR is nice to have.
[CRITICAL|IMPORTANT|MINOR] — file:line
Rule: [rule name]
Issue: [what is wrong]
Fix: [specific code change]
Summary: N critical, M important, P minor. Ready: [YES|NO]
Done when every violation has a file:line and a specific fix, and the
summary gives the counts by severity and a Ready-for-PR verdict.
04 同仓库更多 Skills
teach
Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.
svg-logo-designer
Generate SVG logos with multiple concepts, layouts, and color variations.
documentation-writer
Writes and revises human-facing documentation — READMEs, contributor and setup guides, reference pages, architecture notes, CLAUDE.md, and changelog entries. Covers picking the right document type for the question being asked, structuring for skimming, writing examples that actually run, and keeping docs from going stale. Use when creating or rewriting docs, when a README has drifted from the code, or when deciding where a piece of information belongs. For SKILL.md and agent files, use /skill-writer instead.
adhd-mode
Shapes every response for a reader with ADHD: the next action first, numbered steps, progress restated each turn, tangents held back, concrete time estimates, wins made visible. Stays on for the rest of the session until the reader says "stop adhd mode". On Claude Code, the harness-kit:adhd output style does the same without invoking this skill.
wait-what
That last message didn't land: re-explain it with the missing context.
to-questionnaire
Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.