Skip to content

CHOR-05 — Reduced-motion strategy for choreography (UXE-proposed, Robert-decided) #36157

@robertpenner

Description

@robertpenner

Description: Two phases. Phase 1 (analysis): UXE produces a proposal doc analyzing options — collapse to instantaneous / collapse to a quick fade / preserve sequencing with compressed timing / per-scenario configurable. Robert reviews and decides which strategy to adopt. Phase 2 (implementation): UXE implements the chosen strategy across CHOR-02 scenarios; updates docs.

Why it matters: Reduced-motion compliance is on the v9 Stable checklist and in the Default DoD. Choreography components have unique reduced-motion semantics — sequencing has meaning. Beta exit criteria should include a defined, documented reduced-motion strategy.

  • Difficulty: Medium-Hard
  • Dependencies: CHOR-01 (criteria mention this), CHOR-02 (scenarios to apply it to); benefits from CHOR-04 observations
  • Sequencing: M3 W9–10 (analysis), W10–11 (implementation), in parallel with CHOR-04
  • Pairing: 1× decision conversation between Phase 1 and Phase 2 (~1 hr)
  • Mode: UXE-proposes; Robert decides; UXE implements
  • Tags: partner-pickup, choreography-beta-blocker, a11y

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions