Define OrgCard data model and interface contract
epic-organization-selection-ui-task-001 — Define the OrgCard widget's public interface: the Organization data class (id, displayName, logoUrl, isSelected), the onTap callback signature, and the widget's constructor contract. Establish the Dart model that both OrgCard and OrgSelectionScreen will use.
Acceptance Criteria
Technical Requirements
Implementation Notes
Check whether the project already uses the equatable package for value equality. If equatable is present, extend Equatable and override props with [id]. If not, manually implement == and hashCode on id alone. Do not add logoUrl to equality — two records representing the same org with different logo CDN URLs should still be equal.
The logoUrl field should be String? (nullable) so OrgCard can show an initials fallback without null-check ceremony. Consider adding a static factory Organization.fromJson(Map
Testing Requirements
Write a small unit test file (test/features/org_selection/models/organization_test.dart) with three tests: (1) equality holds when ids match regardless of other fields, (2) copyWith correctly overrides isSelected while preserving all other fields, (3) two Organization instances with different ids are not equal. These tests guard the contract relied upon by later OrgCard and OrgSelectionScreen tasks.
Flutter's Semantics system requires explicit configuration for custom card widgets — the default widget tree semantics may merge child nodes incorrectly, causing VoiceOver to announce partial or garbled text for each OrgCard. This is a critical failure for Blindeforbundet and violates the contractual WCAG 2.2 AA requirement.
Mitigation & Contingency
Mitigation: Wrap each OrgCard in a Semantics widget with an explicit label combining organization name and role label, set button role, and excludeSemantics: true on all child widgets to prevent double-announcement. Test on a physical iOS device with VoiceOver enabled before marking the epic complete.
Contingency: If automated semantics are insufficient, implement a dedicated AccessibilityLabel builder in the OrgCard that constructs the announcement string from OrgLabelsProvider output and passes it directly to the Semantics label field.
Organization logos must load before the screen is considered ready. If assets are fetched from a remote URL and network latency is high (a realistic scenario for rural NHF users), the screen may render with broken image placeholders, degrading the first-impression quality and potentially confusing screen reader users whose VoiceOver announcements would reference an empty image.
Mitigation & Contingency
Mitigation: Cache organization logos locally after first load using the org-branding-cache pattern. For the initial load, render a styled placeholder with the organization's initials and primary color while the logo loads asynchronously. Ensure the Semantics label is derived from the organization name, not the image asset, so screen reader announcements are never dependent on image load state.
Contingency: If caching implementation is out of scope for this epic, ship with initials-based placeholders as permanent fallbacks and defer logo loading to the org-branding-cache epic. The screen remains fully functional and accessible without logos.
The user story specifies that single-organization users bypass the selection screen and are routed directly into the app. If the bypass logic is implemented in the UI layer rather than in OrgSelectionService, it creates a tight coupling that breaks if the routing logic is ever reused or tested in isolation. It also creates a potential timing issue where the screen briefly renders before the bypass fires.
Mitigation & Contingency
Mitigation: Implement the single-org bypass entirely in OrgSelectionService.getPersistedSelection() or as a route guard — the screen should never be pushed onto the navigation stack for single-org users. The OrgSelectionScreen widget itself has no knowledge of this bypass.
Contingency: If the route guard approach is deferred to the routing epic, add a local guard in the OrgSelectionScreen's initState that calls OrgSelectionService, auto-selects if count is 1, and navigates forward before the first frame is painted, using a loading indicator to prevent the flash.