Experience Organization-Specific Terminology and Branding
Each partner organization (NHF, Blindeforbundet, HLF, Barnekreftforeningen) uses different terminology for the same concepts. For example, what one organization calls a 'peer mentor' another may call 'likeperson' or use a different term entirely. The terminology system dynamically resolves label keys to organization-specific strings fetched from the backend and cached locally. All UI text rendered through terminology-aware widgets will display the correct terms for the active organization. This system also feeds WCAG semantics labels so screen readers announce the correct terminology.
User Story
Acceptance Criteria
- Given a peer mentor selects their organization, when the home screen loads, then all navigational labels, section headers, and action buttons display terminology configured for that organization
- Given the app is running with cached terminology, when the peer mentor uses the app offline, then the cached terminology is used and no text falls back to raw label keys
- Given the terminology sync service fetches updated labels from the backend, when new terminology is available, then the cache is updated and the UI reflects the changes on the next navigation
- Given a screen reader is active, when the peer mentor navigates through the app, then WCAG semantics labels use the organization-correct terminology as resolved by the wcag-semantics-label-resolver
- Given the organization has not configured custom terminology for a label key, when the label is rendered, then a sensible default fallback value is shown rather than a raw key
Business Value
The partner organizations serve distinct user communities with their own established vocabularies and cultures. Using organization-specific terminology significantly improves perceived fit and reduces cognitive load, especially for elderly or cognitively challenged users identified in the workshop (e.g., stroke survivors in NHF). It also reduces training burden for organization staff who can refer to app features using their existing internal language, improving adoption rates during the onboarding phase.
Components
- Organization Labels Provider infrastructure
- Organization Labels Provider infrastructure
- Organization Labels Provider infrastructure
- Terminology-Aware Text Widget ui
- Organization Labels Notifier service
- Label Key Resolver Service service
- Terminology Sync Service service
- Terminology Repository data
- Terminology Local Cache Adapter data
- Label Key Registry infrastructure
- Terminology Riverpod Providers infrastructure
- WCAG Semantics Label Resolver infrastructure