View and Understand Authentication Method Options with Accessible UI
The BankID and Vipps login screens must meet WCAG 2.2 AA accessibility requirements, which is explicitly required by all three partner organizations. This includes proper semantic labels for all interactive elements, sufficient color contrast ratios, adequate touch target sizes, support for dynamic type scaling, and compatibility with VoiceOver (iOS) and TalkBack (Android). The auth method selector must announce each option clearly and provide enough context for screen reader users to understand the choice they are making.
User Story
Acceptance Criteria
- Given I am using VoiceOver, When I navigate to the auth method selector screen, Then each button is announced with its label, role, and a brief description of what it does
- Given I am using dynamic text size set to large, When the auth screens render, Then all text scales appropriately without truncation or overlap
- Given I inspect the authentication screens, When I run a contrast ratio check, Then all text and interactive elements meet WCAG 2.2 AA minimum contrast ratios (4.5:1 for normal text, 3:1 for large text)
- Given I am navigating with keyboard or switch access, When I reach the auth screens, Then focus order is logical and all interactive elements are reachable without swiping
- Given I tap the BankID or Vipps button, When the loading state begins, Then a screen reader announcement confirms that authentication is in progress
- Given an authentication error occurs, When the error is shown, Then the error message is announced by the screen reader and includes actionable guidance
Business Value
Universal accessibility is a MUST HAVE requirement shared by all four partner organizations and was the second highest priority in all workshop sessions. Norges Blindeforbund's entire user base depends on screen reader compatibility. NHF explicitly mentioned stroke survivors and users with cognitive challenges. An inaccessible login screen creates an immediate barrier that prevents these users from accessing the app at all.
WCAG 2.2 AA compliance is also a legal requirement for public-sector adjacent organizations receiving government (Bufdir) funding.