Add proxy audit badge to activity history items
epic-contact-detail-and-edit-supporting-ui-task-003 — Conditionally render the proxy-audit-badge widget (component 111-proxy-audit-badge) on each ActivityHistoryList item where the proxy flag is true. Ensure the badge is semantically labelled for screen readers and meets 44x44pt touch target if interactive.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 2 - 518 tasks
Can start after Tier 1 completes
Implementation Notes
Before implementing, read the existing 111-proxy-audit-badge widget source to understand its public API — specifically whether it requires a label parameter or derives its own semantics internally. If the badge already has its own Semantics wrapper with a hardcoded label, do not add a duplicate outer wrapper (this causes duplicate announcements on screen readers). If the badge is interactive, confirm with the design team whether tapping it should show a tooltip ('This activity was recorded by a coordinator on behalf of a peer mentor') — this is valuable for WCAG 2.2 understanding criterion. Keep the integration minimal: one `if (item.proxyFlag) const ProxyAuditBadge()` statement inside the existing _ActivityHistoryTile row.
Do not restructure the tile layout for this change.
Testing Requirements
Two widget tests: (1) pump _ActivityHistoryTile with proxyFlag=true — assert that the proxy-audit-badge widget is found in the widget tree using `find.byType(ProxyAuditBadge)`; (2) pump with proxyFlag=false — assert the badge is NOT found. Additionally, add a Semantics test using `tester.getSemantics(find.byType(ProxyAuditBadge))` to verify the label is non-empty when the badge is present.
Run on both iOS and Android semantic trees if possible.
The encrypted-field-display confirmation dialog adds interaction steps that may frustrate coordinators who access sensitive fields frequently, leading to requests to bypass the flow or skip read-receipt logging, which would violate Blindeforbundet's compliance requirements.
Mitigation & Contingency
Mitigation: Design the confirmation dialog to be as minimal as possible (one clear sentence, single confirm action) and ensure it does not reappear for the same field within a single screen session. Validate the UX with Blindeforbundet coordinators during the TestFlight pilot before finalising.
Contingency: If coordinators raise strong objections, escalate to Blindeforbundet's data protection officer to determine whether a lighter confirmation pattern (e.g., biometric confirmation instead of dialog) satisfies their compliance obligation.
The activity-history-list infinite scroll requires paginated Supabase queries. Contacts with hundreds of activities (e.g., an HLF peer mentor with 380 annual registrations) could cause slow page loads or memory pressure on older devices if pagination boundaries are set too large.
Mitigation & Contingency
Mitigation: Use a page size of 20 records with cursor-based pagination. Implement list item recycling using Flutter's ListView.builder. Benchmark memory usage with 400+ item simulation on a low-end test device before TestFlight release.
Contingency: If performance degrades on older devices, reduce page size to 10 and add a time-window filter (last 30 days, last 6 months, all) so the default view loads a manageable record count for most coordinators.
The cognitive load rule engine (from the Cognitive Accessibility feature) mandates no more than 7 fields per screen section. If a contact model has more than 7 editable fields, the edit-contact-screen layout must be split into sections, adding complexity not accounted for in the initial scope.
Mitigation & Contingency
Mitigation: Audit the full contact field list from all four organisations before implementation. Group fields into logical sections (personal info, contact details, affiliation) so no single section exceeds 7 fields. Use the cognitive-load-rule-engine component if it is already delivered by the Cognitive Accessibility feature.
Contingency: If the rule-engine component is not yet available, implement a simple manual section layout with accordion-style expansion for less-frequently edited fields to stay within the 7-field guideline without blocking delivery.