Sensitive Field Readout Warning

Blind and low-vision users rely on screen readers in public spaces - buses, waiting rooms, cafés - where audible readout of contact addresses, health information, or assignment details would constitute a privacy breach by the app itself. NHF specifically flagged this risk during the workshop. Without an explicit pre-readout warning, the product would force visually impaired peer mentors to choose between using the app accessibly and protecting their contacts' personal data - an unacceptable trade-off that undermines both accessibility and GDPR posture. The feature is a small surface but a critical trust signal, especially for Blindeforbundet's user base, and supports the platform's broader commitment to dignity-preserving design.

Implementation introduces a SensitiveFieldWrapper Flutter widget that intercepts the Semantics node and prepends a Readout Warning Service announcement when the screen reader focuses or activates the field. Sensitivity is declared per-field via a metadata flag, allowing forms (Contact Edit, Assignment Detail, Caregiver Form, Home Visit Report) to opt in without duplicating logic. The warning text is sourced from the Organization Labels system so wording can be localized and tenant-customized. The service must coordinate with VoiceOver/TalkBack focus events and respect user preference to suppress repeated warnings within a session. Audit logging records when sensitive fields are revealed to support security review.