App Settings & Preferences

Giving users control over their experience is a prerequisite for accessibility compliance and long-term retention. For organizations serving users with diverse sensory and cognitive needs - particularly NHF (cognitive accessibility) and Blindeforbundet (screen reader users) - the ability to adjust text size, contrast, and readout behaviour is not a convenience but a functional requirement. Centralizing these controls reduces support burden on coordinators and org admins, who otherwise field individual requests. Cross-device preference sync ensures a consistent experience when a user moves between devices, which is important for coordinators who may switch between a personal phone and a work device. Offering biometric toggle from settings also reinforces the security posture communicated to prospective customers via the sales website.

Build the Settings Screen as a Flutter widget using Riverpod state management; the Preferences Service handles reads and writes via the REST API and caches the latest preference snapshot in Drift. Accessibility overrides (text scale, high contrast) should hook into Flutter's MediaQuery/ThemeExtension pipeline so they propagate app-wide without per-screen handling. The biometric toggle calls into the existing Secure Token Store from the authentication area. Language selection must enumerate only languages with complete localization bundles to avoid partial UI strings. Settings screen must itself be fully WCAG 2.2 AA compliant - all controls require semantic labels, focus indicators, and minimum touch targets. Use a declarative list-item widget pattern (title, subtitle, trailing control) that is easy to extend as new preferences are added without modifying layout logic.