accessibility-review

Audit designs or web pages against WCAG 2.1 AA accessibility criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify accessibility gaps in a design or page before handoff so people using assistive technologies can use it effectively and comfortably.

Core Features & Use Cases

  • WCAG 2.1 AA audit: Evaluates common accessibility areas like contrast, keyboard navigation, touch target size, screen reader behavior, and robust semantics.
  • Structured findings: Produces a prioritized report with severity and recommended fixes mapped to relevant WCAG criteria.
  • Practical testing guidance: Suggests a workflow that combines automated scanning, keyboard-only checks, screen reader testing, and contrast verification.

Quick Start

Use the /accessibility-review skill with your Figma URL, page URL, or a short description of the design you want audited.

Frequently Asked Questions about accessibility-review

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

FAQPage Schema
How do I run a WCAG 2.1 AA accessibility audit on a web page?

Run a WCAG 2.1 AA accessibility audit by providing a Figma URL, web page URL, or design description to evaluate color contrast, keyboard operability, touch target sizing, screen reader semantics, and form labeling.

How do I map design review findings to specific WCAG criteria?

Map design review findings to specific WCAG criteria by generating a structured, prioritized report that details severity levels and recommended fixes directly aligned with the relevant WCAG 2.1 AA accessibility requirements.

Can I audit a Figma design for screen reader semantics and touch target size?

Yes, you can audit a Figma design for screen reader semantics and touch target size by submitting the Figma URL to identify usability and compliance gaps prior to development handoff.

What workflow should I use for accessibility testing alongside automated scanning?

Use an accessibility testing workflow that combines automated scanning with keyboard-only checks, screen reader testing, and contrast verification to comprehensively surface WCAG 2.1 AA compliance gaps.

Why does my web page fail keyboard operability and form labeling checks?

Your web page fails keyboard operability and form labeling checks when it lacks proper semantic HTML and ARIA attributes, which this audit identifies and maps to specific WCAG criteria with actionable recommendations.