Add Accessibility Review For Capture, Viewer, And Contacts Flows

[TheSilkky]

Add Accessibility Review For Capture, Viewer, And Contacts Flows

Priority

High

Type

Accessibility review

Labels

backlog, frontend, accessibility, design, testing

Branch Scope

Created from docs/end-user-product-design at d2c32a3.

Background

The design document identifies future capture, no-account viewer, and trusted-contact flows as core product surfaces. Those flows include high-stress information, access decisions, map/location presentation, and advanced technical details, so accessibility needs to be part of the design and implementation criteria.

This issue should attach accessibility requirements to those flows before they stabilize.

Proposed Scope

• Review capture fallback designs, viewer/map designs, and trusted-contact designs for keyboard access, focus order, labels, contrast, status announcements, and error recovery.
• Define route-specific accessibility acceptance criteria for future implementation issues.
• Confirm disclosure controls and advanced technical panels are understandable to screen-reader users.
• Include no-map and map-failure fallback behavior in the viewer accessibility review.
• Add Playwright or manual test notes where automated coverage is not enough.

Acceptance Criteria

• Each target flow has accessibility acceptance criteria before implementation is considered complete.
• Keyboard-only users can reach primary actions and recover from errors.
• Screen-reader users receive meaningful status, loading, error, empty, and stale-state copy.
• Color is not the only indicator of freshness, risk, key state, or upload state.
• Advanced technical panels do not trap focus or obscure critical warnings.

Out Of Scope

• Cosmetic-only review.
• Bypassing keyboard flows.
• Adding a new accessibility dependency without explicit implementation scope.
• Browser capture implementation.
• Backend changes.

Suggested Validation

• Manual keyboard pass for affected routes
• Screen-reader label review
• npm run typecheck
• npm run lint
• npm run test
• npm run build
• npm run test:e2e
• git diff --check