Bmad UX
aj-geddes/claude-code-bmad-skills
Solutioning-phase UX planning skill (optional; activate when the project has a UI).
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
Install Assistive Technology Scenarios
$ npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills assistive-technology-scenarios --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/inclusive-personas/skills/assistive-technology-scenarios .claude/skills/assistive-technology-scenarios && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "assistive-technology-scenarios" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/assistive-technology-scenarios into .claude/skills/assistive-technology-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assistive-technology-scenarios", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/assistive-technology-scenariosType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills assistive-technology-scenarios --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/inclusive-personas/skills/assistive-technology-scenarios .agents/skills/assistive-technology-scenarios && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "assistive-technology-scenarios" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/assistive-technology-scenarios into .agents/skills/assistive-technology-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assistive-technology-scenarios", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills assistive-technology-scenarios --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/inclusive-personas/skills/assistive-technology-scenarios .cursor/skills/assistive-technology-scenarios && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "assistive-technology-scenarios" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/assistive-technology-scenarios into .cursor/skills/assistive-technology-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assistive-technology-scenarios", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path inclusive-personas/skills/assistive-technology-scenarios--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills assistive-technology-scenarios --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/inclusive-personas/skills/assistive-technology-scenarios .gemini/skills/assistive-technology-scenarios && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "assistive-technology-scenarios" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/assistive-technology-scenarios into .gemini/skills/assistive-technology-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assistive-technology-scenarios", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills assistive-technology-scenariosInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/inclusive-personas/skills/assistive-technology-scenarios .github/skills/assistive-technology-scenarios && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "assistive-technology-scenarios" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/assistive-technology-scenarios into .github/skills/assistive-technology-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assistive-technology-scenarios", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills assistive-technology-scenarios --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/inclusive-personas/skills/assistive-technology-scenarios .opencode/skills/assistive-technology-scenarios && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "assistive-technology-scenarios" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/assistive-technology-scenarios into .opencode/skills/assistive-technology-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assistive-technology-scenarios", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
assistive-technology-scenarios- GitHub stars
- 105
- Token cost
- ~1.1k tokens
- SKILL.md length
- 520 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
- Works in 4 steps: Does the scenario name specific… → Does it describe step-by-step… → Does it surface specific design failures? → …
- Writing usage scenarios or user journeys that include assistive technology
- SKILL.md covers Why This Matters, Common Assistive Technologies, How to Write AT Scenarios and Scenario Coverage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Scenarios that only describe a mouse and a large monitor produce designs that only work that way, so this skill makes assistive technology part of the story. It supplies a reference list by need: vision (screen readers such as JAWS, NVDA, VoiceOver and TalkBack, magnifiers, braille displays, high contrast mode), motor (switch devices, voice control, head pointers and eye tracking, mouth sticks), hearing (captions, visual alerts, hearing loops) and cognitive (text-to-speech, reading rulers, simplified views, password managers).
For each scenario you describe the person, their technology and their environment rather than just naming a disability. The skill's example introduces a data analyst who uses JAWS with Firefox on a Windows laptop and two monitors. The interaction is then written step by step, including what the technology announces as the person moves through the interface, so the team sees actual usage instead of imagined ideal conditions.
When your agent uses it
- Writing usage scenarios or user journeys that include assistive technology
- Drafting storyboards for how people with different abilities use a product
- Reviewing existing use cases for mouse-only assumptions
Example prompts
- “Write a usage scenario for our checkout flow where the customer uses a screen reader.”
- “Add a switch-device user to the onboarding journey and show each step they take.”
- “Rewrite these use cases so they cover voice control and a screen magnifier.”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Does the scenario name specific assistive technology, not just
- Does it describe step-by-step interaction, not just the goal?
- Does it surface specific design failures?
- Would a developer reading this know what to fix?
What it can do on your machine
Read from SKILL.md and the folder at commit 6e0740f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Assistive Technology Scenarios loads about 1.1k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 520 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 520 words, ~1,094 tokens.
Download SKILL.mdSave it as
.claude/skills/assistive-technology-scenarios/SKILL.md (or your agent's skills folder).- name
- assistive-technology-scenarios
- description
- Write usage scenarios that include assistive technology and diverse interaction methods. Use when writing scenarios, use cases, user journeys, or storyboards. Triggers on: assistive technology, AT, screen reader, switch, voice control, magnifier, braille display, head pointer, eye tracking, how people use our product, usage scenario, use case.
Assistive Technology Scenarios
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.
Why This Matters
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.
Common Assistive Technologies
Vision
- Screen reader (JAWS, NVDA, VoiceOver, TalkBack): reads content aloud, navigates by headings, links, and landmarks via keyboard
- Screen magnifier (ZoomText, built-in zoom): enlarges a portion of the screen, user sees only a fraction at a time
- Braille display: converts text to braille in real time, used alongside a screen reader
- High contrast mode: system-level colour override for readability
Motor
- Switch device: one or two buttons that scan through options — much slower than keyboard, every extra step matters
- Voice control (Dragon, Voice Control, Voice Access): speaks commands to navigate and type
- Head pointer / eye tracking: cursor controlled by head movement or eye gaze — precision is limited
- Mouth stick / stylus: physical pointer for touchscreens or keyboards
Hearing
- Captions: real-time or pre-recorded text for audio content
- Visual alerts: flashing screen or visual indicator replacing audio notifications
- Hearing loop / Bluetooth: direct audio to hearing aids
Cognitive
- Text-to-speech: reads content aloud (not a screen reader — the user can see the screen but processes better by hearing)
- Reading ruler / line guide: highlights one line at a time
- Simplified view: browser extensions or settings that strip clutter
- Password managers: reduce memory burden for authentication
How to Write AT Scenarios
Include the Setup
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."
Show full SKILL.md (197 more words)Show less
Show the Interaction Step by Step
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.'"
Show Where It Breaks
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."
Scenario Coverage
For any product, write scenarios for at least:
- One screen reader user completing the core task
- One keyboard-only user completing the core task
- One user with low vision using magnification
- One user with a cognitive difference
- One user in a situational impairment context
Template
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]Assessment Questions
- Does the scenario name specific assistive technology, not just the disability?
- Does it describe step-by-step interaction, not just the goal?
- Does it surface specific design failures?
- Would a developer reading this know what to fix?
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in inclusive-personas/skills/assistive-technology-scenarios of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Assistive Technology Scenarios next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Assistive Technology Scenarios this skillOwl-Listener/inclusive-design-skills | 105 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Bmad UXaj-geddes/claude-code-bmad-skills | 488 | — | ~2k | Automated safety check: Notes | Custom licence | |
| Prototypeplugin87/ux-ui-agent-skills | 1.6k | — | ~614 | Automated safety check: Pass | MIT | |
| Product UX Expertmajiayu000/spellbook | 287 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Color Auditrome-os/rome | 748 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Product Designeraakashg/pm-claude-skills | 112 | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Prototype
plugin87/ux-ui-agent-skills
Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts.
Product UX Expert
majiayu000/spellbook
Product interaction and UX expert. An agent skill from majiayu000/spellbook.
Color Audit
rome-os/rome
Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…
Product Designer
aakashg/pm-claude-skills
A skill your agent uses when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues.
Dont Make Me Think
luongnv89/skills
Review UI usability using Steve Krug's principles and produce a scannable report.
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoError Prevention and Recovery
Owl-Listener/inclusive-design-skills
Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.
Accessible Heading Structure
Owl-Listener/inclusive-design-skills
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Ability Spectrum Mapping
Owl-Listener/inclusive-design-skills
Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Accessibility Testing Strategy
Owl-Listener/inclusive-design-skills
Plan what to test, how to test, and who should test for accessibility.
Alt Text Design
Owl-Listener/inclusive-design-skills
Write meaningful alternative text for images, charts, diagrams, and visual content.
Related
Questions about Assistive Technology Scenarios
What does Assistive Technology Scenarios do?
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks. Scenarios that only describe a mouse and a large monitor produce designs that only work that way, so this skill makes assistive technology part of the story. It supplies a reference list by need: vision (screen readers such as JAWS, NVDA, VoiceOver and TalkBack, magnifiers, braille displays, high contrast mode), motor (switch devices, voice control, head pointers and eye tracking, mouth sticks), hearing (captions, visual alerts, hearing loops) and cognitive (text-to-speech, reading rulers, simplified views, password managers).
When should I use Assistive Technology Scenarios?
Assistive Technology Scenarios fits situations like: writing usage scenarios or user journeys that include assistive technology; drafting storyboards for how people with different abilities use a product; reviewing existing use cases for mouse-only assumptions.
How do I install Assistive Technology Scenarios in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a claude-code`. Or copy the skill folder (inclusive-personas/skills/assistive-technology-scenarios in Owl-Listener/inclusive-design-skills) into .claude/skills/assistive-technology-scenarios in your project. Claude Code loads it when a task matches its description.
How do I install Assistive Technology Scenarios in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a codex`. Or copy the skill folder (inclusive-personas/skills/assistive-technology-scenarios in Owl-Listener/inclusive-design-skills) into .agents/skills/assistive-technology-scenarios in your project. Codex loads it when a task matches its description.
Can I use Assistive Technology Scenarios in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/inclusive-design-skills --skill assistive-technology-scenarios -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/assistive-technology-scenarios, .gemini/skills/assistive-technology-scenarios, .github/skills/assistive-technology-scenarios and .opencode/skills/assistive-technology-scenarios in your project.
What does Assistive Technology Scenarios need to run?
SKILL.md names no scripts, command-line tools or credentials: Assistive Technology Scenarios is instructions for the agent only.
Does Assistive Technology Scenarios access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Assistive Technology Scenarios safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Assistive Technology Scenarios use?
Assistive Technology Scenarios is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Assistive Technology Scenarios use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Assistive Technology Scenarios?
Skills that share tags, products or a category with Assistive Technology Scenarios: Bmad UX (aj-geddes/claude-code-bmad-skills, 488 stars), Prototype (plugin87/ux-ui-agent-skills, 1.6k stars), Product UX Expert (majiayu000/spellbook, 287 stars) and Color Audit (rome-os/rome, 748 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Assistive Technology Scenarios?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 105 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.