Accessibility Statement
Feature Detail
Description
The Accessibility Statement feature provides a dedicated screen in the mobile app where users can read the platform's formal accessibility conformance statement. The statement documents the WCAG 2.2 AA compliance level achieved, known limitations, contact details for reporting accessibility barriers, and the date of the last accessibility review. It satisfies the Norwegian legal requirement under the Act on Universal Design of ICT solutions (Forskrift om universell utforming av IKT). This screen is accessible from the Help & Support area and does not require authentication. It is separate from the Privacy Policy to reflect its distinct regulatory basis and to make accessibility-specific information easy to locate for users who rely on assistive technology.
Sources & reasoning
Listed in the area taxonomy (line 480). Blueprint marks MVP. The source's absolute language around WCAG 2.2 AA compliance ("fra dag én, for alle organisasjoner", lines 28-30) and the Norwegian regulatory environment for Bufdir-funded organizations make a formal accessibility statement a hard legal requirement at launch, not a nice-to-have.
-
docs/source/likeperson.md · line 28-30Alle fire organisasjoner har brukere med svært ulike forutsetninger - motoriske, kognitive og sensoriske. Appen SKAL oppfylle WCAG 2.2 nivå AA som minimumskrav for alle skjermer og interaksjoner - fra dag én, for alle organisasjoner.
-
docs/source/likeperson.md · line 480| help-support | Help & Support | Contact Us, Privacy Policy, Accessibility Statement, FAQ |
Analysis
Norwegian public-facing digital services and applications used by organizations receiving public funding (such as Bufdir-funded organizations) are legally required to publish an accessibility statement under the Universal Design of ICT Regulation. All four customer organizations - NHF, Blindeforbundet, HLF, and Barnekreftforeningen - receive Bufdir funding and have users with disabilities. Publishing a compliant accessibility statement demonstrates legal conformance, reduces liability, and signals organizational commitment to inclusion. For Blindeforbundet in particular, whose users depend on screen readers, the ability to verify compliance expectations before using the app is operationally important. The statement also provides a feedback channel for users encountering barriers, enabling continuous accessibility improvement.
Implementation is structurally identical to the Privacy Policy screen: a scrollable static or remotely fetched document rendered in a Flutter Text widget with full WCAG 2.2 AA styling. The statement content must include the conformance level (AA), the standard referenced (WCAG 2.2), scope (the Meander mobile application), known exceptions with justification, and a contact mechanism for reporting issues. The contact mechanism can reuse the same endpoint as the Contact Us feature to avoid duplicating backend logic. The screen should be reachable without authentication. For MVP, a static bundled statement is acceptable; a future iteration could fetch a remotely updated version to avoid app releases for minor statement updates. Norwegian Bokmål is the primary language; English may be added later.
Components (10)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.