accessibility

Audit web interfaces for WCAG 2.1 AA accessibility gaps and remediation.

8|2|Updated Feb 9, 2026

Search Tags:#accessibility #a11y #screen reader #audit #wcag #aria

Ready to run

npx skills add https://github.com/mikeparcewski/wicked-garden --skill accessibility-mikeparcewski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/mikeparcewski/wicked-garden/tree/main/skills/product/accessibility
Command: npx skills add https://github.com/mikeparcewski/wicked-garden --skill accessibility-mikeparcewski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits code for WCAG 2.1 AA compliance, surfacing accessibility gaps and providing actionable remediation guidance to improve inclusive design.

Core Features & Use Cases

Automated and manual checks for keyboard navigation, ARIA patterns, color contrast, and semantic HTML across web interfaces.
Guided remediation with code-level fixes, practical examples, and checklists to align with WCAG 2.1 AA.
Use cases include design reviews, development sprints, and product audits to ensure accessibility requirements are met.

Quick Start

Audit a UI page for WCAG 2.1 AA conformance and apply the recommended fixes.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I audit my web interface for WCAG 2.1 AA compliance?▼

Audit web interfaces for WCAG 2.1 AA compliance by checking keyboard navigation, ARIA patterns, color contrast, and semantic HTML. The skill surfaces accessibility gaps and provides actionable remediation examples and structured checklists to fix them.

What are the most common ARIA and semantic HTML accessibility gaps in web development?▼

Common accessibility gaps involve missing keyboard navigation, incorrect ARIA patterns, poor color contrast, and non-semantic HTML. These issues prevent screen readers and assistive technologies from properly interpreting and navigating web interfaces.

How do I fix color contrast and keyboard navigation issues to meet WCAG 2.1 AA requirements?▼

Fix color contrast and keyboard navigation issues by applying guided remediation examples that align with WCAG 2.1 AA requirements. Use provided code-level fixes and structured checklists during design reviews and development sprints to ensure full compliance.

Can I use an accessibility audit during design reviews and development sprints?▼

Yes, you can use accessibility audits during design reviews, development sprints, and product audits. The process applies across web interfaces and provides practical guidance and structured checklists to ensure accessibility requirements are met throughout the development lifecycle.

What is the best way to remediate screen reader compatibility issues in a codebase?▼

The best way to remediate screen reader compatibility issues is to audit ARIA patterns and semantic HTML in your codebase, then apply actionable code-level fixes and practical examples to meet WCAG 2.1 AA accessibility requirements.