App Settings & Preferences

A well-structured settings screen is foundational to accessibility compliance and user autonomy. Users relying on assistive technologies such as screen readers or large text must be able to configure their preferences within the app rather than relying solely on OS-level settings. For organizations serving users with diverse cognitive and sensory profiles, in-app configuration reduces friction and support burden. The settings screen also provides the entry point for account management, logout, and organization switching, making it a critical safety valve for multi-organization users and coordinators managing multiple associations.

Implemented as a Flutter screen with a scrollable list of settings menu card widgets, each navigating to a sub-screen or triggering an action. Settings persistence uses a lightweight local key-value store (e.g., shared_preferences) for UI preferences, with server-synced settings (notification preferences, language) persisted via REST API to the PostgreSQL backend. The settings repository abstracts both storage backends behind a clean interface. WCAG 2.2 AA requires that all interactive menu cards have descriptive semantic labels, logical reading order, and keyboard/switch-access navigation support. The hamburger menu trigger must meet minimum touch target size requirements.