Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From inclusive-personas
Guides writing usage scenarios that include assistive technology and diverse interaction methods for inclusive design.
npx claudepluginhub owl-listener/inclusive-design-skills --plugin inclusive-personasHow this skill is triggered — by the user, by Claude, or both
Slash command
/inclusive-personas:assistive-technology-scenariosThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write scenarios that show real people using real assistive technology
Creates inclusive personas, user stories, and scenarios representing permanent, temporary, and situational abilities for diverse design contexts.
Maps inclusive usage scenarios across ability spectrums to identify accessibility gaps in products or features. Chains with ability-spectrum-mapping and assistive-technology-scenarios for test planning.
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.
Write scenarios that show real people using real assistive technology to complete real tasks — so the team designs for actual usage, not imagined ideal conditions.
If your scenarios only describe people using a mouse and a large monitor, your design will only work for people using a mouse and a large monitor. Scenarios shape what teams consider. What they consider, they design for.
Don't just name the disability. Describe the person, their technology, and their environment.
"Priya is a data analyst who uses JAWS screen reader with Firefox on a Windows laptop. She's fast with keyboard shortcuts and has two monitors — one for her spreadsheets, one for the tool she's reviewing. She's at her desk with noise-cancelling headphones."
Describe how the person actually moves through the interface with their technology:
"Priya tabs to the navigation menu. JAWS announces 'Navigation, 5 items.' She presses the down arrow to find 'Reports' and presses Enter. The page loads and JAWS announces the H1: 'Monthly Reports.' She presses H to jump through headings until she finds 'March 2026.'"
The scenario should surface design failures:
"Priya reaches the data table but JAWS announces each cell without column headers. She hears '42,500' but doesn't know which metric or which month. She tabs past the table looking for a text summary but there isn't one."
For any product, write scenarios for at least:
Name: [Name]
Role/context: [Who they are beyond their disability]
Technology: [Devices, AT, browser, settings]
Environment: [Where, when, what else is happening]
Task: [What they're trying to accomplish]
Steps: [How they interact, step by step, using their AT]
Pain points: [Where the design fails or creates friction]
Success: [What a good outcome looks like for this person]