# Stepper and Progress Indicator Animation for Multi-Step Flows

> A stepper shows where someone is in a multi-step flow and how much is left. Animate the change between steps so people see progress happen, mark completed steps clearly, and let people go back without losing data. Keep the number of steps small, label them, and make the current step announced to screen readers.

Updated November 2026. Source: https://www.exodeui.com/learn/stepper-progress-animation/

## Key takeaways

- Use steppers for linear, infrequent, multi-step tasks
- Show completed, current, upcoming and error states
- Animate connector fill and slide content in the direction of travel
- Allow going back; announce the current step

## When to use a stepper

Nielsen Norman Group describes wizards as useful for linear processes that people do rarely, where breaking a task into steps reduces errors. Checkouts, sign-ups, setup flows and long forms are typical. For short forms, a single page is usually faster.

## What the stepper should show

Each step marker needs a clear state:

- Completed: filled, with a check mark
- Current: highlighted and labelled
- Upcoming: muted but visible
- Error: marked if a completed step needs attention

## Animating between steps

When people complete a step, fill the connector line toward the next marker and turn the finished marker into a check mark. Slide the content in the direction of travel: forward moves left, back moves right (mirrored in right-to-left languages). Keep transitions around 200 to 300 ms so the flow feels quick.

## Going back and accessibility

Let people click completed steps to edit them, and keep their entries. Use a list with aria-current="step" on the current item, include "Step 2 of 4" in text, and move focus to the new step's heading after each transition.

## Building this in ExodeUI

In ExodeUI, which we make, the stepper can be one component with a number input for the current step; springs animate the connector fill and check marks as the value changes. Keep the step labels and focus handling in your app's UI.

## Frequently asked questions

### How many steps should a stepper have?

Usually three to five. More steps can feel long; group related fields.

### Should a stepper be clickable?

Completed steps should be, so people can go back and edit. Future steps usually should not.

### How do I make a stepper accessible?

Use a list, mark the current step with aria-current="step", show "Step X of Y" in text and move focus to the new step.

### Which direction should step transitions slide?

In the direction of reading progress: forward moves content toward the start side, back the opposite way.

## Related

- [Onboarding checklists vs wizards](https://www.exodeui.com/learn/onboarding-checklists-vs-wizards/)
- [Checkout form abandonment UX](https://www.exodeui.com/learn/checkout-form-abandonment-ux/)
- [Progress ring animation](https://www.exodeui.com/learn/progress-ring-animation/)
- [Form validation animation](https://www.exodeui.com/learn/form-validation-animation/)
