CRITICAL story-no-access-screen-restricted-roles-organization-admin-003 2 pts
2
Story Points
Critical
Priority
No-Access Screen for Restricted Roles
Feature

User Story

As a Organization Administrator
I want to have a clearly labelled back button or 'Go to Home' action on the no-access screen
So that I can return to an area I am permitted to use without needing to close and reopen the app

Acceptance Criteria

  • Given a peer mentor is on the no-access screen, when they tap the back button, then they are navigated to the previous accessible screen without app state loss
  • Given a peer mentor is on the no-access screen and there is no safe previous route, when they tap 'Go to Home', then they are navigated to the role-based home screen
  • Given the no-access screen is displayed, when the peer mentor inspects the UI, then a persistent back button is visible in the header rather than relying on swipe-to-dismiss gestures
  • Given a peer mentor returns to the home screen from the no-access screen, when the bottom navigation is evaluated, then other tab states are preserved and not reset
  • Given the no-access screen is displayed, when a screen-reader user navigates to the action buttons, then both the back action and home action are announced with descriptive labels

Business Value

Users who encounter a dead end with no obvious exit path are likely to abandon the app entirely. Providing a persistent, accessible navigation action from the no-access screen ensures continuity of the user journey, directly supporting the low-cognitive-load design principle emphasized by all three workshop organizations. This is especially important for users with motor or cognitive impairments who cannot rely on back gestures.