Personnummer Widget — privacy policy link and GDPR disclosure
epic-bankid-vipps-login-ui-task-010 — Add a privacy policy link and GDPR data-sharing disclosure to the Personnummer Confirmation Widget. The disclosure must clearly state which data is shared, with whom (the partner organization), and for what purpose. The privacy policy must open in an in-app browser. The acknowledgment action must be disabled until the user has either scrolled to the bottom of the disclosure text or explicitly tapped a 'Read disclosure' toggle.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
Add a ScrollController to the disclosure SingleChildScrollView. In the controller's listener, when offset >= maxScrollExtent - 10, set a ValueNotifier
Pull the org's privacyPolicyUrl from the BLoC state (it should be part of OrganizationProfile already loaded during org selection). For the in-app browser prefer url_launcher with LaunchMode.inAppWebView as it requires no additional package if url_launcher is already a dependency; fall back to webview_flutter only if custom navigation blocking is required. Disclosure copy should live in the ARB/l10n files with placeholders for orgName and dataController so legal can update without code changes.
Testing Requirements
Widget tests: verify acknowledgment button is disabled on render when text overflows; verify it becomes enabled after simulated scroll-to-bottom (manually invoke ScrollController.jumpTo(maxScrollExtent)); verify it becomes enabled after tapping the 'Read disclosure' toggle. Verify the privacy policy link calls the launch function with the correct org URL. Unit test the scroll-threshold detection logic as an isolated function. Mock the OrganizationProfileRepository to return a test org with a known privacyPolicyUrl.
Verify the org name appears correctly in the disclosure text. No e2e test required beyond task-012 coverage.
BankID on mobile uses a WebView or external app redirect that has known compatibility issues with Flutter's WebView package on certain Android versions. BankID's JavaScript-heavy broker pages may also trigger CSP or mixed-content errors in a Flutter WebView, preventing the authentication flow from completing.
Mitigation & Contingency
Mitigation: Use the flutter_inappwebview package (more mature than webview_flutter for complex OAuth pages) and validate BankID WebView rendering on the broker's test environment before integrating with the service layer. Prefer external browser redirect where the broker supports it.
Contingency: If WebView approach fails for certain BankID brokers, implement the full external browser redirect + deep link callback pattern as the primary flow and treat WebView as a fallback only.
The OAuth redirect flows (both Vipps and BankID) temporarily move the user outside the Flutter app into an external browser or the Vipps/BankID app. Screen reader users may lose focus context during this transition and become disoriented when the app callback returns them to the loading state, failing the WCAG 2.2 AA mandate.
Mitigation & Contingency
Mitigation: Implement explicit accessibility announcements (live region announcements) at each transition point: when launching the external flow ('Opening Vipps'), during the loading wait state ('Waiting for Vipps confirmation'), and on return ('Login successful' or 'Login failed — please try again'). Test with VoiceOver on iOS and TalkBack on Android during development.
Contingency: If OAuth transition accessibility is unresolvable on a specific platform, add an explicit accessibility user guide in the onboarding flow explaining the external app redirect behavior to set user expectations.
Biometric UI varies significantly across devices — Face ID (iPhone), fingerprint sensor (most Android), front-facing camera biometrics (some Android), and devices with no biometrics at all. Flutter's local_auth handles the OS dialog but the surrounding UI must gracefully handle all these cases, and testing coverage for all permutations is difficult.
Mitigation & Contingency
Mitigation: Use local_auth's getAvailableBiometrics() to detect the exact biometric type and render appropriate iconography (Face ID icon vs. fingerprint icon). For devices with no biometrics, skip the biometric screen entirely and route directly to full re-authentication.
Contingency: If a specific device configuration produces unexpected local_auth behavior in production, implement a user-accessible toggle in Settings to disable biometric login entirely, routing those users to the standard BankID/Vipps flow without biometrics.