Eve library

V1-AWEB-101 — Laptop / Desktop / Keyboard Validation Spec

Spec

Revision 1

On this page

Validation plan for the Phase 17.10 redesigned admin web at laptop and large desktop widths with keyboard-only operation as a first-class path.

Scope#

Validates the redesigns shipped in V1-AWEB-093 → V1-AWEB-100 against three viewport contexts and one input modality:

  • Laptop — 1280×800 (the floor for the master-detail split).
  • Large desktop — 2560×1440 (the ceiling, where the split shell + action rail + drawer must remain readable without growing into empty whitespace).
  • Standard desktop — 1920×1080 (the primary operator resolution).
  • Keyboard-only — the operator never reaches for the mouse.

Validation matrix#

For each surface listed below, the validator runs the keyboard- only flow at all three widths and records:

  • whether the operator can complete the flow;
  • whether all surfaces remain visible without horizontal scroll;
  • whether focus rings are visible at every step;
  • whether the action rail (V1-AWEB-094) stays sticky and reachable;
  • whether the master-detail split degrades gracefully at the laptop floor.

Surfaces:

  1. /inbox (UnifiedInboxPanel) — open row, take action, advance.
  2. /review + /review/[reviewId] — pick row, open detail, approve next, escalate, delegate.
  3. /research-integrity — comparative-text verdict; provenance cleared; unsupported-claim override (with evidence-id keyboard checkbox toggle).
  4. /privacy — uphold consent; queue audit-export.
  5. /rights — verified voice consent; pending_re_clearance avatar; queue rights report.
  6. /support — annotate conversation thread; diagnose continuity incident.
  7. /incidents — mitigate; mark postmortem complete.
  8. /personas — review tone calibration; approve premium cast.
  9. /policy — review attestation campaign; deploy bundle (typed confirmation modal).
  10. /trust-safety — open moderation row; flag offender; appeal.

Keyboard-only flow checklist#

For every flow:

  1. Operator opens the workspace via the sidebar (Cmd-K, then category, then workspace).
  2. Operator picks the row via j/k.
  3. Operator opens the row via Enter.
  4. Operator takes the primary action via the action rail (focus arrives via Tab; action invoked via Tab + Enter, never auto-focused on destructive).
  5. Operator advances to the next row via the V1-AWEB-100 "Approve next ⏎" shortcut.
  6. Operator returns to the queue without losing filter state.

Exit criteria#

  • 10/10 surfaces complete keyboard-only at 1280×800.
  • 10/10 complete at 1920×1080.
  • 10/10 complete at 2560×1440 with no rail-rail or detail-rail collision (the master-detail split + sticky action rail must fit without horizontal scroll on a 2560-wide viewport).
  • All focus rings visible at every step (validated via the V1-AWEB-095 + V1-AWEB-093 focus-ring spec).
  • Master-detail split degrades to single-column below 1280px with the action rail moving inline at the bottom (per the V1-AWEB-094 spec).
  • A signed-off Playwright spec (admin-laptop-desktop-keyboard.spec.ts) asserts the resolution-by-resolution flow for the 10 surfaces.

Out of scope#

  • Mobile / tablet viewports (deferred — admin app is desktop-first by product policy).
  • Mouse-only flow validation (deferred to V1-AWEB-103 signoff).
  • Screen-reader validation (deferred to a later accessibility ticket).

Deliverables#

  1. apps/oshun/admin/e2e/admin-laptop-desktop-keyboard.spec.ts — single Playwright spec that runs the 10 flows at each of the 3 viewport widths (30 specs total) using test.use({ viewport: { width, height } }).
  2. Validation report appended to this doc with a per-surface pass / fail row at the three widths (filled in during the validation run, not in this spec).