skills.rest
gaiastudio-ai
gaiastudio-aiOFFICIAL
Explore all skills by this author →
GitHub

gaia-review-a11y

Identify WCAG 2.1 accessibility issues and generate a Markdown findings report.

2|Updated Apr 15, 2026
Search Tags:#automation#accessibility#a11y#wcag#code-review#report#ui-review
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-review-a11y
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gaia-review-a11y
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-review-a11y
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-review-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams assess WCAG 2.1 accessibility across code and UI components, surfacing failures and remediation guidance to improve inclusive design.

Core Features & Use Cases

  • Automated accessibility review across semantic HTML, ARIA attributes, keyboard navigation, color contrast, and screen reader support.
  • Generates a markdown findings report with WCAG criterion IDs, conformance levels (A/AA/AAA), severity, and remediation steps.
  • Use cases include validating new UI components, auditing pages for accessibility regressions, and producing artifact-ready reports for audits.

Quick Start

Provide the target code or component path and run the accessibility review to generate a findings report.

Frequently Asked Questions about gaia-review-a11y

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

FAQPage Schema
How do I check my codebase for WCAG 2.1 accessibility issues?▼

To check your codebase for WCAG 2.1 accessibility issues, provide your target code or component path to recursively scan semantic HTML, ARIA attributes, keyboard focus, and visual accessibility, generating a structured Markdown findings report.

What is included in an automated accessibility audit report?▼

An automated accessibility audit report includes per-finding citations to WCAG criterion IDs, conformance levels (A/AA/AAA), severity ratings, and specific remediation steps, formatted as a deterministic Markdown artifact for compliance tracking.

Can I scan specific UI components for accessibility regressions?▼

Yes, you can scan specific UI components for accessibility regressions by providing the individual file or component path, allowing targeted validation of semantic HTML and screen reader support without scanning the entire project.

Does automated code review detect ARIA attributes and keyboard navigation failures?▼

Automated code review detects ARIA attributes and keyboard navigation failures by recursively scanning target files to surface incorrect semantic HTML, focus management issues, and visual accessibility gaps against WCAG 2.1 criteria.

What's the best way to generate an accessibility findings report for audits?▼

The best way to generate an accessibility findings report for audits is running an automated review on your target codebase, which produces a structured Markdown artifact with WCAG criterion IDs, conformance levels, and actionable remediation guidance.

Related Skills

Explore More Software Engineering Skills→
allofmengallofmeng
12

figma-code-connect-components

Identify unmapped Figma components and fetch matching code components for Code Connect mappings.

Community
Advanced
timsvoicetimsvoice

specimin-ui-accessibility

Audit and fix generated UI code for WCAG 2.1 AA compliance.

Community
Advanced
clawpod-appclawpod-app
46

accessibility-review

Audit designs or pages for WCAG 2.1 AA compliance with remediation guidance.

Community
Intermediate
dachentdachent
18

frontend-design-codex

Validate frontend UI components through browser rendering and screenshot analysis.

Community
Advanced