ability-spectrum-mapping

Name: ability-spectrum-mapping
Author: Owl-Listener

82stars25forks

How to install ability-spectrum-mapping?

owl-listener/inclusive-design-skills/ability-spectrum-mapping

$npx -y skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping

Installs into the current project.

Summary

Map how a product or feature works across the full spectrum of human ability — not just 'can use' and 'can't use'. Use when planning accessibility coverage, identifying gaps, or communicating accessibility scope to stakeholders. Triggers on: ability spectrum, range of users, who

Files · 1

View on GitHub

SKILL.md

1	# Ability Spectrum Mapping
2
3	Map how a feature performs across the full range of human ability —
4	from full capability to no capability in each dimension — to identify
5	where the design starts to break down and who gets excluded.
6
7	## Why a Spectrum
8
9	Accessibility is not binary. It's not "can see" vs "blind." The
10	reality is a continuous spectrum:
11
12	- Full vision → needs glasses → low vision → legally blind → no vision
13	- Full hearing → mild loss → moderate loss → severe loss → deaf
14	- Full dexterity → mild tremor → limited range → single hand → no hands
15	- Full cognition → mild difficulty → moderate difficulty → significant support needs
16
17	Products don't go from "works" to "doesn't work" in a single step.
18	They degrade gradually. The spectrum map shows you exactly where your
19	design starts failing and for whom.
20
21	## How to Build an Ability Spectrum Map
22
23	### Step 1: List Core Tasks
24	Identify the 5–10 most important tasks a user performs with the product.
25
26	### Step 2: Define the Spectrums
27	For each relevant ability dimension, define 4–5 points:
28
29	Vision spectrum:
30	Full vision → Corrected vision → Low vision (magnification) →
31	Very low vision (screen reader + some vision) → No vision (screen reader only)
32
33	Hearing spectrum:
34	Full hearing → Mild loss (louder volume) → Moderate loss (captions needed) →
35	Severe loss (captions + visual alerts) → Deaf (fully visual communication)
36
37	Motor spectrum:
38	Full dexterity → Reduced precision (larger targets) → Limited range
39	(keyboard only) → Minimal movement (switch or voice) →
40	No hand use (eye tracking, sip-and-puff)
41
42	Cognitive spectrum:
43	Comfortable with complexity → Prefers simplicity → Needs plain language →
44	Needs step-by-step guidance → Needs significant support
45
46	### Step 3: Map Each Task
47
48	For each task × ability point, rate:
49	- Works well — no barriers
50	- Works with friction — possible but harder than it should be
51	- Works with workaround — user must find their own solution
52	- Fails — task cannot be completed
53
54	### Step 4: Identify the Breakpoints
55
56	Where does the design shift from "works" to "fails"? That breakpoint
57	is your accessibility boundary. Everything to the right of it is
58	excluded.
59
60	The goal is to push that boundary as far right as possible.
61
62	## Presenting to Stakeholders
63
64	The spectrum map is a powerful communication tool because it shows:
65	- Exactly how many users are affected at each point
66	- Where investment in accessibility has the highest return
67	- That accessibility is a continuum, not a checkbox
68	- Which fixes would move the boundary and include more people
69
70	## Template
71
72	\| Task \| Full vision \| Low vision \| Screen reader \|
73	\|------\|------------\|-----------\|---------------\|
74	\| Search for a product \| Works well \| Works with friction (small targets) \| Fails (search suggestions not announced) \|
75	\| Complete checkout \| Works well \| Works well \| Works with friction (form errors not associated) \|
76
77	## Assessment Questions
78
79	1. Have you mapped core tasks across at least vision, motor, and
80	cognitive spectrums?
81	2. Can you identify the exact breakpoint where each task fails?
82	3. Do you know which fixes would include the most additional users?
83	4. Can you communicate the spectrum to stakeholders without
84	technical jargon?

People who liked this also viewed

6 picks

Type

ability-spectrum-mapping

82stars25forks

View on GitHub

How to install ability-spectrum-mapping?

owl-listener/inclusive-design-skills/ability-spectrum-mapping

$npx -y skills add Owl-Listener/inclusive-design-skills --skill ability-spectrum-mapping

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Ability Spectrum Mapping
2
3	Map how a feature performs across the full range of human ability —
4	from full capability to no capability in each dimension — to identify
5	where the design starts to break down and who gets excluded.
6
7	## Why a Spectrum
8
9	Accessibility is not binary. It's not "can see" vs "blind." The
10	reality is a continuous spectrum:
11
12	- Full vision → needs glasses → low vision → legally blind → no vision
13	- Full hearing → mild loss → moderate loss → severe loss → deaf
14	- Full dexterity → mild tremor → limited range → single hand → no hands
15	- Full cognition → mild difficulty → moderate difficulty → significant support needs
16
17	Products don't go from "works" to "doesn't work" in a single step.
18	They degrade gradually. The spectrum map shows you exactly where your
19	design starts failing and for whom.
20
21	## How to Build an Ability Spectrum Map
22
23	### Step 1: List Core Tasks
24	Identify the 5–10 most important tasks a user performs with the product.
25
26	### Step 2: Define the Spectrums
27	For each relevant ability dimension, define 4–5 points:
28
29	Vision spectrum:
30	Full vision → Corrected vision → Low vision (magnification) →
31	Very low vision (screen reader + some vision) → No vision (screen reader only)
32
33	Hearing spectrum:
34	Full hearing → Mild loss (louder volume) → Moderate loss (captions needed) →
35	Severe loss (captions + visual alerts) → Deaf (fully visual communication)
36
37	Motor spectrum:
38	Full dexterity → Reduced precision (larger targets) → Limited range
39	(keyboard only) → Minimal movement (switch or voice) →
40	No hand use (eye tracking, sip-and-puff)
41
42	Cognitive spectrum:
43	Comfortable with complexity → Prefers simplicity → Needs plain language →
44	Needs step-by-step guidance → Needs significant support
45
46	### Step 3: Map Each Task
47
48	For each task × ability point, rate:
49	- Works well — no barriers
50	- Works with friction — possible but harder than it should be
51	- Works with workaround — user must find their own solution
52	- Fails — task cannot be completed
53
54	### Step 4: Identify the Breakpoints
55
56	Where does the design shift from "works" to "fails"? That breakpoint
57	is your accessibility boundary. Everything to the right of it is
58	excluded.
59
60	The goal is to push that boundary as far right as possible.
61
62	## Presenting to Stakeholders
63
64	The spectrum map is a powerful communication tool because it shows:
65	- Exactly how many users are affected at each point
66	- Where investment in accessibility has the highest return
67	- That accessibility is a continuum, not a checkbox
68	- Which fixes would move the boundary and include more people
69
70	## Template
71
72	\| Task \| Full vision \| Low vision \| Screen reader \|
73	\|------\|------------\|-----------\|---------------\|
74	\| Search for a product \| Works well \| Works with friction (small targets) \| Fails (search suggestions not announced) \|
75	\| Complete checkout \| Works well \| Works well \| Works with friction (form errors not associated) \|
76
77	## Assessment Questions
78
79	1. Have you mapped core tasks across at least vision, motor, and
80	cognitive spectrums?
81	2. Can you identify the exact breakpoint where each task fails?
82	3. Do you know which fixes would include the most additional users?
83	4. Can you communicate the spectrum to stakeholders without
84	technical jargon?

People who liked this also viewed

6 picks

Type