fixing-accessibility

Fix accessibility issues in web UI components with WCAG-compliant code suggestions.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill fixing-accessibility-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/fixing-accessibility
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill fixing-accessibility-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix common and subtle accessibility regressions in user interfaces by auditing labels, ARIA attributes, keyboard behavior, focus management, contrast, and semantic structure so users with disabilities can reliably interact with the UI.

Core Features & Use Cases

  • Targeted audits: Identify missing accessible names, unlabeled inputs, icon-only buttons without aria-labels, and links with non-descriptive text.
  • Keyboard & focus fixes: Ensure tab order, focus visibility, focus trap behavior for modals, and Escape-to-close patterns.
  • WCAG alignment: Surface contrast issues, announcement patterns (aria-live, aria-busy), proper form error associations, and recommendations that avoid unnecessary library migrations.
  • Use Case: During a code review for a new modal or form, run the review to get exact failing snippets, one-line explanations, and minimal, copy-paste fixes that preserve existing UI code.

Quick Start

Run the fixing-accessibility review on a changed UI file to receive quoted violations, why each matters, and concise code-level fixes prioritizing native semantics and minimal change.

Frequently Asked Questions about fixing-accessibility

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

FAQPage Schema
How do I fix accessibility issues in web UI components like modals and forms?

Fix accessibility issues by auditing UI components for missing ARIA attributes, keyboard navigation gaps, and focus management errors to ensure WCAG compliance. The review outputs exact failing snippets, explanations, and minimal copy-paste code corrections.

How do I add accessible names and ARIA attributes to icon-only buttons?

Add accessible names to icon-only buttons by applying appropriate ARIA attributes like aria-label during a targeted accessibility audit. The review identifies non-descriptive link text and unlabeled inputs, suggesting minimal semantic HTML fixes.

What is the best way to implement focus trap behavior and keyboard navigation for dialogs?

Implement focus trap behavior for dialogs by auditing tab order, focus visibility, and Escape-to-close patterns. The accessibility review checks keyboard navigation logic and provides concise code-level fixes to manage focus correctly within modals.

Does this accessibility audit require migrating my existing UI libraries?

This accessibility audit does not require migrating existing UI libraries, as it prioritizes native semantics and minimal changes. Recommendations surface contrast issues, aria-live announcements, and form error associations using targeted fixes that preserve your current codebase.

When should I run an accessibility audit during the development workflow?

Run an accessibility audit during code reviews or feature changes when adding new web UI components like buttons, links, forms, dialogs, menus, and modals. This catches subtle regressions early by validating WCAG compliance before deployment.