usage
- Pass stable step identifiers and human-readable labels
- Map application job state before rendering
- Use error only on the step where progress stopped
- Keep eligibility, state transitions and status inference in the consuming application
Administration
Workflow steps
Show progress through a short, ordered workflow without inferring business state.
Production component
Live preview
This example is rendered from the same package consumed by UJ applications.
- UploadComplete
- ValidateCurrent
- ConfirmUpcoming
- ResultUpcoming
Contract
Usage and quality requirements
The contract keeps purpose, states and ownership visible before a component is reused.
states
- complete
- current
- upcoming
- error
- two to six steps
- long labels
- narrow viewport
- dark theme
- forced colours
purpose
Communicate a short workflow's ordered progress using explicit complete, current, upcoming and error states supplied by the owning application.
responsive
- Horizontal progress at wider widths
- Vertical progress at 320px
- 768px
- 1440px
- 200% text resize
accessibility
- Named ordered list
- Current step uses aria-current=step
- Every state has visible text
- State is not conveyed by colour alone
- Source order matches workflow order
- WCAG 2.2 AA
runtime Boundary
The component performs no fetching, routing, polling, state transition or job-status inference.
source Authority
The owning application's persisted workflow state