preference-audit

Name: preference-audit
Author: Owl-Listener

82stars25forks

How to install preference-audit?

owl-listener/inclusive-design-skills/preference-audit

$npx -y skills add Owl-Listener/inclusive-design-skills --skill preference-audit

Installs into the current project.

Summary

Audit an existing interface for respect of user preferences including motion, contrast, colour scheme, and text scaling. Chains: user-preference-respect, responsive-accessibility, colour-independence. Use when reviewing an existing product for adaptive behaviour.

Files · 1

View on GitHub

SKILL.md

1	# User Preference Audit
2
3	Test whether an existing interface correctly detects and responds to
4	user preferences — the accessibility settings people have deliberately
5	chosen.
6
7	## Process
8
9	### Step 1: Test Motion Preferences
10	Using user-preference-respect, enable prefers-reduced-motion and
11	navigate the entire interface. Document:
12	- Animations that continue playing
13	- Transitions that still slide or fade
14	- Parallax effects that remain active
15	- Autoplay video or carousels that don't stop
16	- Any motion that serves no functional purpose
17
18	### Step 2: Test Contrast and Colour Preferences
19	Enable prefers-contrast (more) and forced-colors mode. Using
20	user-preference-respect and colour-independence, document:
21	- Elements that become invisible or indistinguishable
22	- Focus indicators that disappear
23	- Interactive elements that lose their borders
24	- Colour-only status indicators that become meaningless
25	- Charts or visualisations that become unreadable
26
27	### Step 3: Test Colour Scheme
28	Switch between light and dark modes. Document:
29	- Content that becomes illegible in one mode
30	- Images or icons that don't adapt
31	- Hardcoded colours that clash with the theme
32	- Contrast failures specific to one mode
33
34	### Step 4: Test Text Scaling and Zoom
35	Using responsive-accessibility, test at 200% browser zoom
36	and with system font size at maximum. Document:
37	- Text that overflows or gets clipped
38	- Layouts that break or overlap
39	- Horizontal scrolling that appears
40	- Fixed-height containers that truncate content
41	- Interactive elements that become unreachable
42
43	### Step 5: Test Combinations
44	Test realistic combinations:
45	- Dark mode + high contrast + reduced motion
46	- 200% zoom + large system font
47	- Forced colours + reduced motion
48
49	Document any failures that only appear in combination.
50
51	## Output
52
53	Deliver an audit report:
54
55	1. Summary — which preferences are respected, which are ignored
56	2. Preference-by-preference findings — specific failures for each
57	3. Combination failures — issues that appear only when multiple
58	preferences are active
59	4. Fix list — prioritised by severity and number of users affected
60
61	Severity definitions:
62	- Critical — preference is completely ignored, causing harm or
63	blocking access
64	- Major — preference is partially respected, significant gaps remain
65	- Minor — preference is mostly respected, edge cases need fixing

People who liked this also viewed

6 picks

Type

preference-audit

82stars25forks

View on GitHub

How to install preference-audit?

owl-listener/inclusive-design-skills/preference-audit

$npx -y skills add Owl-Listener/inclusive-design-skills --skill preference-audit

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# User Preference Audit
2
3	Test whether an existing interface correctly detects and responds to
4	user preferences — the accessibility settings people have deliberately
5	chosen.
6
7	## Process
8
9	### Step 1: Test Motion Preferences
10	Using user-preference-respect, enable prefers-reduced-motion and
11	navigate the entire interface. Document:
12	- Animations that continue playing
13	- Transitions that still slide or fade
14	- Parallax effects that remain active
15	- Autoplay video or carousels that don't stop
16	- Any motion that serves no functional purpose
17
18	### Step 2: Test Contrast and Colour Preferences
19	Enable prefers-contrast (more) and forced-colors mode. Using
20	user-preference-respect and colour-independence, document:
21	- Elements that become invisible or indistinguishable
22	- Focus indicators that disappear
23	- Interactive elements that lose their borders
24	- Colour-only status indicators that become meaningless
25	- Charts or visualisations that become unreadable
26
27	### Step 3: Test Colour Scheme
28	Switch between light and dark modes. Document:
29	- Content that becomes illegible in one mode
30	- Images or icons that don't adapt
31	- Hardcoded colours that clash with the theme
32	- Contrast failures specific to one mode
33
34	### Step 4: Test Text Scaling and Zoom
35	Using responsive-accessibility, test at 200% browser zoom
36	and with system font size at maximum. Document:
37	- Text that overflows or gets clipped
38	- Layouts that break or overlap
39	- Horizontal scrolling that appears
40	- Fixed-height containers that truncate content
41	- Interactive elements that become unreachable
42
43	### Step 5: Test Combinations
44	Test realistic combinations:
45	- Dark mode + high contrast + reduced motion
46	- 200% zoom + large system font
47	- Forced colours + reduced motion
48
49	Document any failures that only appear in combination.
50
51	## Output
52
53	Deliver an audit report:
54
55	1. Summary — which preferences are respected, which are ignored
56	2. Preference-by-preference findings — specific failures for each
57	3. Combination failures — issues that appear only when multiple
58	preferences are active
59	4. Fix list — prioritised by severity and number of users affected
60
61	Severity definitions:
62	- Critical — preference is completely ignored, causing harm or
63	blocking access
64	- Major — preference is partially respected, significant gaps remain
65	- Minor — preference is mostly respected, edge cases need fixing

People who liked this also viewed

6 picks

Type