Click. Nothing happens. Click again. Now there are two submissions. A useful progress indicator prevents that uncertainty by explaining what the website is doing and what the visitor should expect next.
Match the indicator to the task
Use a determinate indicator when the system can measure progress meaningfully. If it cannot, use a clear status message or an indeterminate indicator rather than inventing a percentage. For longer tasks, explain what is happening in plain language and keep instructions visible.
Make status accessible
Do not communicate progress through motion or color alone. Provide text and appropriate accessible status announcements for important changes. Respect reduced-motion preferences and avoid animations that make content hard to use. The exact implementation should be tested with the interaction and assistive tools it needs to support.
Plan the failure state
Explain what happens if the process times out or fails. Preserve entered information when practical and provide a sensible retry route. Avoid suggesting repeated submissions when that could create duplicate orders or requests. A reassuring spinner is useful only if the process eventually resolves clearly.
Your next steps
- Use real progress measurements when available.
- Add understandable status text.
- Check keyboard and accessible announcements.
- Design success, timeout, and retry messages.
For further guidance, see W3C’s practical accessibility tutorials.
Keep exploring
Need a hand putting this into practice?
I help small businesses bring their websites, branding, and marketing together with practical advice and personal attention. Tell me what you’re working on, and let’s discuss the next step.
