{
  "ocm": "1",
  "id": "shipshitdev-skills-accessibility",
  "kind": "skill",
  "name": "accessibility",
  "description": "Applies WCAG 2.1 AA to web UI work and fixes what fails — semantic HTML, ARIA roles and states, keyboard access, focus management, contrast ratios, and screen-reader verification — while a component is being built or reviewed. Use when the user names accessibility, a11y, WCAG, ARIA, keyboard navigation, focus traps, screen readers, or contrast. For a scored multi-dimension quality report, use `audit`; for design-token consistency, use `design-consistency-auditor`.",
  "publisher": "shipshitdev",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "accessibility",
      "a11y",
      "wcag",
      "aria",
      "keyboard-navigation",
      "screen-reader",
      "inclusive-design",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Applies WCAG 2.1 AA to web UI work and fixes what fails — semantic HTML, ARIA roles and states, keyboard access, focus management, contrast ratios, and screen-reader verification — while a component is being built or reviewed. Use when the user names accessibility, a11y, WCAG, ARIA, keyboard navigation, focus traps, screen readers, or contrast. For a scored multi-dimension quality report, use `audit`; for design-token consistency, use `design-consistency-auditor`."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/shipshitdev/skills",
      "path": "skills/accessibility/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/shipshitdev/skills/blob/HEAD/skills/accessibility/SKILL.md",
      "key": "shipshitdev/skills/skills/accessibility/SKILL.md"
    }
  },
  "instructions": "# Accessibility (a11y) Skill\n\n## When to Use\n\nUse when you're:\n\n- Creating or reviewing UI components\n- Implementing interactive elements (buttons, forms, modals)\n- Adding keyboard navigation\n- Reviewing color contrast and visual design\n- Testing with screen readers\n- Auditing existing pages for accessibility issues\n- Implementing ARIA attributes\n\n## Quick Workflow\n\n1. Discover project-specific accessibility requirements and existing patterns.\n2. Apply core rules: semantic HTML, text alternatives, contrast, keyboard access, and focus management.\n3. Validate with automated tooling plus manual k",
  "cost": {
    "context_tokens": 320
  }
}