Run AccessibilityAuditService on all existing screens
epic-screen-reader-support-core-services-task-017 — Execute AccessibilityAuditService.runAudit() against every existing application screen using the test harness. Collect all per-screen audit reports, aggregate violations by type and severity, and produce a consolidated remediation backlog. Log the full report as a structured artefact in the CI pipeline so baseline violations are tracked. This task establishes the accessibility debt baseline before the pilot.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 6 - 158 tasks
Can start after Tier 5 completes
Implementation Notes
Enumerate screens programmatically from the GoRouter configuration rather than hardcoding a list, to ensure new screens are automatically included in future audit runs. For screens that require navigation state (e.g. wizard step 2 requires step 1 completion), create minimal navigation helpers that drive the wizard to the target step before running the audit. Severity classification should follow WCAG 2.2 AA: missing semantic labels and focus traps are critical; insufficient tap target size and missing heading roles are major; colour contrast on non-interactive decorative elements is minor.
The baseline artefact is explicitly for the Blindeforbundet pilot preparation — document this context in the report header. After the audit, do NOT automatically fix violations in this task; create tickets in the remediation backlog instead.
Testing Requirements
This is an infrastructure task, not a feature test. The audit runner itself should be a standalone integration_test script. Use a seeded mock auth session so all role-gated screens (coordinator, org admin, peer mentor) are reachable. For multi-step wizards, navigate to each step individually so each step's widget tree is audited.
Write a helper that enumerates all GoRouter routes and drives the harness to each one. After each screen audit, serialise the report using jsonEncode() and append to a per-run output file. Validate that the output JSON is parseable in a post-audit assertion to catch serialisation bugs.
Flutter's build pipeline and SemanticsService.announce() operate asynchronously. Announcements triggered too early (before the semantic tree settles) may be swallowed silently on both platforms, causing acceptance criteria around the 500ms window to fail intermittently in CI and on device, which would block pilot launch.
Mitigation & Contingency
Mitigation: Implement the LiveRegionAnnouncer with a post-frame callback delay and an internal timing guard. Write integration tests using WidgetTester.pump() sequences that verify announcement delivery across multiple frame boundaries. Validate on physical devices at each sprint boundary, not only in CI.
Contingency: If consistent announcement timing cannot be achieved within Flutter's semantic pipeline, switch to a platform channel approach that calls native UIAccessibility.post (iOS) and AccessibilityManager.announce (Android) directly, bypassing Flutter's intermediary.
Flutter does not natively emit a focus-gain event to Dart code when VoiceOver or TalkBack moves focus to a specific widget. If the intercept mechanism for the SensitiveFieldWarningDialog relies on an unsupported or undocumented hook in the semantics tree, it may miss focus events for some field types or in some navigation contexts, leaving sensitive data unprotected.
Mitigation & Contingency
Mitigation: Prototype the focus-intercept mechanism during the first sprint of this epic, before building the dialog UI. Evaluate Flutter's SemanticsBinding.instance callbacks and custom SemanticsActions as intercept points. Document the chosen mechanism with platform compatibility notes.
Contingency: If no reliable focus-intercept is available, implement an alternative where sensitive fields show a static 'Screen reader active — tap to reveal' overlay instead of an OS dialog, which is less seamless but achieves equivalent privacy protection without relying on an unreliable event hook.
The AccessibilityTestHarness depends on internal flutter_test semantic tree APIs that can change between Flutter minor versions. If the project upgrades Flutter during this epic, the harness may break silently, causing CI accessibility tests to pass while actually skipping assertions.
Mitigation & Contingency
Mitigation: Pin the Flutter SDK version in pubspec.yaml for the duration of this epic. Document which flutter_test APIs are used and their stability tier. Add a canary test that explicitly fails if the semantic tree API surface changes.
Contingency: If a forced Flutter upgrade breaks the harness, prioritise patching the harness as a blocking task before any other epic work continues, using the canary test failure as the trigger.