Tester companion
V2 acceptance guide
Use this page to understand what the internally tested draft is expected to prove.
Tester-only guide. This page is not part of the ordinary visitor journey. It describes what the internally tested acceptance build must demonstrate before owner review.
What this acceptance build must demonstrate
- Home starts with one dominant need/search action, followed by common tasks and secondary audience routes.
- A− / A+ visibly changes the whole-interface text scale and remains usable at enlarged text and 200% zoom.
- Natural-language Home requests such as “ride to doctor,” “meal delivery,” “walker,” “help with my phone” and “I want to volunteer” do not dead-end.
- Transportation and companionship use guided request flows with review, honest quote/confirmation language and human fallback.
- Senior and Caregiver sample views share the same fictional state and respect permission boundaries.
- Volunteer and Organization actions lead somewhere useful rather than looking clickable without working.
- Learn & Enjoy remains finite, deliberate and accessible: no autoplay, favourites first where real, clear external handoffs.
- Booking keeps request versus confirmed status clear and confirmed calendar choices are verified separately.
- Phone and desktop layouts are checked at baseline text, A+ and 200% reflow without clipping or hidden controls.
- Commercial polish never overrides senior usability, accessibility, trust, recovery or dignity.
Owner review rule
Richard receives the preview link only after internal functional and visual verification both pass and known fixable issues are corrected.