Accessibility Statement
Feature Detail
Description
The Accessibility Statement screen publishes the platform's formal WCAG 2.2 AA compliance statement for the Meander Mobile App. It covers conformance level, scope, known limitations, the date of the last accessibility review, and a contact for reporting barriers. The screen is pre-authentication accessible and linked from Help & Support and Settings. It satisfies the Norwegian accessibility regulation requirement that digital services publish a compliance statement visible to all users, including those using assistive technology.
Sources & reasoning
Section §1.2 mandates WCAG 2.2 AA as an absolute MVP requirement with no exceptions across all four organizations. Norwegian law (likestillings- og diskrimineringsloven) requires digital services to publish an accessibility statement. The blueprint marks this feature MVP under the always-on help-support module. The Blindeforbundet screen-reader dependency makes the statement especially trust-critical, beyond legal compliance alone.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Publishing an accessibility statement is a legal obligation under Norwegian anti-discrimination law for digital services, covering all four tenant organizations. The Meander platform commits to WCAG 2.2 AA compliance from day one, and the statement operationalizes that commitment by making it auditable and publicly visible. For Blindeforbundet users who rely on screen readers daily, a published accessibility statement signals institutional seriousness about inclusion and builds the trust needed for adoption. The statement also creates accountability - publishing known limitations with remediation timelines encourages the team to track accessibility gaps systematically rather than treating WCAG compliance as a one-time check.
Implemented as a static Flutter screen with structured sections: conformance level, scope, known limitations, last review date, and feedback contact. Content is managed as a versioned backend resource or locale asset to allow server-side updates without an app release. The screen must itself be fully WCAG 2.2 AA compliant - scalable text, semantic screen reader traversal, and 4.5:1 minimum contrast - as it is the compliance statement for the app it lives in. Accessible pre-authentication. A feedback link routes to the Contact Us screen or a designated accessibility email. Layout kept simple: headings, paragraphs, and a contact link; no interactive elements beyond scrolling and the feedback link.
Components (44)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.