On this page
Published: September 7, 2026
A spinner says that something may be happening. It does not explain how long the task may take, whether a visitor can leave, or what happens after a failure. Start the brief with the real process and its uncertainty.
Match feedback to the operation
Use determinate progress only when the system can report a meaningful fraction. For unpredictable waits, explain the action underway and set an honest expectation. Multi-step journeys can show completed, current, and remaining stages without inventing a percentage.
Define interruption rules
State whether the visitor may cancel, navigate away, retry, or continue in the background. Explain what data is saved and what may need to be repeated. Do not show success until the service has confirmed the outcome.
Review the accessible experience
- Announce important state changes without excessive repetition.
- Keep status text available alongside animation.
- Respect reduced-motion preferences.
- Retain keyboard focus on a useful control.
- Make timeout and failure actions specific.
Test time, not just screens
Exercise quick success, slow success, known progress, stalled work, cancellation, network failure, and duplicate requests. Record timestamps and system responses with the visual evidence.
Further reading
Related Articles
Include progress behavior in the component contract and service-level assumptions.
Ready to plan your next step?
Contact WebsiteDesignOutsource.com
Turn the guidance into a reviewable handoff
Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.
Plan a website production handoff