ss-a11y
Audit a component or page for accessibility issues and fix them
Profile →npx skills add bitjaru/styleseed --skill ss-a11y --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Accessibility Audit ## When NOT to use - For general design system compliance review → use `/ss-review` - For Nielsen UX heuristics → use `/ss-audit` - For non-StyleSeed code (no `data-slot`, no semantic tokens) — assumes StyleSeed conventions - For runtime testing — this is a static code audit, not a screen-reader simulation Target: **$ARGUMENTS** ## Audit Criteria ### WCAG 2.2 AA Compliance #### 1. Perceivable - **Color contrast**: Text must meet 4.5:1 (normal) or 3:1 (large/bold text) - Check `text-muted-foreground` (#717182) on `bg-background` (#FFFFFF) = 4.6:1 (passes) - Check `text-brand` on white (verify contrast with your skin's brand color) - Flag any custom colors that don't meet ratio - **Non-text contrast**: UI controls/graphics must meet 3:1 - **Text alternatives**: All `<img>` need `alt`, icons need `aria-label` when meaningful - **Color independence**: Don't convey info by color alone (add icons/text) #### 2. Operable - **Touch targets**: Minimum 44x44px (`min-h-11 min-w-11`) - Common violation: `h-9` (36px) buttons — should be `h-11` - Icon buttons need explicit size: `w-11 h-11` - **Keyboard navigation**: All interactive elements must be keyboard-accessible - Tab
- When NOT to use
- Audit Criteria
- WCAG 2.2 AA Compliance
- Design System Token Reference
- Output
What does the ss-a11y skill do?
Audit a component or page for accessibility issues and fix them
How do I install it?
Run `npx skills add bitjaru/styleseed --skill ss-a11y --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From bitjaru/styleseed, a repository with 867 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.