Version 6.0.0

Progress circle

Progress circles show the progression of a system operation such as downloading, uploading, processing, etc. in a visual way. They can represent determinate or indeterminate progress.

Example of an indeterminate progress circle in action, just spinning and spinning.

Anatomy#


Diagram of the anatomy of a progress circle, showing the track and fill.

Options#


Key example showing both determinate and indeterminate progress circles in default variant.

Default variant#

Progress circles are used to visually show the progression of a system operation such as downloading, uploading, processing, etc. By default, progress circles have a blue fill that shows the progress.

Example of an 'over background' progress circle.

Over background variant#

When a progress circle needs to be placed on top of a colored background, use the over background variant. This progress circle uses a static white color regardless of the color theme. Make sure the background offers enough contrast for the progress circle to be legible.

Examples of the size variants of progress circle, showing small, medium, and large sizes.

Size#

Progress circles come in 3 sizes: small, medium (default), or large. These are available to fit various contexts. For example, the small progress circle can be used in place of an icon or in tight spaces, while the large one can be used for full-page loading.

Examples of both a determinate and indeterminate progress circle.

Indeterminate#

A progress circle can be either determinate or indeterminate. By default, progress circles are determinate. Use a determinate progress circle when progress can be calculated against a specific goal (e.g., downloading a file of a known size). Use an indeterminate progress circle when progress is happening but the time or effort to completion can’t be determined (e.g., attempting to reconnect to a server).

Key example of determinate progress circle with the value going from 0 to 1, which shown by the blue fill.

Value#

The value shows the progress of a system operation, from 0 to 1, such as downloading, uploading, processing, etc. This is not applicable when a progress bar is indeterminate.

Table of options#

From the design point of view, each component has a number of options. These options and their names are platform agnostic, and each implementation should adapt these to fit into their framework.

PropertyValuesDefault Value
variant
default / over background
default
size
small / medium / large
medium
is indeterminate
yes / no
no
value
number (0 to 1)
Not applicable when indeterminate.
0

Usage guidelines#


Use progress circles for loading views#

Medium and large progress circles are optimized for large areas with no space constraints. Use them for loading content into views (e.g., web pages, panels, etc.)

Illustration showing large progress circle in their preferred use in a content view.

Use small progress circle when space is limited#

Small progress circles are well suited when space is limited both vertically and horizontally, such as in buttons, menu items, and input fields.

Illustration of a small progress circle being used inside a call-to-action button.

Internationalization#


Example of a determinate and indeterminate progress circle in RTL layout, where the fill continues to progress clockwise.

RTL#

For RTL (right-to-left) languages, the fill of both the determinate and indeterminate progress circle continues to spin clockwise.

Changelog#


DateNumberNotes
Apr 24, 20206.0.0
  • "Circle loader" has been renamed to "progress circle"
Apr 18, 20195.0.0
  • This component is now individually versioned (individual versions of existing components start at 5.0.0)

Design checklist#


N/A

All interactive states

Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).

All color themes

Works properly across all four color themes (lightest, light, dark, darkest).

All platform scales

Includes a desktop scale (UWP, macOS, web desktop) and a mobile scale (iOS, Android, web mobile).

Accessible use of color

Color is not used as the only visual means of conveying information (WCAG 2.0 1.4.1).

N/A

Accessible contrast for text

Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).

Accessible contrast for UI components

Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).

N/A

Content design

UI language and information design considerations have been incorporated into component design.

Defined options

Includes relevant options (variant, style, size, orientation, optional iconography, decorations, selection, error state, etc.)

N/A

Defined behaviors

Includes guidelines for keyboard focus, layout (wrapping, truncation, overflow), animation, interactions, etc.

Usage guidelines

Includes a list of dos and don'ts that highlight best practices and common mistakes.

N/A

Writing guidelines

Includes content standards or usage guidelines for how to write or format in-product content for the component.

Internationalization guidelines

Works properly across various locales and includes guidelines for bi-directionality (RTL).

N/A

Keyboard interactions

Follows WCAG 2.0 standards for keyboard accessibility guidelines and includes a description of the keyboard interactions.

Design tokens

All design attributes (color, typography, layout, animation, etc.) are available as design tokens.

N/A

UI kit

Includes a downloadable XD file that shows multiple options, states, color themes, and platform scales.

Generated UI kit

Includes a downloadable XD file, generated by code using design tokens defined in Spectrum DNA, and shows multiple options, states, color themes, and platform scales.

In Spectrum for Adobe XD plugin

Component is included in the Spectrum for Adobe XD plugin.