Accessibility check for UI components against WCAG 2.2 AA

Many accessibility problems are visible in source code before anyone opens a screen reader: a clickable `div`, an icon button with no name, a modal that does not trap or restore focus, an input whose label is only a placeholder. This skill makes Claude Code review components for those problems against a concrete WCAG 2.2 AA checklist.

**What it checks** - Semantics: interactive elements use `button`, `a`, `input` and friends instead of click handlers on generic elements. - Names and labels: every control has an accessible name; images have meaningful or empty `alt`; form fields have associated labels; errors are linked to fields. - Keyboard: everything clickable is reachable and operable by keyboard; no positive `tabindex`; custom widgets handle the expected keys. - Focus: visible focus styles are not removed; dialogs move focus in, keep it inside, and return it on close. - ARIA: roles and attributes are valid and not redundant; `aria-hidden` is not put on focusable content. - Contrast: when colors are literal values or resolvable design tokens, computes the contrast ratio (4.5:1 for normal text, 3:1 for large text and UI parts). - Target size: interactive targets at least 24 by 24 CSS pixels unless an exception applies. - Motion and announcements: animations respect `prefers-reduced-motion`; async status changes use a live region.

**Output** Findings with the WCAG success criterion number, `file:line`, the user impact in one sentence, and the fix. With `fix` as an argument it applies the fixes.

**What it will not do** Static review cannot confirm real screen reader output or computed styles. It says so, and recommends automated checks such as axe in your end-to-end tests plus a manual keyboard pass. It does not claim a component is "compliant".