Lead: << Your name/s >> << Select the status - ONGOING WAITING DONE PUBLISHED ON HOLD >>
Related Pages: << Links to related pages, if relevant >>
Description
Progress bars express an unspecified wait time or display the current completed ratio of a process or action.
Types
| Type | Usage | Image |
|---|---|---|
Determinate | For operations in which the length of the process is known. Determinate operations display the indicator increasing in width from 0 to 100% of the track, in sync with the process’s progress. |
|
Indeterminate | For operations in which the length of the process is not known. Indeterminate operations display the indicator continually growing and shrinking along the track until the process is complete. |
|
Usage & Behaviour
Progress bars inform users about the status of ongoing processes, such as loading a page, submitting a form, or saving updates. They communicate an applications state and indicate available actions, such as whether users can navigate away from the current screen.
General guidelines
Structure
Linear progress indicators are composed of two required elements:
- Track - The track is a fixed width rule, with set boundaries for the indicator bar to travel along.
- Indicator Bar - The bar animates along the length of the track.
Placement and Positioning
The placement of a progress indicator can indicate the scope of a process. Progress bars should only be placed at the top or in the center of a container or component. For example:
- A progress bar at the center of the screen should indicate loading all screen content (and that no interaction is possible until complete)
- A progress bar attached to the top a container, such as a card indicates the process applies to that particular item (and that interaction with the rest of the UI is possible)
Default State
Progress bars should be hidden by default and only appear on screen when they are active. Once complete, the progress bar should return to it's default state (removed from view) in most cases replaced by the content that was loaded.
States
<<e.g. active disabled, error, hover, temporary (spinner size), empty etc...>>
Best practices
<<e.g. Slider should display a label its on>>
Accessibility compliance
A progress bar indicates that the user's request is received and is in the process of executing the task. Content authors should provide values of aria-valuemin, aria-valuemax and aria-valuenow where the aria-valuemax is known. Further guidelines for optimum compliance can be found at https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_progressbar_role.
Focus management
Progress bars a purely visual indicator that contains no user interaction and therefore cannot be focused on.
Screen reader support
<<Make sure the components support screen reader for content or behaviour where needed - see /wiki/spaces/UX/pages/308248620 >>
Contrast & size compliance
<<Visual designers must comply with the minimal of /wiki/spaces/UX/pages/301498483 for each component>>
Design
| Zeplin link | Screen thumbnail |
|---|---|
|
