skills.rest
ruskicoder
ruskicoderCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-review

Audits designs and pages for WCAG 2.1 AA accessibility compliance.

3|Updated Jun 29, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#audit#wcag#color contrast
One-click install
npx skills add https://github.com/ruskicoder/system-prompts --skill accessibility-review-ruskicoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-review
Source: https://github.com/ruskicoder/system-prompts/tree/main/prompt-orchestrator/.opencode/skills/accessibility-review
Command: npx skills add https://github.com/ruskicoder/system-prompts --skill accessibility-review-ruskicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and web pages often ship with accessibility barriers like insufficient color contrast, missing form labels, and broken keyboard navigation that block users with disabilities and create legal risk. This Skill runs a structured WCAG 2.1 AA audit so issues are found and prioritized before handoff. ## Core Features & Use Cases - WCAG 2.1 AA Checklist Audit: Reviews Perceivable, Operable, Understandable, and Robust criteria including contrast ratios, keyboard access, focus indicators, and ARIA roles. - Structured Findings Report: Outputs severity-ranked findings tables, color contrast checks, keyboard navigation maps, and screen reader behavior notes. - Use Case: Before handing off a Figma design to engineering, run the audit to catch contrast failures, missing labels, and focus traps, then create tracker tickets for each finding. ## Quick Start Ask the AI to audit accessibility of your Figma URL or page description against WCAG 2.1 AA and produce a severity-ranked findings report.

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?▼

Provide a Figma URL, page URL, or description and the audit checks Perceivable, Operable, Understandable, and Robust criteria. It returns a findings report with severity levels, WCAG criterion references, and recommended fixes.

What color contrast ratio is required for WCAG AA?▼

WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text under criterion 1.4.3. Non-text UI components and graphics need at least 3:1 under criterion 1.4.11.

Can an automated audit catch all accessibility issues?▼

No, automated scans catch roughly 30% of issues. A complete audit also requires keyboard-only navigation testing, screen reader testing with VoiceOver or NVDA, contrast verification, and zooming to 200% to check layout.

What are the most common accessibility issues in designs?▼

The most common issues are insufficient color contrast, missing form labels, no keyboard access to interactive elements, missing alt text, focus traps in modals, missing ARIA landmarks, auto-playing media, and time limits without extensions.

What are the limitations of an AI accessibility review?▼

An AI audit cannot fully replicate manual testing with real assistive technology like VoiceOver or NVDA, which catches issues automation misses. It works best as a first-pass review prioritized by user impact before manual verification.

Related Skills

Explore More Design & Creative Skills→
ValyayValyay

figma-audit

Compare live UI screenshots against Figma references and report visual discrepancies.

Community
Advanced
hpsgdhpsgd

accessibility-audit

Audit web UI codebases for WCAG 2.1 AA compliance and generate remediation reports.

Official
Advanced
wshobsonwshobson
38.6k

screen-reader-testing

Test web applications for accessibility compliance with VoiceOver, NVDA, and JAWS.

Community
Intermediate
Community-AccessCommunity-Access
387

lighthouse-bridge

Parse Lighthouse CI reports and track accessibility score regressions.

Official
Advanced