Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jpoindexter/inclusive-design
The inclusive-design philosophy and practice — Microsoft's 3 principles + Persona Spectrum, the social model of disability as mismatch, and deep cognitive, neurodivergent, sensory, cultural, economic, and age inclusion patterns that go beyond WCAG conformance.
Passed 21 of 22 test cases with the skill, and 20 of 22 without it.
2 fixed19 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are establishing the core design tenets for our product team based on industry-standard inclusive design frameworks. A team member proposed starting by recruiting diverse participants for usability testing at the end of the sprint, then finding universal solutions that work for everyone, and finally auditing excluded groups. Correct this proposed workflow according to established inclusive design principles, detailing the proper sequential order and what each step requires.
| Checked | Without skill | With skill |
|---|---|---|
| Specifies that identifying and naming who is excluded by default choices must occur first | Passed | Passed |
| Requires starting design with a permanent constraint and extending the solution to temporary and situational cases | Missed | Passed |
| Mandates involving diverse users as co-designers early in the process rather than as end-of-sprint test subjects | Passed | Passed |
The instructions your model reads when the skill loads.
Accessibility is the floor (a conformance outcome — see the accessibility-and-inclusive-design skill for WCAG 2.2 mechanics: contrast ratios, ARIA, keyboard, screen readers). Inclusive design is the method that gets you there and further: a way of working that recognizes who has been left out, designs deliberately for human diversity, and treats exclusion as a property of the design, not the person. This skill is the philosophy and the cognitive/neuro/cultural/economic practice. It does not repeat WCAG numbers — it tells you who you are excluding, why, and what to build instead.
| Term | Origin | What it is | Shape of the solution |
|---|---|---|---|
| Accessible design | WCAG / EN 301 549 / standards bodies | An outcome: the product meets defined criteria so disabled people can use it. Measurable, often legally required. | One product, audited against a checklist. |
| Universal design | Ronald Mace, NC State, 1985; 7 Principles | One solution that works for the widest range of people without adaptation. An ideal end-state. | One design, no variants. |
| Inclusive design | Microsoft Inclusive Design Toolkit; Kat Holmes, Mismatch (2018) | A process: design with human diversity as the input, often shipping plural paths so each person can self-select. | Many adaptable paths; the design flexes. |
The practical distinction: universal design seeks the single ramp everyone uses; inclusive design accepts you may need a ramp and stairs and an elevator, and lets the person choose. Accessibility is what you can be sued for; inclusion is what makes the product good. Aim for accessible as the non-negotiable baseline, design inclusively to exceed it.
Mace's 7 Principles of Universal Design (NC State Center for Universal Design) are still a useful audit lens, even where you ship plural paths rather than one solution: (1) equitable use — same means for all where possible, equivalent where not; (2) flexibility in use — accommodate preferences and abilities; (3) simple and intuitive — independent of experience, language, or concentration level; (4) perceptible information — convey it redundantly (visual + verbal + tactile), not in one channel; (5) tolerance for error — minimize hazards of accidental action; (6) low physical effort; (7) size and space for approach and use. Read these as questions to ask of any screen.
The medical model locates disability in the body: the person is broken, fix the person. The social model (term coined by disability scholar Mike Oliver, 1983; rooted in the disability-rights movement) locates it in the mismatch between a person and their environment: a person using a wheelchair is not disabled by their legs but by the staircase. Change the environment and the disability disappears.
For designers this reframes everything: you are the source of exclusion, and therefore you can remove it. A signup form that rejects a hyphenated surname disables that user — the user is fine, the regex is wrong. Microsoft's phrasing: design creates "mismatched interactions" between a person's abilities and the product's demands. Your job is to find and close those mismatches.
From the Microsoft Inclusive Design Toolkit. Memorize and apply them in order.
| Principle | Meaning | In practice |
|---|---|---|
| 1. Recognize exclusion | Every design choice includes some and excludes others. Bias toward your own abilities is invisible to you. Name who your default excludes. | "This drag-to-reorder excludes anyone who can't drag." "This idiom excludes literal and non-native readers." |
| 2. Solve for one, extend to many | Design for a person with a permanent constraint, and the solution scales to everyone who shares that constraint situationally or temporarily. | Captions built for Deaf users serve everyone in a loud bar or silent train. One-handed flows built for an amputee serve a parent holding a baby. |
| 3. Learn from diversity | People who experience exclusion are the experts on it. Bring them in as co-designers, not test subjects at the end. | Recruit disabled, neurodivergent, multilingual, low-bandwidth users into research before the design is locked. |
"Solve for one, extend to many" worked end-to-end: start with a blind user who can't see a "drag the photo here" uploader. Solve it — add a keyboard-operable file picker with a clear text label and status announcements. That same fix now serves a motor-impaired user who can't drag precisely (permanent), a user with a trackpad failing (temporary), and a user on a phone with one thumb (situational). One accessibility fix, four populations served. This is the inverse of the usual cost framing: inclusive solutions compound in reach.
The Toolkit's central tool: every "disability" exists as permanent, temporary, and situational variants. Designing for the permanent case automatically covers a vastly larger population in the temporary and situational columns. Microsoft's canonical example is the one-arm spectrum (amputee / arm injury / new parent holding a baby).
| Ability affected | Permanent | Temporary | Situational |
|---|
test cases passed, vs 20 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.