Accessibility test pass on a feature

Before shipping any interface, not after someone files a complaint.

Run an accessibility review of the interface below.

Check, and for each state pass, fail or cannot tell from what I gave you:
1. Keyboard only: every action reachable, visible focus, logical order, no traps, escape closes what it opens.
2. Screen reader: meaningful names for controls, correct roles, headings in order, images with appropriate alternatives, decorative images hidden.
3. State changes announced: errors, loading, results appearing, dynamic content.
4. Colour: contrast ratios for text and interactive elements, and nothing conveyed by colour alone.
5. Forms: labels tied to inputs, errors identified in text and associated with the field, no reliance on placeholder as label.
6. Motion, zoom to 200 percent, and reduced-motion preferences.

Give the exact element for each failure and the fix. Then list what can only be verified by testing with a real screen reader.

Interface or markup:

Beyond unit tests. Manual QA, exploratory charters, accessibility, load, and contracts between services.