Help us improve
Share bugs, ideas, or general feedback.
Guides designing interfaces where users can accomplish tasks via keyboard, mouse, touch, voice, switch, eye tracking, or head pointer. Covers input equivalence, flexible text entry, and alternatives for complex interactions.
npx claudepluginhub owl-listener/inclusive-design-skills --plugin inclusive-interactionHow this skill is triggered — by the user, by Claude, or both
Slash command
/inclusive-interaction:multi-modal-inputThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design systems where users can accomplish any task through whichever
Designs interaction flows with inclusive input options (keyboard, pointer, voice) and accessible feedback. Use when building new features or interfaces to incorporate accessibility from the start.
Treats accessibility as a design discipline covering WCAG 2.2, screen readers, keyboard navigation, cognitive/motor accessibility, and testing methodology. Activates on accessibility reviews, inclusive design checks, and compliance questions.
Designs accessible interactive states, transitions, animations, error handling, loading patterns, and feedback for UI elements, covering visual, screen reader, keyboard, and touch interactions.
Share bugs, ideas, or general feedback.
Design systems where users can accomplish any task through whichever input method works for them — keyboard, mouse, touch, voice, switch, eye tracking, or any combination.
Never assume how someone will interact with your interface. Offer choices. Let the user decide.
People interact with technology through many methods, often combining several at once: