accessibility-review

Audits designs/pages against WCAG 21 AA producing severity-ranked issue reports with mapping to criteria.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/sun2443/designer-skills --skill accessibility-review-sun2443
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-review
Source: https://github.com/sun2443/designer-skills/tree/main/design/skills/accessibility-review
Command: npx skills add https://github.com/sun2443/designer-skills --skill accessibility-review-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch accessibility problems early so users can navigate, read, and interact with products regardless of disabilities or assistive technology needs.

Core Features & Use Cases

  • WCAG 2.1 AA audits: Evaluates a design or page against key perceivable, operable, understandable, and robust criteria.
  • Practical issue reporting: Summarizes issues by severity (critical/major/minor) and maps findings to specific WCAG criteria with recommendations.
  • Design-review scenarios: Used during handoff to validate contrast, keyboard navigation, touch target sizing, screen reader behavior, and form labeling.

Quick Start

Run accessibility-review on the linked Figma design when you want an immediate WCAG 2.1 AA audit for color contrast, keyboard navigation, touch targets, and screen reader considerations.

Frequently Asked Questions about accessibility-review

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

FAQPage Schema
How do I audit a design for WCAG 2.1 AA accessibility compliance?

To audit a design for WCAG 2.1 AA accessibility, evaluate contrast ratios, keyboard navigation, touch target sizing, and screen reader semantics to identify issues across perceivable, operable, understandable, and robust categories.

What is included in a WCAG 2.1 AA accessibility findings report?

A WCAG 2.1 AA accessibility findings report includes issue summaries, severity levels categorized as critical, major, or minor, specific WCAG criterion mapping, and actionable recommendations for resolving the identified barriers.

How do I check color contrast and touch targets during a design handoff?

Check color contrast and touch targets during a design handoff by validating contrast ratios against WCAG standards and measuring touch target sizing to ensure operability for users with disabilities or assistive technology needs.

Can I evaluate keyboard navigation and screen reader semantics for Figma designs?

You can evaluate keyboard navigation and screen reader semantics by running an accessibility review on the linked Figma design to validate focus behavior, form labeling, and overall operability for assistive technologies.

What is the best way to map accessibility issues to specific WCAG criteria?

The best way to map accessibility issues to specific WCAG criteria is to generate a structured findings report that pairs each identified perceivable or operable barrier with its corresponding WCAG 2.1 AA criterion and actionable recommendations.

Why does my design review fail keyboard navigation and focus behavior checks?

Your design review fails keyboard navigation and focus behavior checks when the evaluated page lacks proper operability semantics, preventing users who rely on assistive technology from navigating interactive elements effectively.