Accessibility Expert

Audit web applications for WCAG 2.1 AA accessibility compliance.

Updated Jan 17, 2026

Search Tags:#accessibility #a11y #screen reader #keyboard navigation #wcag #aria

Ready to run

npx skills add https://github.com/CarGDev/codetyper.cli --skill accessibility-expert-cargdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Accessibility Expert
Source: https://github.com/CarGDev/codetyper.cli/tree/main/src/skills/accessibility
Command: npx skills add https://github.com/CarGDev/codetyper.cli --skill accessibility-expert-cargdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical need to make web applications usable by everyone, regardless of ability, by ensuring compliance with accessibility standards and best practices.

Core Features & Use Cases

WCAG 2.1 AA Compliance: Audits and guides implementation to meet perceivable, operable, understandable, and robust criteria.
Semantic HTML & ARIA: Provides guidance on correct usage of HTML elements and ARIA attributes to improve screen reader compatibility.
Keyboard Navigation: Ensures all interactive elements are keyboard accessible and focus management is handled correctly.
Use Case: A developer can use this Skill to review a complex form component and receive specific recommendations on ARIA roles, states, and keyboard interaction patterns to ensure it's fully accessible to screen reader users.

Quick Start

Use the accessibility skill to check the current page for WCAG 2.1 AA compliance issues.

Frequently Asked Questions about Accessibility Expert

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

FAQPage Schema

How do I make my web application meet WCAG 2.1 AA compliance?▼

To meet WCAG 2.1 AA compliance, your web application must follow perceivable, operable, understandable, and robust design principles. This involves auditing interactive elements and implementing semantic HTML, ARIA patterns, and keyboard navigation.

How do I add ARIA roles to a complex form component for screen reader compatibility?▼

Adding ARIA roles to a complex form component for screen reader compatibility requires reviewing the existing HTML structure and applying specific ARIA attributes, roles, and states. This ensures screen readers correctly interpret interactive elements.

What is the best way to ensure keyboard navigation works across all interactive elements?▼

The best way to ensure keyboard navigation works is by auditing your interactive elements and verifying that focus management is handled correctly. All functionality must be accessible without a mouse using proper semantic HTML.

Can I use this to audit a page for perceivable and operable accessibility issues?▼

Yes, you can use this to audit a current page for perceivable and operable accessibility issues. It evaluates your web application against WCAG 2.1 AA criteria to identify areas where semantic HTML or ARIA patterns need implementation.

Why does my dynamic web component need ARIA attributes and focus management?▼

Dynamic web components need ARIA attributes and focus management because standard HTML lacks the semantics to announce dynamic changes. Proper ARIA patterns and keyboard navigation ensure screen reader users understand state changes.

When do I need semantic HTML versus ARIA roles for web accessibility?▼

You need semantic HTML as the baseline for web accessibility, using ARIA roles only when native HTML elements cannot convey the necessary semantics. ARIA supplements semantic HTML to handle complex interactions for screen reader users.