# Responsive and accessibility manual review

Automated axe, layout, focus, and target-size checks provide a blocking baseline; they do not prove
WCAG conformance or that the application is usable with every phone, keyboard, zoom setting, or
assistive technology. Run this protocol for a release candidate and record the actual equipment,
browser, assistive technology, result, and unresolved findings in that release's acceptance
evidence. Do not mark an unavailable check as passed.

Historical review results remain available in Git. The current repository-level limitation is
summarized in [current state](current-state.md#known-limitations); this file intentionally owns only
the reusable protocol.

## Review protocol

Use synthetic local/test accounts and Mocking Bird only. Do not enter real credentials or recovery
links in recordings or reports.

- On a physical phone near 360 CSS pixels wide, use touch and the virtual keyboard through login,
  recovery, and Settings. Confirm focused inputs and primary actions remain visible, the drawer and
  page can scroll fully, and no action is obscured.
- At 320 CSS pixels and 200% desktop browser zoom, inspect Home, login, recovery, Settings, the open
  drawer, notifications, and enabled-local Mocking Bird. Confirm content reflows without two-axis
  reading, clipping, or unreachable actions. At 768×1024, resize across the 900px drawer breakpoint
  and confirm temporary/permanent navigation transitions cleanly.
- Use only a hardware keyboard. Confirm the skip link, visible focus order, drawer trapping and
  Escape restoration, route-heading focus, invalid-field focus, snackbar dismissal, and every action
  needed for the representative journeys.
- Inspect light, dark, and system appearances, including Swedish long copy. Check text, controls,
  focus indicators, disabled states, validation, and notification contrast; axe is not a substitute
  for this visual review.
- With VoiceOver or NVDA, navigate by landmarks and headings; operate login, recovery, Settings,
  drawer, and notifications. Confirm labels, current-page state, validation relationships, status
  and alert announcements, and focus changes are understandable.
- Enable reduced motion and repeat navigation and drawer operations. Confirm functionality does not
  depend on animation.