ux-inclusive-design

Audits interfaces against WCAG 2.2 criteria and Microsoft Inclusive Design Persona Spectrum methodology.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/geekatron/jerry-claude-plugin --skill ux-inclusive-design-geekatron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-inclusive-design
Source: https://github.com/geekatron/jerry-claude-plugin/tree/main/skills/ux-inclusive-design
Command: npx skills add https://github.com/geekatron/jerry-claude-plugin --skill ux-inclusive-design-geekatron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping digital products often lack a systematic way to evaluate accessibility, leaving them exposed to ADA, EAA, and Section 508 compliance risk and excluding users with permanent, temporary, or situational disabilities. This Skill performs structured WCAG 2.2 conformance audits and inclusive design analysis so accessibility barriers are identified and prioritized before launch. ## Core Features & Use Cases - WCAG 2.2 Compliance Auditing: Evaluates success criteria across Perceivable, Operable, Understandable, and Robust principles at conformance levels A, AA, and AAA, with per-criterion pass/fail evidence and severity ratings aligned to Nielsen's scale. - Persona Spectrum Analysis: Maps each interaction pattern across visual, motor, auditory, and cognitive disability types in permanent, temporary, and situational durations using Microsoft Inclusive Design methodology. - Specialized Test Protocols: Covers color contrast ratio measurement, keyboard navigation and focus management, screen reader compatibility (ARIA, landmarks, alt text), and cognitive load assessment including reading level evaluation. - Use Case: A small team preparing a checkout flow for release asks for a WCAG 2.2 AA audit; the Skill produces a full accessibility report with contrast measurements, keyboard findings, persona spectrum profiles, and a prioritized remediation backlog with WCAG technique references. ## Quick Start Ask the /user-experience skill to audit your checkout flow for WCAG 2.2 AA compliance and it will route the request to this sub-skill's evaluator agent.

Frequently Asked Questions about ux-inclusive-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a web interface for WCAG 2.2 compliance?

Invoke the parent /user-experience skill with a request like "audit this page for WCAG 2.2 AA compliance" and the orchestrator routes it to this sub-skill. The evaluator checks every success criterion up to your target level across the four POUR principles and produces per-criterion pass/fail findings with evidence and remediation.

What is a Persona Spectrum analysis in inclusive design?

A Persona Spectrum analysis maps each interaction pattern across four disability types (visual, motor, auditory, cognitive) and three durations (permanent, temporary, situational), following Microsoft's Inclusive Design methodology. It identifies exclusion points and shows how solving for permanent disabilities extends benefits to all users.

Does this skill work without Figma MCP access?

Yes, it falls back to screenshot-input mode where you provide design screenshots and hex/RGB color values manually. In degraded mode, contrast ratios require user-provided color values, and keyboard findings are flagged as structural assessments requiring manual verification.

Can this skill replace manual accessibility testing with screen readers?

No. The evaluation is structural, assessing semantic HTML and ARIA implementation, but it cannot replicate actual screen reader experiences across JAWS, NVDA, or VoiceOver. Severity 3-4 findings should be validated with automated tools like axe-core and manual assistive technology testing.

When should I use heuristic evaluation instead of accessibility auditing?

Use /ux-heuristic-eval for general usability evaluation against Nielsen's 10 heuristics. This sub-skill focuses specifically on accessibility barriers and WCAG conformance; it does not cover broader usability concerns outside the accessibility scope.