🏠 Overview › 👥 User Roles ›📖 Persistent Back Button Navigation Without Swipe Ge...

Persistent Back Button Navigation Without Swipe Gestures

Peer mentors using the app include individuals with motor impairments, stroke survivors, and elderly users who may struggle with swipe gestures. Every screen that allows backward navigation must display a persistent, adequately sized back button in a consistent location. The back button must be labelled with semantic accessibility metadata so screen readers announce it correctly, and it must meet the 44×44pt minimum touch target size. Swipe-to-go-back should remain available as a supplementary option but must never be the only path backwards.

CRITICAL story-navigation-gesture-accessibility-coordinator-001 3 pts
3
Story Points
Critical
Priority
Navigation & Gesture Accessibility
Feature

User Story

As a Coordinator
I want to navigate backwards through the app using a clearly visible back button on every screen rather than relying on swipe gestures
So that I can use the app confidently even if I have limited fine motor control, use an assistive device, or am unfamiliar with gesture-based navigation patterns

Acceptance Criteria

  • Given I am on any secondary or detail screen, when the screen renders, then a back button is visible in the top-left header area with a minimum touch target of 44×44pt
  • Given I am using a screen reader (VoiceOver), when I navigate to the back button, then it is announced as 'Go back' or the equivalent localized label with role 'button'
  • Given I tap the back button, when the action completes, then I am returned to the immediately preceding screen with focus restored to the element I was interacting with
  • Given I am on the root screen of any tab, when the screen renders, then no back button is displayed and no navigation hint implies swiping is required
  • Given I use swipe-to-go-back as an alternative gesture, when the swipe is performed, then it produces the same result as tapping the back button without breaking screen reader focus

Business Value

Users with motor impairments or cognitive disabilities account for a significant portion of peer mentors across NHF, Blindeforbundet, and HLF. Gesture-only navigation excludes these users entirely, violating the WCAG 2.2 AA requirement for pointer cancellation and multiple input paths. Providing a persistent back button ensures every peer mentor can navigate the app independently, directly supporting the app's core mission of enabling volunteer activity logging without barriers.

Components

Navigation & Gesture Accessibility
Related Feature
Coordinator
User Role