fixing-accessibility
Audit and fix HTML accessibility issues across ARIA labels, keyboard navigation, focus management, and WCAG compliance.
- Covers nine rule categories prioritized by impact: accessible names, keyboard access, focus management, semantics, forms and errors, announcements, contrast, media, and tool boundaries
- Provides targeted fixes for common patterns like icon-only buttons, form error linking, and focus trapping in modals
- Includes quick reference for when to apply (interactive controls, forms, dialogs, custom interactions) and common code-level fixes with before/after examples
- Emphasizes minimal, surgical changes over large UI rewrites and prefers native HTML elements over ARIA workarounds
fixing-accessibility
Fix accessibility issues.
how to use
-
/fixing-accessibilityApply these constraints to any UI work in this conversation. -
/fixing-accessibility <file>Review the file against all rules below and report:- violations (quote the exact line or snippet)
- why it matters (one short sentence)
- a concrete fix (code-level suggestion)
Do not rewrite large parts of the UI. Prefer minimal, targeted fixes.
when to apply
More from ibelick/ui-skills
fixing-motion-performance
Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.
14.4Kbaseline-ui
Validates animation durations, enforces typography scale, checks component accessibility, and prevents layout anti-patterns in Tailwind CSS projects. Use when building UI components, reviewing CSS utilities, styling React views, or enforcing design consistency.
11.2Kfixing-metadata
>
10.3Kui-skills
Opinionated constraints for building better interfaces with agents.
22