Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
The fixing-accessibility skill is designed to help developers audit and correct HTML accessibility issues in web applications. It addresses common accessibility barriers by ensuring that interactive elements, forms, dialogs, and media comply with accessibility standards such as WCAG. By identifying missing ARIA labels, keyboard navigation gaps, focus management problems, color contrast deficiencies, and form-related errors, this skill helps teams create more inclusive digital experiences for users with disabilities. Its primary goal is to improve usability for all users, especially those relying on assistive technologies like screen readers or keyboard navigation.
You can apply the skill to a file by using the command `/fixing-accessibility <file>`. The skill will review the file for accessibility violations, explain why each issue matters, and suggest concrete code-level fixes.
No, the skill is designed for targeted, minimal fixes. It focuses on correcting accessibility issues without refactoring unrelated code or changing the overall UI structure.
It covers accessible names, keyboard access, focus management, dialogs, semantics, forms and errors, announcements, contrast and visual states, media, and tool boundaries, prioritized by their impact on usability.
The skill works with standard HTML and common front-end frameworks, but it does not require migration between libraries and should not add ARIA when native semantics are sufficient.
Front-end developers, UI/UX designers, and QA engineers who are responsible for ensuring web accessibility and WCAG compliance will benefit most from this skill.
Quick Setup:
.claude/skills/Repository
ibelick/ui-skills