Consistent Vertical Scrolling Layout Without Horizontal Swiping
The workshop documentation explicitly states: 'back button preferred over sideways swipe, vertical scroll is the norm'. This is a layout and interaction design constraint that must be enforced at the design token level for interaction patterns and implemented via the vertical-scroll-container component. All multi-step flows (activity wizard, proxy registration, expense forms) must use vertical scroll within a single screen or explicit forward/back navigation buttons rather than horizontal page swiping. Navigation between sections must be accessible via the labelled-navigation-bar and tab-state-manager using explicit tap targets, not swipe gestures. The navigation-accessibility-service must ensure focus management supports keyboard/switch access navigation.
User Story
Acceptance Criteria
- Given a peer mentor navigates the activity registration wizard, when moving between steps (date, duration, notes), then navigation occurs via clearly labeled Next/Back buttons — not by swiping horizontally
- Given a peer mentor is on any screen with a back option, when they want to return to the previous screen, then a visible back button is present in the header — not relying solely on swipe-back gesture
- Given a peer mentor scrolls through a long form or list, when reading content, then the scroll direction is vertical and no horizontal scrolling is required to see complete content at standard viewport width
- Given a peer mentor uses a switch access device or keyboard navigation, when navigating between screens and form fields, then all navigation is achievable without swipe gestures using only tap/click/focus actions
- Given a peer mentor uses the bottom navigation bar, when switching between the five main tabs (Home, Contacts, Add, Work, Notifications), then each tab is accessible via an explicit tap target on the labelled-navigation-bar
Business Value
The requirement to prefer vertical scroll and back buttons over swipe gestures was a named, explicit accessibility requirement from workshop participants — directly tied to the motor impairment and cognitive accessibility needs of NHF's stroke survivor population and Blindeforbundet's blind users who navigate via VoiceOver (which uses tap-based navigation, not swipe-to-go-back). This interaction pattern also benefits HLF's older hearing-impaired users. Implementing it as a layout system constraint ensures uniform application across all 30+ screens.