accessibility-reviewlisted

# Accessibility Review Review an interface for barriers that prevent or degrade use by people with disabilities. Work from observable evidence and the declared scope. Do not claim WCAG conformance from a checklist alone, and do not treat visual taste or unverified assumptions as accessibility defects. ## Establish scope and safety Identify the changed components, routes, states, supported browsers and input modes, and any applicable product or regulatory requirements. Prefer local fixtures, test accounts, and redacted data. Do not submit forms, alter user data, or exercise privileged flows without authorization. Record unavailable environments and untested states as limitations. ## Inspect the implementation Start with the diff and the component's surrounding markup, styles, state transitions, and tests. Check: - semantic elements, heading order, landmarks, labels, names, descriptions, and form errors; - keyboard reachability, logical order, visible focus, escape behavior, and absence of keyboard traps; - focus placement after dialogs, navigation, validation, loading, and conditional content changes; - correct ARIA roles, states, properties, relationships, and native-control preference; - screen-reader announcements for status, errors, live updates, and dynamic content; - text and non-text contrast, resizing, reflow, reduced motion, touch targets, and zoom; - alternative text, captions, transcripts, meaningful link text, and non-color cues; - timing, autoplay, drag-only