From loopkit
Audits interactive components for common accessibility failures: keyboard navigation, labels, contrast, semantics, and focus. Run after building any UI.
How this skill is triggered — by the user, by Claude, or both
Slash command
/loopkit:a11y-passWhen to use
forms, buttons, modals, images, color choices, keyboard interaction
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- **Keyboard** — every interactive element reachable and operable by Tab/Enter/Esc. Modals trap focus and restore it on close.
<label>; icon-only buttons have aria-label.alt; decorative images alt="".<button>/<a>, not a clickable <div>. Headings in order.outline: none without a replacement.
Output: each failure with the element + the fix. Test it with Tab only, no mouse.npx claudepluginhub archive228/loopkitAutomatically checks code and elements for accessibility issues when users ask about WCAG compliance or accessibility. Performs focused checks on components, forms, or pages.
Audits web/app accessibility covering semantics, keyboard flow, focus, labels, ARIA, contrast, and responsive behavior. Useful for frontend changes or existing UI needing accessibility review.
Audits and fixes HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.