fixing-accessibility

1# fixing-accessibility
2 
3Fix accessibility issues.
4 
5## how to use
6 
7- `/fixing-accessibility`
8  Apply these constraints to any UI work in this conversation.
9 
10- `/fixing-accessibility <file>`
11  Review the file against all rules below and report:
12  - violations (quote the exact line or snippet)
13  - why it matters (one short sentence)
14  - a concrete fix (code-level suggestion)
15 
16Do not rewrite large parts of the UI. Prefer minimal, targeted fixes.
17 
18## when to apply
19 
20Reference these guidelines when:
21- adding or changing buttons, links, inputs, menus, dialogs, tabs, dropdowns
22- building forms, validation, error states, helper text
23- implementing keyboard shortcuts or custom interactions
24- working on focus states, focus trapping, or modal behavior
25- rendering icon-only controls
26- adding hover-only interactions or hidden content
27 
28## rule categories by priority
29 
30| priority | category | impact |
31|----------|----------|--------|
32| 1 | accessible names | critical |
33| 2 | keyboard access | critical |
34| 3 | focus and dialogs | critical |
35| 4 | semantics | high |
36| 5 | forms and errors | high |
37| 6 | announcements | medium-high |
38| 7 | contrast and states | medium |
39| 8 | media and motion | low-medium |
40| 9 | tool boundaries | critical |
41 
42## quick reference
43 
44### 1. accessible names (critical)
45 
46- every interactive control must have an accessible name
47- icon-only buttons must have aria-label or aria-labelledby
48- every input, select, and textarea must be labeled
49…