compliance-mapping

Name: compliance-mapping
Author: Owl-Listener

82stars25forks

How to install compliance-mapping?

owl-listener/inclusive-design-skills/compliance-mapping

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

Installs into the current project.

Summary

Map design decisions to accessibility standards and legal requirements. Use when documenting WCAG conformance, preparing for audits, tracking compliance status, or when legal or procurement requires accessibility documentation. Triggers on: WCAG, compliance, conformance, audit, V

Files · 1

View on GitHub

SKILL.md

1	# Compliance Mapping
2
3	Map design decisions to specific accessibility standards so the team
4	knows exactly where they stand — what's covered, what's not, and
5	what's at risk.
6
7	## Why Designers Need This
8
9	Compliance mapping is usually treated as an engineering audit task.
10	But most conformance failures originate in design decisions made
11	before code was written. A designer who understands which standards
12	their decisions affect can prevent failures instead of discovering
13	them.
14
15	## Key Standards
16
17	### WCAG 2.2 Level AA
18	The global baseline. Most laws reference this.
19	- Level A: minimum (29 criteria)
20	- Level AA: standard target (20 additional criteria)
21	- Level AAA: aspirational (28 additional criteria)
22
23	Most organisations target Level AA. Some criteria in Level AAA
24	are worth adopting even if not required (especially cognitive
25	accessibility criteria).
26
27	### Legal Frameworks
28	- ADA (US): requires accessible digital services, courts
29	reference WCAG 2.1 AA
30	- EAA (EU): European Accessibility Act, effective June 2025,
31	references EN 301 549 which aligns with WCAG 2.1 AA
32	- Section 508 (US government): references WCAG 2.0 AA,
33	update expected
34	- EN 301 549 (EU): the technical standard behind EAA,
35	aligned with WCAG 2.1 AA plus additional requirements for
36	software, hardware, and documentation
37
38	## Design Decision to WCAG Mapping
39
40	### Colour and Visual Design
41	\| Design decision \| WCAG criteria \|
42	\|----------------\|---------------\|
43	\| Text contrast ratios \| 1.4.3 Contrast (Minimum) AA \|
44	\| Non-text contrast \| 1.4.11 Non-text Contrast AA \|
45	\| Colour not sole indicator \| 1.4.1 Use of Color A \|
46	\| Text resizing to 200% \| 1.4.4 Resize Text AA \|
47	\| Content reflow at zoom \| 1.4.10 Reflow AA \|
48	\| Text spacing override \| 1.4.12 Text Spacing AA \|
49
50	### Interaction Design
51	\| Design decision \| WCAG criteria \|
52	\|----------------\|---------------\|
53	\| Keyboard operability \| 2.1.1 Keyboard A \|
54	\| No keyboard traps \| 2.1.2 No Keyboard Trap A \|
55	\| Focus visible \| 2.4.7 Focus Visible AA \|
56	\| Focus order logical \| 2.4.3 Focus Order A \|
57	\| Touch target size \| 2.5.8 Target Size (Minimum) AA \|
58	\| No motion-only input \| 2.5.4 Motion Actuation A \|
59	\| Gesture alternatives \| 2.5.1 Pointer Gestures A \|
60
61	### Content and Structure
62	\| Design decision \| WCAG criteria \|
63	\|----------------\|---------------\|
64	\| Page titles \| 2.4.2 Page Titled A \|
65	\| Heading hierarchy \| 1.3.1 Info and Relationships A \|
66	\| Link purpose clear \| 2.4.4 Link Purpose (In Context) A \|
67	\| Language of page set \| 3.1.1 Language of Page A \|
68	\| Consistent navigation \| 3.2.3 Consistent Navigation AA \|
69	\| Error identification \| 3.3.1 Error Identification A \|
70	\| Labels on inputs \| 3.3.2 Labels or Instructions A \|
71
72	### Motion and Timing
73	\| Design decision \| WCAG criteria \|
74	\|----------------\|---------------\|
75	\| Pause/stop/hide motion \| 2.2.2 Pause, Stop, Hide A \|
76	\| No flashing content \| 2.3.1 Three Flashes A \|
77	\| Timing adjustable \| 2.2.1 Timing Adjustable A \|
78	\| Animation from interaction \| 2.3.3 Animation from Interactions AAA \|
79
80	## How to Use This
81
82	### During Design
83	Before finalising a design decision, check which WCAG criteria
84	it affects. This catches failures at the cheapest point to fix them.
85
86	### During Review
87	Map the design against the relevant criteria table. Flag any
88	decision that would cause a conformance failure.
89
90	### For Audit Preparation
91	Use the mapping tables to create a pre-audit checklist specific
92	to your product. This tells auditors exactly which decisions map
93	to which criteria.
94
95	## Assessment Questions
96
97	1. Can the team map their key design decisions to WCAG criteria?
98	2. Are there design decisions that would cause conformance failures?
99	3. Does the team know which legal frameworks apply to their product?
100	4. Is there a process for checking designs against standards before
101	implementation?

