🏠 Overview › 🧩 Components ›🧩 Readout Warning Service

Readout Warning Service

Component Detail

Service Layer medium complexity mobile
0
Dependencies
0
Dependents
2
Entities
0
Integrations

Description

A service that coordinates the warning prompt flow when a screen reader is active and a sensitive field is about to be announced. It tracks per-field unlock state, enforces confirmation gestures, and integrates with the platform accessibility APIs.

Feature: Sensitive Field Readout Warning

readout-warning-service

Sources & reasoning

Explicitly called out in §1.2 (line 24) as an NHF-flagged requirement under the universal-design MUST HAVE umbrella. It is bundled with the Phase 1 WCAG accessibility scope and depends on the WCAG primitives to wrap fields uniformly.

  • Varsling ved opplesning av sensitive felt (NHF).
  • Skjermleser-støtte (VoiceOver/JAWS): Alle interaktive elementer skal ha semantiske labels og ARIA-attributter. Særlig kritisk for Blindeforbundet, men relevant for alle.

Responsibilities

  • Detect when a screen reader is active on the device
  • Present confirmation prompts before announcing sensitive content
  • Track unlock state and timeouts per sensitive field
  • Log readout events for audit and trust transparency
  • Expose configuration for sensitivity levels and gesture requirements

Interfaces

isScreenReaderActive(): boolean
promptForReadout(fieldId, sensitivityLevel): Promise<boolean>
registerSensitiveField(fieldId, config): void
getUnlockState(fieldId): UnlockState

Related Data Entities (2)

Data entities managed by this component

Contacts 24 fields core Notes 15 fields core