fixing-accessibility

fixing-accessibility

When to Use

Use this skill when you need 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.

Fix accessibility issues.

how to use

• /fixing-accessibility

Apply 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

Reference these guidelines when:

• adding or changing buttons, links, inputs, menus, dialogs, tabs, dropdowns
• building forms, validation, error states, helper text
• implementing keyboard shortcuts or custom interactions
• working on focus states, focus trapping, or modal behavior
• rendering icon-only controls
• adding hover-only interactions or hidden content

rule categories by priority

priority	category	impact
1	accessible names	critical
2	keyboard access	critical
3	focus and dialogs	critical
4	semantics	high
5	forms and errors	high
6	announcements	medium-high
7