skills.rest
lilbom32
lilbom32COMMUNITY
Explore all skills by this author →
GitHub

accessibility-review

Identify WCAG 2.1 AA compliance gaps in designs and frontend code.

Updated Mar 15, 2026
Search Tags:#accessibility#a11y#wcag#color-contrast#screen-readers#ui-audit#keyboard-access
One-click install
npx skills add https://github.com/lilbom32/ketnoitrithuc --skill accessibility-review-lilbom32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-review
Source: https://github.com/lilbom32/ketnoitrithuc/tree/main/.claude/skills/design/1.1.0/skills/accessibility-review
Command: npx skills add https://github.com/lilbom32/ketnoitrithuc --skill accessibility-review-lilbom32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WCAG 2.1 AA accessibility gaps in designs and frontend code can prevent a large portion of users with disabilities from effectively using digital products. This guide helps identify and remediate those issues early in design and development.

Core Features & Use Cases

  • Comprehensive WCAG audit: Evaluate perceivable, operable, understandable, and robust aspects across UI, content, and components.
  • Hybrid testing approach: Combine automated scans with manual validation for reliable results.
  • Actionable remediation guidance: Provide concrete fixes, suggested code changes, and documentation updates to close WCAG gaps.
  • Use cases: Designers, product teams, and developers validating accessibility during design review and feature rollout.

Quick Start

Run an automated accessibility review on your project to identify WCAG 2.1 AA gaps.

Frequently Asked Questions about accessibility-review

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

FAQPage Schema
How do I audit my UI designs for WCAG 2.1 AA accessibility compliance?▼

Run an automated accessibility review to identify WCAG 2.1 AA gaps in semantic structure, keyboard operability, color contrast, alt text, focus management, and ARIA labeling across your UI components and pages.

How does a hybrid accessibility testing approach work for frontend code?▼

A hybrid accessibility approach combines automated scans with manual validation to reliably identify WCAG 2.1 AA gaps in frontend code, ensuring color contrast, ARIA labeling, and focus management meet guidelines.

What's the best way to check color contrast and keyboard access in a design system?▼

Apply WCAG 2.1 AA accessibility audits across design system components to validate color contrast ratios, keyboard operability, focus management, and ARIA labeling through automated checks and manual validation.

Can I use this to fix ARIA labeling and semantic structure gaps?▼

Yes, it identifies ARIA labeling and semantic structure gaps and provides actionable remediation guidance, suggested code changes, and documentation updates to close WCAG 2.1 AA compliance issues in frontend code.

Does automated accessibility testing catch all WCAG screen-reader compliance issues?▼

Automated testing alone does not catch all WCAG screen-reader compliance issues. Manual validation is required alongside automated scans to ensure semantic structure, alt text, and ARIA labeling fully meet WCAG 2.1 AA guidelines.

Related Skills

Explore More Design & Creative Skills→
t-stringst-strings

Frontend Accessibility

Review frontend UI code for HTML semantics, ARIA, keyboard navigation, and contrast.

Official
Basic
cypxxccypxxc
1

Accessibility Audit

Audit React components for WCAG 2.1 AA accessibility gaps.

Community
Intermediate
wredziowredzio

accessibility

Identify and remediate WCAG 2.1 AA accessibility issues in web pages.

Community
Advanced
PrasadTelasulaPrasadTelasula

accessibility-compliance

Implement WCAG 2.1 AA accessibility across QA Team Portal interfaces with ARIA roles, keyboard navigation, and color contrast fixes.

Community
Advanced