Help us improve
Share bugs, ideas, or general feedback.
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.
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:design-flowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design a new interaction flow that supports diverse input methods and
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.
Designs accessible interactive states, transitions, animations, error handling, loading patterns, and feedback for UI elements, covering visual, screen reader, keyboard, and touch interactions.
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.
Share bugs, ideas, or general feedback.
Design a new interaction flow that supports diverse input methods and provides accessible feedback from the start — not retrofitted after.
List every point in the flow where the user must act:
Using multi-modal-input, for each interaction specify how it works across at least three input methods:
Flag any interaction that only works with one input method.
Using keyboard-navigation, define:
Using touch-target-design, specify:
Using feedback-and-status, for each interaction specify:
Deliver an interaction specification that includes: