Test ConfirmBeforeSubmitScreen accessibility and flow
epic-cognitive-accessibility-wizard-ui-task-013 — Write integration tests for ConfirmBeforeSubmitScreen verifying that the Confirm action fires WizardSubmitted, the Go Back action returns to the previous step with field values preserved, and that the screen is fully navigable by screen reader without any unlabelled interactive elements. Check that the screen does not appear if the user navigates back from it using the device back button.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 4 - 323 tasks
Can start after Tier 3 completes
Implementation Notes
Use bloc_test's `whenListen` to pre-position the WizardStateManager in the confirmation state, avoiding the need to run through the full wizard in each test case. For semantics testing, wrap the test widget in a MediaQuery with textScaleFactor 1.0 to avoid flaky layout-dependent semantics. Use flutter_test's `SemanticsHandle` (tester.ensureSemantics()) to enable the semantics tree. For device back simulation, prefer sending the SystemChannels.navigation 'popRoute' message rather than calling Navigator.pop directly, as this mirrors real device behaviour.
Ensure test cleanup restores the NavigatorObserver to avoid state leakage between tests.
Testing Requirements
Integration tests using flutter_test with BLoC test utilities (bloc_test package). Use tester.pumpWidget with a BlocProvider supplying a pre-seeded WizardStateManager positioned at the confirmation step. Test Confirm tap: find by semantics label, tap, verify WizardSubmitted in emitted events. Test Go Back tap: find by semantics label, tap, verify previous-step state restored.
Accessibility test: call tester.getSemantics on the root and traverse the tree asserting every SemanticsNode with hasTapAction has a non-empty label. Device back test: simulate SystemNavigator.pop and assert the route stack lands on the preceding wizard step widget, not ConfirmBeforeSubmitScreen.
The WizardStateManager BLoC must guarantee that step transitions only occur on explicit user action, never automatically. Subtle reactive patterns in Bloc (e.g. stream listeners triggering add() calls) could inadvertently auto-advance the wizard, violating the core cognitive accessibility rule and creating a regression that is difficult to detect without dedicated tests.
Mitigation & Contingency
Mitigation: Write a dedicated unit test that subscribes to the BLoC stream and asserts no StepChanged event is emitted for 5 seconds after a state update, without an explicit user-sourced event being dispatched. Make this test part of the CI gate for the WizardStateManager.
Contingency: If an auto-advance regression is discovered post-integration, introduce a mandatory UserActionToken parameter on all step-transition events so the BLoC can structurally refuse transitions that do not originate from a user gesture handler.
The ConfirmBeforeSubmitScreen requires deep-linking back to specific wizard steps for corrections. Implementing bidirectional navigation within a multi-step wizard while preserving all previously entered state is architecturally non-trivial and may conflict with the existing StatefulShellRoute navigation setup described in the app architecture.
Mitigation & Contingency
Mitigation: Design the ConfirmBeforeSubmitScreen's back-navigation links to dispatch a GoToStep event on the WizardStateManager rather than using GoRouter's pop() chain. This keeps navigation state entirely in the BLoC and avoids coupling to the router's stack semantics.
Contingency: If BLoC-driven step navigation proves incompatible with the router, implement the correction flow as a dedicated sub-route that pre-populates its form from the WizardStateManager's current draft, then merges the edited field back into the draft on completion before returning to the confirm screen.
The CognitiveAccessibilityAudit utility must inspect live widget trees for violations such as icon-only buttons. Flutter's widget tree inspection APIs are available in test mode but have limitations in identifying semantic intent (e.g. distinguishing a decorative icon from a navigation button). False negatives could give a false sense of compliance.
Mitigation & Contingency
Mitigation: Augment the audit with a convention-based approach: require all navigation buttons to use a named wrapper widget (e.g. LabelledNavigationButton) that the audit can detect by type, rather than relying solely on widget-tree semantics analysis.
Contingency: If widget-tree detection proves insufficiently reliable, scope the CognitiveAccessibilityAudit to route-configuration analysis (verifying back navigation availability per route) and static analysis of wizard step count definitions via the CognitiveLoadRuleEngine, which provides deterministic results.
The InlineContextualHelpWidget sources content from a bundled JSON asset via the HelpContentRegistry. If help texts are missing for newly added screens or fields (a likely scenario as the 61-feature app grows), the widget silently shows nothing, degrading the accessibility experience without any visible failure.
Mitigation & Contingency
Mitigation: Integrate a CognitiveAccessibilityAudit check that verifies every registered (screenId, fieldId) pair that requests help has a corresponding entry in the HelpContentRegistry bundle. Run this check in CI as part of the audit report.
Contingency: Add a debug-mode overlay that highlights fields with missing help entries using a visible warning indicator, making coverage gaps immediately obvious to developers during local development before they reach CI.