HIGH story-navigation-shell-organization-administrator-006 3 pts
3
Story Points
High
Priority
Navigation Shell
Feature

User Story

As a user
I want all navigation elements in the bottom bar, app bar, and drawer to be fully operable and clearly announced by VoiceOver and JAWS screen readers
So that So that visually impaired users can independently navigate the full app without assistance

Acceptance Criteria

  • Given VoiceOver is enabled on iOS, when the user focuses on the bottom navigation bar, then each tab is announced as '[Tab name], tab, [selected/not selected]'
  • Given JAWS is active, when the user navigates to the hamburger menu button, then it is announced as 'Open navigation menu, button'
  • Given a screen reader is active, when the user activates a tab or drawer item, then the newly displayed screen title is announced immediately upon navigation
  • Given VoiceOver is enabled, when the user swipes through the bottom nav tabs, then all five tabs are reachable via swipe gesture and activation keys without requiring visual reference
  • Given the system has reduced-motion accessibility settings enabled, when the navigation shell performs a screen transition, then animations are suppressed or minimized to a simple crossfade
  • Given any navigation element in the shell, when rendered, then all touch targets are at least 44x44 logical pixels

Business Value

Screen reader compatibility is a MUST HAVE requirement identified by Blindeforbundet (VoiceOver/JAWS support) and relevant to all three organizations. Visually impaired peer mentors who cannot independently use the navigation shell are entirely excluded from the application. Accessible navigation is a legal obligation under WCAG 2.2 AA and directly affects the organizations' ability to comply with Bufdir grant requirements that mandate inclusive digital services.