Help us improve
Share bugs, ideas, or general feedback.
Maps design decisions to WCAG conformance and legal requirements (ADA, EAA, Section 508, EN 301 549). Use for accessibility audits, VPATs, and compliance documentation.
npx claudepluginhub owl-listener/inclusive-design-skills --plugin accessibility-decisionsHow this skill is triggered — by the user, by Claude, or both
Slash command
/accessibility-decisions:compliance-mappingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Map design decisions to specific accessibility standards so the team
Captures accessibility decisions, tradeoffs, and WCAG compliance for a feature during design or shipping.
Audits designs for WCAG 2.2 AA violations (contrast, focus, target size, keyboard semantics, motion, cognition). Auto-activates on designer tasks.
Audits UI components against WCAG 2.2, Section 508, and ARIA requirements. Provides automated and manual steps for color, keyboard, screen reader, form, and motion accessibility.
Share bugs, ideas, or general feedback.
Map design decisions to specific accessibility standards so the team knows exactly where they stand — what's covered, what's not, and what's at risk.
Compliance mapping is usually treated as an engineering audit task. But most conformance failures originate in design decisions made before code was written. A designer who understands which standards their decisions affect can prevent failures instead of discovering them.
The global baseline. Most laws reference this.
Most organisations target Level AA. Some criteria in Level AAA are worth adopting even if not required (especially cognitive accessibility criteria).
| Design decision | WCAG criteria |
|---|---|
| Text contrast ratios | 1.4.3 Contrast (Minimum) AA |
| Non-text contrast | 1.4.11 Non-text Contrast AA |
| Colour not sole indicator | 1.4.1 Use of Color A |
| Text resizing to 200% | 1.4.4 Resize Text AA |
| Content reflow at zoom | 1.4.10 Reflow AA |
| Text spacing override | 1.4.12 Text Spacing AA |
| Design decision | WCAG criteria |
|---|---|
| Keyboard operability | 2.1.1 Keyboard A |
| No keyboard traps | 2.1.2 No Keyboard Trap A |
| Focus visible | 2.4.7 Focus Visible AA |
| Focus order logical | 2.4.3 Focus Order A |
| Touch target size | 2.5.8 Target Size (Minimum) AA |
| No motion-only input | 2.5.4 Motion Actuation A |
| Gesture alternatives | 2.5.1 Pointer Gestures A |
| Design decision | WCAG criteria |
|---|---|
| Page titles | 2.4.2 Page Titled A |
| Heading hierarchy | 1.3.1 Info and Relationships A |
| Link purpose clear | 2.4.4 Link Purpose (In Context) A |
| Language of page set | 3.1.1 Language of Page A |
| Consistent navigation | 3.2.3 Consistent Navigation AA |
| Error identification | 3.3.1 Error Identification A |
| Labels on inputs | 3.3.2 Labels or Instructions A |
| Design decision | WCAG criteria |
|---|---|
| Pause/stop/hide motion | 2.2.2 Pause, Stop, Hide A |
| No flashing content | 2.3.1 Three Flashes A |
| Timing adjustable | 2.2.1 Timing Adjustable A |
| Animation from interaction | 2.3.3 Animation from Interactions AAA |
Before finalising a design decision, check which WCAG criteria it affects. This catches failures at the cheapest point to fix them.
Map the design against the relevant criteria table. Flag any decision that would cause a conformance failure.
Use the mapping tables to create a pre-audit checklist specific to your product. This tells auditors exactly which decisions map to which criteria.