Progress bars are tracks with a fill that report where something stands as a share of a whole the reader can see. The five compositions here stretch that further than a loading bar. A stepped compression control lands a square knob on one of five stops, a spending meter runs a second bar behind the first, a semicircular ring of segments carries a level stepper, an intensity bar is scaled from low to high, and a dial reads its highlighted arc as an angle.
What separates them is who owns the value. Every one of these can be dragged or stepped, which makes them controls that happen to look like meters, and a control owes things a readout does not: a handle you can see, keyboard steps, and a value read back as a number. The inverse matters more. A quota meter is not progress. Nothing is completing, so a full bar means the ceiling has been hit, and drawing that like a finished download says the opposite of the truth.
An account page showing space used against the plan's ceiling, with a second bar behind the first for what is pending. The footer states both figures so nobody has to estimate the fill by eye.
A multi-step purchase or signup where the bar answers the only question anyone has at step two, which is how many more there are. Steps are countable, so the fill is exact rather than estimated.
Export and encoding dialogs where quality is picked along a handful of named stops rather than a free range. The knob lands on a stop and the readout names it, so the value is never stranded between two labels.
Vehicle and robotics dashboards where a value swings around a centre instead of filling from zero. The arc reads as an angle, and the stepper beside it lets the same control be nudged by hand during setup.
Use a progress bar when the total is known and the fill can be trusted: a file of known size, a form with a fixed number of steps, a quota against its limit. Use a spinner when there is no total to divide by. A bar whose fill is guessed is worse than a spinner, because it makes a promise about time that it then breaks.
A bar that only reports should expose a progressbar role carrying its current, minimum and maximum values, so assistive technology can announce the position without reading pixels. One the person can change is a slider instead: it takes keyboard focus, moves on the arrow keys, and announces the new value after each step. Never let colour alone signal that a value has passed its limit.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Progress bars are tracks with a fill that report where something stands as a share of a whole the reader can see. The five compositions here stretch that further than a loading bar. A stepped compression control lands a square knob on one of five stops, a spending meter runs a second bar behind the first, a semicircular ring of segments carries a level stepper, an intensity bar is scaled from low to high, and a dial reads its highlighted arc as an angle.
What separates them is who owns the value. Every one of these can be dragged or stepped, which makes them controls that happen to look like meters, and a control owes things a readout does not: a handle you can see, keyboard steps, and a value read back as a number. The inverse matters more. A quota meter is not progress. Nothing is completing, so a full bar means the ceiling has been hit, and drawing that like a finished download says the opposite of the truth.
An account page showing space used against the plan's ceiling, with a second bar behind the first for what is pending. The footer states both figures so nobody has to estimate the fill by eye.
A multi-step purchase or signup where the bar answers the only question anyone has at step two, which is how many more there are. Steps are countable, so the fill is exact rather than estimated.
Export and encoding dialogs where quality is picked along a handful of named stops rather than a free range. The knob lands on a stop and the readout names it, so the value is never stranded between two labels.
Vehicle and robotics dashboards where a value swings around a centre instead of filling from zero. The arc reads as an angle, and the stepper beside it lets the same control be nudged by hand during setup.
Use a progress bar when the total is known and the fill can be trusted: a file of known size, a form with a fixed number of steps, a quota against its limit. Use a spinner when there is no total to divide by. A bar whose fill is guessed is worse than a spinner, because it makes a promise about time that it then breaks.
A bar that only reports should expose a progressbar role carrying its current, minimum and maximum values, so assistive technology can announce the position without reading pixels. One the person can change is a slider instead: it takes keyboard focus, moves on the arrow keys, and announces the new value after each step. Never let colour alone signal that a value has passed its limit.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.