Receive Spoken Warnings Before Sensitive Fields Are Read Aloud
Peer mentors frequently work in public settings — coffee shops, transit, community centres — and may have their screen reader reading aloud while others are present. Sensitive fields such as contact names, phone numbers, encrypted assignment details, and health-related notes must trigger a spoken privacy warning before their content is announced. The sensitive-field-privacy-guard must intercept screen reader focus events on designated fields and inject a live region announcement: 'Warning: sensitive information follows. Ensure you are in a private setting.' The sensitive-field-configuration must allow per-organisation administrators to define which fields are flagged as sensitive. A confirmation gesture must be required before the field content is read.
User Story
Acceptance Criteria
- Given a contact detail screen with a phone number field, when the screen reader moves focus to it, then a live region announces 'Sensitive information: confirm to read' before the number is read
- Given the peer mentor confirms the sensitive field warning (e.g., double-tap), when the field content is read, then the full value is announced without the warning repeating
- Given the sensitive-field-configuration has 'email' marked as sensitive, when a screen reader focuses on an email field, then the warning is triggered for that field
- Given a field not marked as sensitive in configuration, when the screen reader focuses on it, then no warning is shown and the content is read normally
- Given a sensitive-field-warning-dialog is shown visually, when the screen reader is active, then the dialog message is the first announced element and focus is placed within it
- Given an organisation admin has not configured sensitive fields, when the app falls back to defaults, then standard sensitive fields (name, phone, address) are always protected
Business Value
Blindeforbundet explicitly required this feature in workshops, noting it is unique to their use case. Peer mentors handle highly personal health and contact information; accidental disclosure in public spaces could violate GDPR and erode trust between the organisation and its members. This feature directly addresses a named requirement from the client and is a differentiator showing genuine accessibility expertise beyond basic compliance.
Components
- Sensitive Field Warning Dialog ui
- Live Region Announcer ui
- Screen Reader Detection Service service
- Sensitive Field Privacy Guard service
- Sensitive Field Configuration data
- Accessibility Settings Repository data
- Semantics Service Facade infrastructure
- Accessibility Live Region Announcer infrastructure