disability-inclusive-personas
Create user personas that include disability as a natural dimension of human diversity — not as a separate 'accessibility persona'. Use when creating personas, user profiles, proto-personas, or any representation of target users. Triggers on: persona, user persona, proto-persona, user profile, target user, who is the user, disability persona, accessibility persona, inclusive persona.
- Installs
- 75
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill disability-inclusive-personas- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads disability-inclusive-personas automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Disability-Inclusive Personas
Build personas where disability is woven into the full picture of a person — their goals, frustrations, context, and behaviour — not isolated as a special category.
The Problem with "Accessibility Personas"
Most teams either:
- Create personas with no mention of disability at all, or
- Create separate "accessibility personas" that exist only to represent a disability
Both fail. The first excludes. The second reduces a person to their disability and ensures they're only considered when someone remembers to look at the "accessibility slide."
The Better Approach
Every persona set should include disability as one dimension among many — the same way you include age, technical confidence, or context of use. Some personas will have disabilities. All personas exist in contexts that create situational impairment.
Persona Dimensions to Include
For every persona, consider:
Permanent Disability
- Visual: blind, low vision, colour vision deficiency
- Hearing: deaf, hard of hearing
- Motor: limited dexterity, tremor, paralysis, limb difference
- Cognitive: dyslexia, ADHD, autism, memory difficulties
- Speech: stutter, non-verbal, atypical speech
Temporary Impairment
- Broken arm, eye surgery recovery, concussion, medication side effects, ear infection, dental procedure
Situational Impairment
- Bright sunlight on screen, noisy environment, carrying a child, wearing gloves, driving, multitasking, unfamiliar language, emotional distress, fatigue
Intersectionality
- A persona can have multiple conditions
- Disability intersects with age, language, income, technical skill
- A 65-year-old with low vision AND limited broadband AND a second language has compounding access barriers
How to Include Disability Naturally
In the Bio
Don't: "Sarah is blind." Do: "Sarah is a project manager who has been blind since birth. She uses JAWS screen reader on her work laptop and VoiceOver on her iPhone. She's fast with keyboard shortcuts and gets frustrated by interfaces that waste her time."
In Goals and Frustrations
Don't: list disability under "Challenges" Do: show how the disability shapes what good and bad experiences look like. "Sarah's goal is to review her team's status updates in under 10 minutes. Her biggest frustration is dashboards that require a mouse to access key data."
In Context of Use
Include the assistive technology and environment:
- What device and assistive technology do they use?
- What's their environment? (noisy, quiet, mobile, desktop)
- What's their energy level? (morning, end of long day)
- Who else is present? (alone, with family, in public)
In the Scenario
The persona's scenario should show them using the product with their actual setup — not a theoretical clean-room test.
Minimum Diversity Rule
For any persona set of 4 or more:
- At least one persona should have a permanent disability
- At least one persona should have a situational impairment
- At least two personas should vary in technical confidence
- The set should vary across age, language, and context
This is a minimum, not a target.
Assessment Questions
- Does the persona set include at least one person with a disability?
- Is disability integrated into the full persona, not isolated?
- Are assistive technology and environment specified?
- Does the persona's scenario reflect real-world usage with their setup?
- Are situational impairments represented across the set?
FAQ
What does the disability-inclusive-personas skill do?
Create user personas that include disability as a natural dimension of human diversity — not as a separate 'accessibility persona'. Use when creating personas, user profiles, proto-personas, or any representation of target users. Triggers on: persona, user persona, proto-persona, user profile, target user, who is the user, disability persona, accessibility persona, inclusive persona.
How do I install disability-inclusive-personas?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill disability-inclusive-personas in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/disability-inclusive-personas/ (personal) or .claude/skills/disability-inclusive-personas/ (project).
Which AI agents can use disability-inclusive-personas?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is disability-inclusive-personas safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains disability-inclusive-personas?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 75 recorded installs.
More from owl-listener/inclusive-design-skills
plain-language-design
owl-listener/inclusive-design-skills
Write and review content for plain language accessibility. Use when writing interface copy, error messages, instructions, onboarding text, help content, legal or medical information, forms, or any user-facing text. Triggers on: plain language, reading level, simplify text, jargon, hard to understand, nobody reads this, unclear copy, rewrite, too complicated, ESL, literacy, readability.
keyboard-navigation
owl-listener/inclusive-design-skills
Design keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen. Use when designing any interactive interface — forms, menus, modals, tabs, carousels, drag-and-drop, data tables, or custom components. Triggers on: keyboard, focus, tab order, focus trap, skip link, arrow keys, keyboard shortcut, can't use mouse, motor disability, switch access, focus indicator, focus ring.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Assess and reduce cognitive load in interfaces, flows, and content. Use when designing or reviewing any multi-step process, complex form, dashboard, decision flow, or information-dense screen. Triggers on: cognitive load, too complex, overwhelmed, too many steps, decision fatigue, confusing, information overload, simplify this flow. Applies to any interface where users must think, decide, or remember.
responsive-review
owl-listener/inclusive-design-skills
Review responsive and flexible layout for accessibility across devices, zoom levels, and orientations. Chains: responsive-accessibility, flexible-typography, information-density. Use when testing an existing interface across screen sizes and zoom levels for accessibility.
user-preference-respect
owl-listener/inclusive-design-skills
Design interfaces that detect and respond to system-level user preferences. Use when implementing dark mode, reduced motion, high contrast, text scaling, or any user preference that affects how the interface renders. Triggers on: user preference, system preference, prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, media query, user settings, system settings, accessibility settings, OS settings.
error-prevention-recovery
owl-listener/inclusive-design-skills
Design error prevention, error messages, and recovery flows for cognitive accessibility. Use when designing forms, checkout flows, account creation, settings, data entry, or any flow where users can make mistakes. Triggers on: error handling, error messages, form errors, validation, users make mistakes, users abandon, error recovery, undo, forgiving design.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.