See a Clear Message When Biometrics Are Unavailable on My Device
Not all users will have devices with biometric hardware, and some users may have biometric enrollment disabled at the OS level. Older users and users with motor or sensory impairments (a key demographic for NHF and Blindeforbundet) may use older devices or may have accessibility settings that interfere with biometric unlock. The app must gracefully detect unavailability, display a plain-language explanation, and offer a seamless fallback to password or BankID authentication. The unavailability banner must meet WCAG 2.2 AA contrast and screen reader requirements.
User Story
Acceptance Criteria
- Given my device has no biometric hardware, When biometric setup is attempted, Then a banner explains that biometric login is not available on this device and I am directed to use password login
- Given my device has biometrics disabled at the OS level, When I attempt biometric login, Then a clear message tells me to enable biometrics in device settings or use password login instead
- Given biometric authentication fails due to too many failed attempts and the sensor locks, When I open the app, Then I am immediately shown the fallback login screen with a plain-language explanation
- Given the unavailability banner is shown, When a screen reader is active, Then the banner text is fully announced with appropriate semantics and focus is placed on the banner
- Given the unavailability banner is shown, When I tap the fallback action button, Then I am taken to the standard password login screen without additional friction
- Given biometric unavailability is detected, When I view the banner, Then it uses the design token color system with sufficient contrast ratio (minimum 4.5:1) for all text
Business Value
The three partner organizations collectively serve users with visual impairments, hearing loss, motor disabilities, and cognitive challenges. Many will use older devices. A confusing or alarming biometric failure state creates support burden and discourages app adoption. Plain-language, accessible fallback handling is explicitly required by the universal design mandate shared by all four organizations and is a prerequisite for WCAG 2.2 AA compliance.
Components
- Biometric Unavailable Banner ui
- Local Auth Integration infrastructure
- Biometric Authentication Service service
- Biometric Authentication Service service
- Login Screen ui
- Live Region Announcer ui
- Semantics Wrapper Widget ui
- Plain Language Error Display ui
- Contrast-Safe Color Palette Widget ui
- Biometric Authentication Service service