skills.rest
kiryteo
kiryteoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility-review

Audits designs and code for WCAG 2.1 AA compliance.

1|Updated Mar 9, 2026
Search Tags:#accessibility#a11y#contrast#screen-reader#keyboard-navigation#wcag-2.1
One-click install
npx skills add https://github.com/kiryteo/opencode-setup --skill accessibility-review-kiryteo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-review
Source: https://github.com/kiryteo/opencode-setup/tree/main/skills/accessibility-review
Command: npx skills add https://github.com/kiryteo/opencode-setup --skill accessibility-review-kiryteo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit designs and code for WCAG 2.1 AA compliance, flagging issues that block accessibility.

Core Features & Use Cases

  • Guided WCAG checks: Verifies contrast, semantic structure, keyboard accessibility, and screen-reader compatibility.
  • Real-world Scenarios: Suitable for product designs, web interfaces, and app UIs during design reviews or development QA.
  • Example: Given a form with unlabeled inputs, highlight missing labels and propose accessible alternatives.

Quick Start

Audit your current UI to identify WCAG 2.1 AA compliance 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 compliance?▼

To audit UI designs for WCAG 2.1 AA compliance, submit your web or app interface components for review. The audit identifies accessibility gaps by checking contrast, keyboard navigation, semantic structure, and screen-reader compatibility.

What is WCAG 2.1 AA compliance for web and app interfaces?▼

WCAG 2.1 AA compliance for web and app interfaces means meeting accessibility criteria like sufficient color contrast, logical semantic structure, full keyboard navigation, and screen-reader compatibility so users with disabilities can access content.

Can I check keyboard navigation and screen-reader compatibility during a QA review?▼

Yes, you can check keyboard navigation and screen-reader compatibility during a QA review. The audit evaluates interactive controls and UI layouts to ensure they are fully accessible via keyboard and readable by assistive technologies.

How do I fix unlabeled form inputs to meet accessibility standards?▼

To fix unlabeled form inputs for accessibility standards, the audit highlights missing labels and proposes accessible alternatives. This ensures forms meet WCAG 2.1 AA criteria for screen-reader compatibility and semantic structure.

Does this accessibility review work for both design and development phases?▼

Yes, this accessibility review works for both design and development phases. It is suitable for product designs, web interfaces, and app UIs during early design reviews or development QA to flag and resolve accessibility blockers.

What are the limitations of automated WCAG 2.1 contrast checks?▼

Automated WCAG 2.1 contrast checks identify visual accessibility gaps in UI components but require human context to fully validate semantic structure and interactive control behaviors during complex web and app interface reviews.

Related Skills

Explore More Design & Creative Skills→
dragoscirjandragoscirjan

lang-html

Enforce semantic HTML, WCAG 2.1 AA accessibility, and keyboard navigability.

Community
Basic
jhb-softwarejhb-software
38

astro-accessibility

Audits Astro components for WCAG 2.1 AA compliance gaps in accessibility.

Official
Intermediate
hdkz-devhdkz-dev

accessibility-ally

Audit web applications for semantic HTML, keyboard navigation, and color contrast issues.

Community
Intermediate
leboncoinleboncoin
92

check-accessibility

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

Official
Intermediate