a11y

Audit UI components for WCAG 2.1/2.2 AA accessibility compliance.

7|Updated Jan 29, 2026

Search Tags:#accessibility #a11y #wcag #contrast #keyboard #semantic-html #aria

Ready to run

npx skills add https://github.com/joabgonzalez/ai-agents-skills --skill a11y-joabgonzalez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: a11y
Source: https://github.com/joabgonzalez/ai-agents-skills/tree/main/skills/a11y
Command: npx skills add https://github.com/joabgonzalez/ai-agents-skills --skill a11y-joabgonzalez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes accessibility guidelines and best practices to help teams build inclusive interfaces that meet WCAG and ARIA standards across technologies.

Core Features & Use Cases

Semantic HTML and ARIA guidance to ensure proper structure and accessibility
Keyboard navigation, focus management, color contrast, and screen-reader considerations
Use Case: Integrate into design reviews and code audits to validate accessibility across components

Quick Start

Audit a UI component and apply WCAG 2.1/2.2 AA checks to improve accessibility.

Frequently Asked Questions about a11y

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

FAQPage Schema

How do I check my UI components for WCAG compliance?▼

To check WCAG compliance, audit your UI components against WCAG 2.1/2.2 Level AA standards by validating semantic structure, ARIA usage, color contrast, keyboard navigation, and screen reader considerations across HTML, CSS, and frameworks.

What is the best way to apply ARIA and semantic HTML for accessibility?▼

The best way to apply ARIA and semantic HTML is to follow universal accessibility guidelines that ensure proper document structure and screen reader support, validating element roles and attributes against established WCAG standards.

How do I fix keyboard navigation and focus management issues in web apps?▼

Fix keyboard navigation and focus management issues by applying accessibility guidance to your UI components, ensuring logical tab order, visible focus states, and proper keyboard operability across your HTML and framework implementations.

Can I use this approach to validate color contrast across different frameworks?▼

Yes, you can validate color contrast across different frameworks by applying universal accessibility checks that measure visual presentation against WCAG 2.1/2.2 Level AA requirements to ensure inclusive interfaces.

Do I need specific libraries to audit screen reader compatibility?▼

No specific libraries are required to audit screen reader compatibility; you apply centralized accessibility guidelines and practical checks directly to your existing HTML, CSS, and framework components to ensure proper screen reader considerations.

Why does my semantic HTML structure still fail accessibility audits?▼

Semantic HTML may fail accessibility audits if it lacks proper ARIA usage, sufficient color contrast, or correct keyboard navigation implementation, requiring comprehensive WCAG 2.1/2.2 Level AA checks across the entire UI component.