fixing-accessibility

Fix accessibility issues in web UI components with ARIA and keyboard navigation.

Updated Feb 3, 2026

Search Tags:#accessibility #a11y #frontend #ux #aria #screen-readers #keyboard-access

Ready to run

npx skills add https://github.com/chiperman/agent-skills --skill fixing-accessibility-chiperman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/chiperman/agent-skills/tree/main/skills/fixing-accessibility
Command: npx skills add https://github.com/chiperman/agent-skills --skill fixing-accessibility-chiperman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers fix accessibility issues in user interfaces, reducing barriers for all users.

Core Features & Use Cases

Guided accessibility checks: Provides a prioritized checklist covering keyboard, ARIA, and semantic markup.
Actionable fixes: Suggests concrete, code-level improvements for common components like buttons, forms, dialogs, and navigation.
Use Case: When shipping a new interface, run this Skill to audit focus management, labeling, and keyboard navigation to ensure inclusivity.

Quick Start

Use the fixing-accessibility skill to review a UI component, identify issues, and apply targeted fixes.

Frequently Asked Questions about fixing-accessibility

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

FAQPage Schema

How do I fix UI accessibility issues in frontend components?▼

To fix UI accessibility issues, you need to audit focus management, keyboard navigation, and ARIA usage. This skill provides a prioritized checklist and suggests concrete, code-level improvements for buttons, forms, and dialogs to ensure inclusivity.

How do I manage focus and keyboard navigation in dynamic web dialogs?▼

Managing focus and keyboard navigation in dynamic web dialogs requires proper ARIA usage and semantic markup. This skill helps you audit these constraints, providing targeted fixes to ensure accessible names and correct focus management across your SPAs.

What's the best way to audit ARIA usage and semantic markup in web apps?▼

The best way to audit ARIA usage and semantic markup is running a guided accessibility checklist. This skill reviews your frontend components, identifies issues in labeling and semantics, and applies targeted fixes to reduce barriers for all users.

Can I use this to check accessible names and keyboard access for dashboards?▼

Yes, you can use this skill to check accessible names and keyboard access for dashboards. It applies to frontend components, forms, and navigation across web apps and SPAs, satisfying constraints for accessible names, semantics, and keyboard navigation.

Why does my screen reader skip interactive elements in my SPA navigation?▼

Screen readers skip interactive elements in SPA navigation when semantic markup and ARIA roles are missing or incorrect. This skill helps identify these specific issues and provides actionable, code-level fixes for navigation and dynamic interfaces.