fix-web-accessibilitylisted

# Fix Web Accessibility Fix accessibility issues. ## how to use - `/fix-web-accessibility` Apply these constraints to any UI work in this conversation. - `/fix-web-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. ## standards and conformance target - target [WCAG 2.2 Level AA](https://www.w3.org/TR/WCAG22/#conformance-reqs) by default, while honoring explicit project conformance requirements; AA covers both Level A and Level AA success criteria - use the [WCAG 2.2 Quick Reference](https://www.w3.org/WAI/WCAG22/quickref/) to check applicable criteria and their exceptions; the rules below are a focused checklist, not a complete conformance audit - include relevant WCAG 2.2 additions: obscured focus (2.4.11), alternatives to dragging (2.5.7), pointer target size (2.5.8), consistent help placement (3.2.6), repeated data entry (3.3.7), and accessible authentication (3.3.8) - use [ARIA APG patterns](https://www.w3.org/WAI/ARIA/apg/patterns/) for widget semantics, keyboard interaction, states, and focus management; preserve native HTML behavior where it provides the needed interaction - APG is [informative implementation guidance](https://www.w3.org/WAI/ARIA/apg/about/introduction/), and its examples require integration and testing; following