Add Coordinator Attribution Banner to Activity Form
epic-proxy-activity-registration-ui-task-011 — Implement an inline attribution banner inside ProxyActivityForm that appears when the form is used in proxy context. The banner must display the coordinator's name and role, use a visually distinct but accessible background color from the design token palette, and be announced by screen readers as a status region.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 13 - 6 tasks
Can start after Tier 12 completes
Implementation Notes
Keep CoordinatorAttribution as a simple immutable Dart class — do not reuse auth models directly in UI layer to avoid tight coupling. The Semantics liveRegion: true property causes screen readers to announce the content when it appears; ensure it is only shown once (not toggled) to avoid repeated announcements. Choose a design token that communicates 'informational/neutral' status (avoid warning amber or error red as this is not an error state). In Norwegian context the label text should still be in English as per project output rules.
If the design token palette does not yet have an info surface color, add one to AppColors and use it — do not hardcode hex values.
Testing Requirements
Widget tests (flutter_test): verify banner is absent when CoordinatorAttribution is null, verify banner renders coordinator name and role when attribution provided, verify background color token is applied (by checking BoxDecoration or color property), verify Semantics liveRegion is true. Accessibility test: run flutter_test SemanticsController to confirm the widget is announced as a live region. Manual test: enable TalkBack/VoiceOver on device and confirm announcement on form focus.
The bulk registration screen combines pre-filled defaults, a dynamic multi-select participant list, per-participant conflict badges, and a batch submission confirmation — making it one of the most complex screens in the application. Scope creep or underestimated interaction complexity could cause the epic to exceed its estimate significantly.
Mitigation & Contingency
Mitigation: Implement the bulk screen in two vertical slices: (1) participant selection and form submission without conflict handling, (2) conflict badge rendering and override flow. Validate slice 1 with coordinators before building slice 2.
Contingency: If the full conflict review UI cannot be completed within the epic, ship the bulk screen with a simplified 'skip all duplicates' fallback mode and defer per-participant override toggles to a follow-up sprint.
The proxy-registration-bloc must manage state across two distinct flows (single proxy and bulk) with branching conflict paths, intermediate buffering of bulk participant selections, and reliable state reset. Incorrect state transitions could leave the UI in a loading or stale-conflict state after submission.
Mitigation & Contingency
Mitigation: Model the BLoC state as a sealed class hierarchy with exhaustive pattern matching in the UI. Write state-machine unit tests that exercise every valid transition and assert that invalid transitions are no-ops. Use flutter_bloc's BlocObserver in debug builds to log all transitions.
Contingency: If BLoC state bugs surface in QA, introduce an explicit ResetToIdle event triggered on screen disposal to guarantee clean state, and add a 'Start over' affordance visible to the coordinator at any conflict step.
The typeahead peer mentor selector with multi-select mode may be difficult to operate with VoiceOver/TalkBack, particularly the dynamic search results list and the selected-chip removal controls, risking WCAG 2.2 AA non-compliance for screen reader users.
Mitigation & Contingency
Mitigation: Wrap all search result items and selected chips with explicit Semantics widgets providing role, label, and selected-state announcements. Test the selector with VoiceOver on iOS and TalkBack on Android during development, not only at QA time.
Contingency: If the multi-select typeahead cannot be made fully accessible within the sprint, provide an alternative flat scrollable list with checkboxes as a fallback mode, toggled by an accessibility-settings flag.
The peer mentor selector must apply RLS chapter-scope filtering to show only mentors the coordinator is responsible for. If the Supabase query for the selector does not correctly join against the coordinator's chapter assignments, coordinators may see mentors from other chapters, violating data isolation.
Mitigation & Contingency
Mitigation: Implement the selector's data query using the same RLS-aware Supabase client used by the contact list feature, which already handles chapter-scope filtering. Write an integration test with a multi-chapter coordinator fixture asserting cross-chapter mentors are not returned.
Contingency: If a data isolation breach is discovered, immediately add a client-side chapter_id filter as a defence-in-depth measure and audit selector query logs for any unauthorised cross-chapter results.