People who liked this also viewed

6 picks

Type

compliance-mapping

82stars25forks

View on GitHub

How to install compliance-mapping?

owl-listener/inclusive-design-skills/compliance-mapping

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Compliance Mapping
2
3	Map design decisions to specific accessibility standards so the team
4	knows exactly where they stand — what's covered, what's not, and
5	what's at risk.
6
7	## Why Designers Need This
8
9	Compliance mapping is usually treated as an engineering audit task.
10	But most conformance failures originate in design decisions made
11	before code was written. A designer who understands which standards
12	their decisions affect can prevent failures instead of discovering
13	them.
14
15	## Key Standards
16
17	### WCAG 2.2 Level AA
18	The global baseline. Most laws reference this.
19	- Level A: minimum (29 criteria)
20	- Level AA: standard target (20 additional criteria)
21	- Level AAA: aspirational (28 additional criteria)
22
23	Most organisations target Level AA. Some criteria in Level AAA
24	are worth adopting even if not required (especially cognitive
25	accessibility criteria).
26
27	### Legal Frameworks
28	- ADA (US): requires accessible digital services, courts
29	reference WCAG 2.1 AA
30	- EAA (EU): European Accessibility Act, effective June 2025,
31	references EN 301 549 which aligns with WCAG 2.1 AA
32	- Section 508 (US government): references WCAG 2.0 AA,
33	update expected
34	- EN 301 549 (EU): the technical standard behind EAA,
35	aligned with WCAG 2.1 AA plus additional requirements for
36	software, hardware, and documentation
37
38	## Design Decision to WCAG Mapping
39
40	### Colour and Visual Design
41	\| Design decision \| WCAG criteria \|
42	\|----------------\|---------------\|
43	\| Text contrast ratios \| 1.4.3 Contrast (Minimum) AA \|
44	\| Non-text contrast \| 1.4.11 Non-text Contrast AA \|
45	\| Colour not sole indicator \| 1.4.1 Use of Color A \|
46	\| Text resizing to 200% \| 1.4.4 Resize Text AA \|
47	\| Content reflow at zoom \| 1.4.10 Reflow AA \|
48	\| Text spacing override \| 1.4.12 Text Spacing AA \|
49
50	### Interaction Design
51	\| Design decision \| WCAG criteria \|
52	\|----------------\|---------------\|
53	\| Keyboard operability \| 2.1.1 Keyboard A \|
54	\| No keyboard traps \| 2.1.2 No Keyboard Trap A \|
55	\| Focus visible \| 2.4.7 Focus Visible AA \|
56	\| Focus order logical \| 2.4.3 Focus Order A \|
57	\| Touch target size \| 2.5.8 Target Size (Minimum) AA \|
58	\| No motion-only input \| 2.5.4 Motion Actuation A \|
59	\| Gesture alternatives \| 2.5.1 Pointer Gestures A \|
60
61	### Content and Structure
62	\| Design decision \| WCAG criteria \|
63	\|----------------\|---------------\|
64	\| Page titles \| 2.4.2 Page Titled A \|
65	\| Heading hierarchy \| 1.3.1 Info and Relationships A \|
66	\| Link purpose clear \| 2.4.4 Link Purpose (In Context) A \|
67	\| Language of page set \| 3.1.1 Language of Page A \|
68	\| Consistent navigation \| 3.2.3 Consistent Navigation AA \|
69	\| Error identification \| 3.3.1 Error Identification A \|
70	\| Labels on inputs \| 3.3.2 Labels or Instructions A \|
71
72	### Motion and Timing
73	\| Design decision \| WCAG criteria \|
74	\|----------------\|---------------\|
75	\| Pause/stop/hide motion \| 2.2.2 Pause, Stop, Hide A \|
76	\| No flashing content \| 2.3.1 Three Flashes A \|
77	\| Timing adjustable \| 2.2.1 Timing Adjustable A \|
78	\| Animation from interaction \| 2.3.3 Animation from Interactions AAA \|
79
80	## How to Use This
81
82	### During Design
83	Before finalising a design decision, check which WCAG criteria
84	it affects. This catches failures at the cheapest point to fix them.
85
86	### During Review
87	Map the design against the relevant criteria table. Flag any
88	decision that would cause a conformance failure.
89
90	### For Audit Preparation
91	Use the mapping tables to create a pre-audit checklist specific
92	to your product. This tells auditors exactly which decisions map
93	to which criteria.
94
95	## Assessment Questions
96
97	1. Can the team map their key design decisions to WCAG criteria?
98	2. Are there design decisions that would cause conformance failures?
99	3. Does the team know which legal frameworks apply to their product?
100	4. Is there a process for checking designs against standards before
101	implementation?

People who liked this also viewed

6 picks

Type