skills.rest
richtabor
richtaborCOMMUNITY
Explore all skills by this author →
Website𝕏@richtaborGitHub

accessibility-review

Identify accessibility issues in UI components against WCAG 2.1/2.2 Level AA.

69|11|Updated Dec 30, 2025
Search Tags:#ui#checklist#accessibility#a11y#wcag#review
One-click install
npx skills add https://github.com/richtabor/agent-skills --skill accessibility-review-richtabor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-review
Source: https://github.com/richtabor/agent-skills/tree/main/skills/accessibility-review
Command: npx skills add https://github.com/richtabor/agent-skills --skill accessibility-review-richtabor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams identify and prioritize accessibility issues in UI components, pages, and applications against WCAG 2.1/2.2 Level AA, making accessibility reviews practical and actionable.

Core Features & Use Cases

  • One-at-a-time accessibility review workflow that surfaces Critical and Warning findings with concrete fixes and file locations.
  • References the WCAG 2.1/2.2 checklist and applies it to target UI elements, pages, or designs.
  • Use cases include auditing a component (button, form, modal), validating color contrast, and validating accessibility during design reviews and QA checks.

Quick Start

Ask the skill to review a UI target for accessibility, for example: "Is this accessible?"

Frequently Asked Questions about accessibility-review

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

FAQPage Schema
How do I check if my UI components meet WCAG 2.1 AA accessibility standards?▼

You can check UI components against WCAG 2.1 Level AA by running a one-at-a-time accessibility review that surfaces Critical and Warning findings with concrete fixes and file locations.

What is the best way to audit a web page for a11y issues during design reviews?▼

The best way to audit for a11y issues during design reviews is applying the WCAG 2.1/2.2 checklist to target elements, ensuring practical validation of individual components or full screen designs.

Can I validate color contrast and form accessibility for specific page elements?▼

Yes, you can validate color contrast and form accessibility by targeting specific UI elements like buttons or modals, which generates prioritized findings with actionable fixes referenced against the WCAG checklist.

How does a component-level accessibility audit handle prioritized findings?▼

A component-level accessibility audit handles prioritized findings by enforcing a one-at-a-time workflow that categorizes issues into Critical and Warning levels, providing specific file locations and actionable fixes.

Does this accessibility review workflow support both development QA and design phases?▼

Yes, the accessibility review workflow supports both development QA and design phases, applying WCAG 2.1/2.2 Level AA standards to UI components, pages, and applications to validate accessibility.

When do I need an accessibility audit for my application's screen designs?▼

You need an accessibility audit for screen designs when someone asks if a UI target is accessible, requiring validation against WCAG 2.1 Level AA to identify and prioritize issues with actionable fixes.

Related Skills

Explore More Design & Creative Skills→
factorialcofactorialco
27

a11y

Enforce WCAG 2.1/2.2 Level AA accessibility standards in UI components.

Official
Intermediate
Dzakiamriz22Dzakiamriz22
1

ui-review

Audit frontend UI components across eight design dimensions and refactor failing code.

Community
Advanced
petbrainspetbrains
13

frontend-design-review

Review frontend UI/UX designs for accessibility and responsive behavior.

Official
Basic
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate