WCAG 2.2 AA Compliance
Feature Detail
Description
This feature ensures the Meander Mobile App meets WCAG 2.2 Level AA accessibility standards from day one, covering all screens and interactions without exception. It encompasses screen reader support (VoiceOver/TalkBack) with semantic labels, minimum 4.5:1 text contrast ratios, scalable typography up to 200%, minimum 24x24px touch targets, full keyboard navigation with visible focus indicators, and non-drag alternatives for all drag-based interactions. Cognitive accessibility - simplified navigation, logical flows, and clear error messages with suggested fixes - is mandated from the outset for users with motor, cognitive, and sensory impairments.
Sources & reasoning
Lines 28 and 30 declare WCAG 2.2 AA an absolute MVP requirement with no organizational exemptions, and line 321 repeats this explicitly under Fase 1 scope. The priority matrix (line 143) marks it MUST HAVE Phase 1 for all five organizations. This is the strongest mandate in the source doc, directly placing target_release at MVP with no ambiguity.
-
docs/source/likeperson.md · line 28Appen SKAL oppfylle WCAG 2.2 nivå AA som minimumskrav for alle skjermer og interaksjoner - fra dag én, for alle organisasjoner. Ingen organisasjon er unntatt eller utsatt til senere fase.
-
docs/source/likeperson.md · line 30WCAG 2.2 AA compliance er et absolutt krav for MVP - ikke noe som fikses etterpå.
-
docs/source/likeperson.md · line 321WCAG 2.2 AA compliance fra dag én - for alle organisasjoner, uten unntak
Analysis
All five partner organizations serve users with diverse accessibility needs. Blindeforbundet's peer mentors are visually impaired and depend on screen readers; NHF explicitly serves stroke survivors and users with cognitive challenges. An inaccessible app would exclude a significant portion of the target audience and directly undermine the platform's value proposition. WCAG 2.2 AA compliance is an absolute MVP requirement with no phase-out exemptions and no per-organization deferrals. Beyond ethical obligations, compliance de-risks the platform against legal challenges in Norway's regulated accessibility landscape and signals organizational trust to all partner organizations simultaneously, accelerating adoption.
Flutter's Semantics widget must wrap every interactive element, with MergeSemantics and ExcludeSemantics applied judiciously to avoid screen reader noise. Design tokens must enforce 4.5:1 contrast ratios (3:1 for large text and UI components) at the token system level, preventing non-compliant values from entering the widget tree. Touch targets are enforced at 24x24px minimum via Material tap target size constraints. All drag interactions require a non-drag alternative (tap or keyboard). The AccessibilityAuditService runs Flutter's built-in accessibility auditing APIs, and SemanticLabellingService ensures consistent label application across the widget tree. Vertical scroll and back-button navigation are the interaction norms.
Components (6)
Shared Components
These components are reused across multiple features
User Stories
No user stories have been generated for this feature yet.