fixing-accessibility

Identify and fix accessibility issues in UI components using defined rules.

Updated Jan 24, 2026

Search Tags:#ui #accessibility #a11y #validation #focus #semantics #aria

Ready to run

npx skills add https://github.com/seflless/dot-agents --skill fixing-accessibility-seflless

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps identify and fix accessibility issues in UI components, reducing barriers for users with disabilities.

Core Features & Use Cases

Provides guidance for accessible names, keyboard interaction, focus management, and semantic markup.
Covers contrast and state considerations, ARIA usage, and proper error descriptions to improve usability.
Use cases include audits of forms, dialogs, navigation, and interactive controls to ensure WCAG-aligned accessibility.

Quick Start

Audit the current UI and apply the most critical accessibility 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 accessibility issues in UI components like forms and navigation?▼

To fix accessibility issues in UI components, you must audit forms, navigation, and interactive controls for accessible names, keyboard interaction, and focus management. This ensures WCAG-aligned compliance and reduces barriers for users with disabilities.

What is the best way to manage focus visibility and keyboard navigation for accessibility?▼

The best way to manage focus visibility and keyboard navigation is by applying defined accessibility rules for focus management and semantic markup. Properly implementing these rules ensures interactive controls remain operable via keyboard inputs.

How do I use ARIA attributes correctly to improve UI accessibility?▼

Correct ARIA usage involves applying defined rules for accessible names and semantic markup across dialogs and interactive controls. This ensures screen readers accurately interpret UI state considerations and proper error descriptions.

Can I audit color contrast and state considerations for WCAG compliance?▼

Yes, you can audit color contrast and state considerations to ensure WCAG compliance. The process involves evaluating contrast ratios and state changes across UI components to improve overall usability for visually impaired users.

Why does my form fail accessibility validation due to improper error descriptions?▼

Form accessibility validation fails due to improper error descriptions when semantic markup and ARIA usage do not correctly associate error messages with inputs. Fixing this requires applying defined rules for accessible names and proper error descriptions.