🏠 Overview › ✅ Implementation Tasks ›✅ epic-cognitive-accessibility-wizard-ui-task-001

Scaffold WizardStateManager BLoC class

epic-cognitive-accessibility-wizard-ui-task-001 — Create the BLoC class skeleton for WizardStateManager including state classes (WizardIdle, WizardInProgress, WizardPaused, WizardComplete), event classes (WizardStarted, WizardStepAdvanced, WizardPaused, WizardResumed, WizardSubmitted), and the base mapEventToState wiring. No persistence logic yet — pure in-memory structure.

critical priority medium complexity frontend pending frontend specialist Tier 0

Acceptance Criteria

WizardStateManager extends Bloc<WizardEvent, WizardState> and compiles without errors
State hierarchy: WizardState (sealed/abstract) with concrete subclasses WizardIdle, WizardInProgress, WizardPaused, WizardComplete — all are immutable (use Equatable or @immutable annotation)
WizardInProgress holds: currentStepIndex (int), totalSteps (int), fieldValues (Map<String, dynamic>)
WizardPaused holds: pausedStepIndex (int), draftFieldValues (Map<String, dynamic>), pausedAt (DateTime)
WizardComplete holds: submittedAt (DateTime), finalFieldValues (Map<String, dynamic>)
Event hierarchy: WizardEvent (sealed/abstract) with concrete subclasses WizardStarted (totalSteps), WizardStepAdvanced (fieldValues for current step), WizardPaused (no extra fields needed), WizardResumed (no extra fields), WizardSubmitted (finalFieldValues)
on<WizardStarted> transitions from WizardIdle to WizardInProgress(currentStepIndex: 0)
on<WizardStepAdvanced> increments currentStepIndex and merges fieldValues; emitting WizardComplete when advancing past last step
on<WizardPaused> transitions from WizardInProgress to WizardPaused, capturing current step and fields
on<WizardResumed> transitions from WizardPaused to WizardInProgress restoring index and fields
on<WizardSubmitted> transitions to WizardComplete
All event handlers are registered in the BLoC constructor body
No SharedPreferences, Supabase, or file I/O calls in this task — pure in-memory

Technical Requirements

frameworks
Flutter
BLoC
performance requirements
State objects are immutable — use copyWith pattern for mutations
No async operations in this scaffold — all handlers are synchronous
security requirements
fieldValues map must not log PII to console — no print/debugPrint of map contents

Execution Context

Execution Tier
Tier 0

Tier 0 - 440 tasks

Implementation Notes

Use the flutter_bloc package (already in tech stack). Prefer sealed classes (Dart 3) for WizardEvent and WizardState to enable exhaustive pattern matching. Define all state and event classes in separate files: lib/features/wizard/bloc/wizard_state.dart and lib/features/wizard/bloc/wizard_event.dart, with the BLoC in lib/features/wizard/bloc/wizard_state_manager.dart. Use Equatable for all state classes so BLoC's equality check works correctly and avoids redundant rebuilds.

The WizardStateManager constructor should take totalSteps as a parameter or receive it via WizardStarted event — prefer the event approach for flexibility. Keep the BLoC thin: no domain logic, only state transitions.

Testing Requirements

This task produces the scaffold only — full unit tests are handled in task-004. However, write a minimal smoke test in the same PR: create a WizardStateManager instance, add WizardStarted(totalSteps: 3), and assert state is WizardInProgress with currentStepIndex == 0.

This confirms the BLoC wires correctly before dependent tasks begin.

Component
Wizard State Manager
service medium
Epic Risks (4)
high impact medium prob technical

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.

medium impact medium prob integration

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.

medium impact medium prob technical

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.

low impact high prob scope

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.

Quick Links
All Tasks Execution Plan