Add org label override and accessibility semantics
epic-contact-detail-and-edit-foundation-task-012 — Extend assignment-status-indicator to consume org-labels-provider for terminology overrides (e.g. HLF may call 'open' something else). Add Semantics widget with descriptive label combining status name and org override so screen readers announce the full meaning. Add widget tests for all three status states and override path.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 3 - 413 tasks
Can start after Tier 2 completes
Implementation Notes
Convert AssignmentStatusIndicator from StatelessWidget to ConsumerWidget to access the org-labels-provider via ref.watch(). The precedence chain should be: (1) explicit orgLabel parameter → (2) org-labels-provider value → (3) hardcoded English default. Implement this as a simple null-coalescing chain. The Semantics widget should have excludeSemantics: false so inner Text widgets don't double-announce.
Set the Semantics.label to the resolved display name + ' status' suffix — this gives screen reader users context that the element represents a status, not just a label. If org-labels-provider is not yet implemented, define a minimal OrgLabelsProvider stub that returns defaults — the interface must be agreed to allow this task to proceed without blocking on provider implementation.
Testing Requirements
Widget tests: (1) pump the widget inside a ProviderScope with a mock OrgLabels map that overrides 'open' to 'Aktiv sak' — verify badge text shows 'Aktiv sak', (2) verify Semantics label is 'Aktiv sak status' when override is active, (3) verify explicit orgLabel='Custom' overrides both provider and default, (4) repeat for pending and completed statuses, (5) verify that without a ProviderScope override, default English labels are shown. Use ProviderContainer and overrides from Riverpod testing utilities. Verify Semantics tree with tester.getSemantics() and check label property.
Blindeforbundet's encryption key retrieval mechanism may not be finalised at implementation time, or session key availability via Supabase RLS may be inconsistent, causing decryption failures that expose masked placeholders to users and degrade the experience.
Mitigation & Contingency
Mitigation: Agree with Blindeforbundet on key storage and retrieval contract before implementation starts. Prototype key retrieval in a spike against the staging Supabase instance and validate the full decrypt/verify cycle with real test data before committing to the implementation.
Contingency: Implement a fallback that shows a 'field temporarily unavailable' state with a retry affordance. Log decryption failures server-side for audit. Escalate to Blindeforbundet stakeholders to unblock key management before the service tier epic begins.
NHF contacts may belong to up to 5 chapters, each governed by separate RLS policies. A coordinator's chapter scope may not cover all affiliations, causing partial profile reads or silent data omissions that are difficult to detect in tests.
Mitigation & Contingency
Mitigation: Map all RLS policy combinations for multi-chapter contacts early. Write integration tests that create contacts with 5 affiliations and query them from coordinators with varying chapter scopes. Use Supabase's RLS test utilities to verify row visibility per role.
Contingency: Add an explicit 'affiliation partially visible' state in the repository response model so the UI can communicate scope limitations to the coordinator rather than silently showing incomplete data.
Organisation-specific validation rules (e.g., NHF chapter limit, Blindeforbundet encrypted field edit flow) may expand in scope during implementation as edge cases are discovered, causing the validator to grow beyond the planned complexity.
Mitigation & Contingency
Mitigation: Define the complete validation rule set with product and org stakeholders before coding begins. Document each rule with its source organisation and acceptance test. Use a rule registry pattern so new rules can be added without modifying core validator logic.
Contingency: Timebox validator enhancements to 2 hours per additional rule. Defer non-blocking rules to a follow-on maintenance task rather than blocking the epic delivery.