Styleseed ss-a11y

Audit a component or page for accessibility issues and fix them

install
source · Clone the upstream repo
git clone https://github.com/bitjaru/styleseed
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/bitjaru/styleseed "$T" && mkdir -p ~/.claude/skills && cp -r "$T/engine/.claude/skills/ss-a11y" ~/.claude/skills/bitjaru-styleseed-ss-a11y && rm -rf "$T"
manifest: engine/.claude/skills/ss-a11y/SKILL.md
source content

Accessibility Audit

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 order should be logical
    • focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2
  • Motion: Animations must respect
    prefers-reduced-motion
    @media (prefers-reduced-motion: reduce) {
      *, *::before, *::after {
        animation-duration: 0.01ms !important;
        transition-duration: 0.01ms !important;
      }
    }
    

3. Understandable

  • Labels: Form inputs must have visible labels or
    aria-label
  • Error messages: Form errors must be programmatically associated (
    aria-describedby
    )
  • Language:
    <html lang="en">
    (or appropriate language code for your project)

4. Robust

  • Semantic HTML: Use appropriate elements (
    <button>
    ,
    <nav>
    ,
    <main>
    ,
    <header>
    )
  • ARIA: Use Radix UI components (they handle ARIA automatically)
  • Roles: Custom interactive elements need proper
    role
    attributes

Design System Token Reference

TokenMinimum ContrastNote
--foreground
7:1+Body text — verify with your skin
--muted-foreground
4.5:1+Secondary text — verify with your skin
--brand
4.5:1+Accent — verify with your skin's brand color
--destructive
4.5:1+Error — verify with your skin
--success
3:1+Large text/icons only — verify with your skin
--warning
4.5:1+Warning text — some skins need a darker variant

Output

  1. Issues found: List with severity (Critical/Major/Minor)
  2. Auto-fixes: Apply fixes directly where possible
  3. Manual review needed: Flag items that need human judgment