accessibility-mode

Audit UI components and code for WCAG 2.1 AA compliance.

3|1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/HouseGarofalo/claude-code-base --skill accessibility-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-mode
Source: https://github.com/HouseGarofalo/claude-code-base/tree/main/.claude/skills/accessibility-mode
Command: npx skills add https://github.com/HouseGarofalo/claude-code-base --skill accessibility-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and designers create more inclusive digital products by auditing and fixing accessibility issues, ensuring compliance with WCAG guidelines.

Core Features & Use Cases

  • WCAG Compliance: Audits code against WCAG 2.1 AA principles (Perceivable, Operable, Understandable, Robust).
  • Code Review: Identifies common accessibility pitfalls in HTML, ARIA usage, keyboard navigation, and color contrast.
  • Fix Implementation: Provides code examples for correcting issues like missing alt text, inaccessible buttons, and poor focus management.
  • Use Case: When developing a new UI component, use this Skill to review its implementation for accessibility best practices before release.

Quick Start

Review the provided code snippet for accessibility issues according to WCAG 2.1 AA standards.

Frequently Asked Questions about accessibility-mode

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

FAQPage Schema
How do I audit my HTML code for WCAG 2.1 AA compliance?

To check web accessibility, review your code against WCAG 2.1 AA standards focusing on perceivability, operability, understandability, and robustness. This process identifies common pitfalls in semantic HTML, ARIA patterns, keyboard navigation, and color contrast.

What is the best way to fix missing alt text and inaccessible buttons?

The best way to fix missing alt text and inaccessible buttons is by implementing corrected code examples that ensure proper semantic HTML and accessible UI components. This approach provides solutions for correcting issues like missing alt text and inaccessible buttons.

How does ARIA usage affect keyboard navigation and web accessibility?

ARIA usage affects keyboard navigation and web accessibility by providing patterns that enhance operability for assistive technologies. Auditing your ARIA implementation ensures that interactive elements remain perceivable and operable via keyboard navigation for users relying on screen readers.

Can I use this approach to review UI components for inclusive design before release?

Yes, you can use this approach to review UI components for inclusive design before release. When developing a new UI component, audit its implementation against WCAG 2.1 AA principles to ensure it meets accessibility best practices prior to deployment.

Why does poor focus management cause web accessibility issues?

Poor focus management causes web accessibility issues because it prevents keyboard-only users from navigating operable UI components effectively. Auditing focus management ensures that interactive elements receive proper focus states, maintaining perceivability and operability across digital products.