...
Description
Progress indicators express an unspecified wait time or show that an operation is currently ongoing. They display the current completed completion ratio of a process or action.
...
Types
Linear & Circular
LUX offers two visually distinct variations of progress indicatorsan operation or a visual animation that conveys an unspecified wait time.
...
Types
There are two visually-distinct types of progress indicator: linear and circular progress indicators.
Only one type should represent each kind of activity in an application. For example, if a refresh action displays a circular indicator on one screen, that same action shouldn’t use a linear indicator elsewhere in the application.
Type | Usage | Image |
|---|---|---|
Linear | Linear progress indicators are often referred to as a Progress bar. Determinate indicators are for operations |
where the |
duration of the process is known. |
The indicator |
increases in width from 0 to 100% of the track, in sync with the process’s progress. Indeterminate indicators are for operations |
where the |
duration of the process is not known. |
The indicator is continuously animated along the track until the process is complete. They can be applied to the entire page, large containers, and to form elements. |
|
Circular | Circular progress indicators are often referred to as a Progress spinner. Determinate indicators are for operations |
where the length of the process is known. They fill the invisible, circular track with |
color, as the indicator moves from 0 to 360 degrees. Indeterminate indicators are for operations |
where the |
duration of the process is not known. They continuously animate along the invisible circular track until the process is complete. They can be applied directly to |
an element, such as a button or card. |
|
Usage &
...
Behavior
Progress indicators inform users about the status of ongoing processes, such as loading a page, submitting a form, or saving updates. They communicate an applications application's state and indicate available actions, such as whether users can navigate away from the current screen.
A linear indicator can also be integrated into form elements, such as file uploads, to express a connection between a background ongoing process and individual items. They are ideal for long determinate activities (over 10 seconds).
A circular indicator can be integrated into a button or actionable icon to express a connection between an interaction and a specific item. They are typically used to express when an interaction, such as clicking a button again, is not available. They should be used for short, indeterminate activities (between 2-5 seconds).
General guidelines
Structure
Linear progress Progress indicators are composed consist of two required elements:
...
A track. The fixed area which the indicator bar
...
travels along. For circular indicators, the track is invisible.
...
...
The
...
indicator bar. The animated colored area which moves along the
...
track.
...
Placement and Positioning
The placement of a progress indicator can indicate the scope of a process. Linear progress indicators should only be placed at the top or in the center of a container or component. For example:
|
|
|
 |
|
|
|
|  |
When integrated to form elements ( |
...
such as file upload), it may be placed to the right of the |
...
field |
...
it relates to. It may also be placed underneath the field depending on available |
...
space or responsive design. |
...
 |
A circular progress indicator |
...
can be placed |
...
: |
...
|
...
|
...
|
...
|
...
|
...
|
...
| 
|
Default State
Determinate linear progress indicators may be hidden or shown in their empty state by default
...
. When shown, they can indicate that an action may be a lengthy operation.
...
For example,
...
a form
...
submission which is expected to take several minutes to complete should show the linear progress indicator in its empty state to set
...
the user’s expectations.
Indeterminate linear progress indicators should be hidden by default and only appear
...
once active.
...
On completion, the linear progress indicator should
...
be hidden again, and in most cases replaced by the content that was loaded or a post-completion message.
Circular progress indicators should be hidden by default and only appear
...
once active.
...
On completion, the circular progress indicator should
...
be hidden again, and in most cases replaced by the content that was loaded. In the case of integration with a component
...
such as a button, the
...
component is returned to
...
its default state.
States
There are none of the traditional Common states such as hover, active, focused and errorstates for linear do not apply to progress indicators, as user interaction is not applicablepossible.
Linear
State | Determinate | Indeterminate |
|---|---|---|
Empty |  | |
Partially complete |  |  |
Complete |  |
NA | ||
Disabled | | |
Circular
State | Determinate | Indeterminate |
|---|---|---|
Empty |  | |
Partially complete |  |  |
Complete |  |
NA | ||
Disabled | | |
Interaction
Progress indicators do not support user interaction, they . They are solely used to provide a visual status indicator. The exception to this is where circular progress indicators are integrated into a button with a built-in cancel operation.
Best practices
...
Don’t stop a progress indicator - A progress indicator makes users develop an expectation for how fast the action is being processed. As a result, any unexpected freezes will be noticed and will impact user satisfaction. The worst possible case is when a progress indicator approaches 99% and suddenly stops. Most users will be frustrated by this behaviour because it makes them think the app is frozen. You can disguise small delays in your progress indicator by moving it instantly and steadily.
...
Use:
A linear indicator can be integrated into form elements, such as file uploads, to express a connection between a background ongoing process and individual items. They are ideal for long determinate activities (over 10 seconds).
Don’t Use:
When the action lasts less than 1 second.
General:
Consider adding informative text to tell the user what is happening or
...
explain why they are waiting.
...
Provide a general time estimate for time-consuming tasks
...
. Don’t try to be exact
...
: This might take five
...
minutes can be enough
...
to encourage users
...
to wait
...
.
Make sure that long operations offer the ability to cancel during the process.
...
Avoid using vertical linear indicators - A linear progress indicator is instinctively easier to visualize when oriented horizontally. Avoid orienting it vertically to reduce the cognitive load required for users.
Accessibility Compliance
Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.
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 ARIA progressbar role.
Responsive design
Verint products should support all devices down to the common tablet size (960px width). For general guidelines, see Fundamentals - Responsive design.
Progress indicator placement and positioning is fixed, relative to their parent container, regardless of screen width or height.
Linear progress indicators are fixed height and their width can be either fixed or dynamic. Max width will not exceed its parent container width.
Circular progress indicators are are fixed height and width in one of 3 available sizes (S, M, L). Original sizing should be maintained unless it exceeds the size of its parent container. The next size below should be displayed in that scenario.
Design
Zeplin link | Screen thumbnail |
|---|
<< Add links >>
<< Add screenshots >>
...
Code
| Html macro | ||
|---|---|---|
| ||
<link rel="stylesheet" href="https://ux.verint.com/fonts/css/verint_lux.css">
<link rel="stylesheet" href="https://ux.verint.com/bootstrap-4.0.0/dist/css/bootstrap.css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
<script src="https://ux.verint.com/bootstrap-4.0.0/dist/js/bootstrap.bundle.js"></script>
<script src="https://ux.verint.com/bootstrap-4.0.0/dist/other/bootstrap-tooltip-custom-class.js"></script>
<script src="https://ux.verint.com/bootstrap-4.0.0/dist/other/accessibility.js"></script>
<script src="https://ux.verint.com/bootstrap-4.0.0/dist/other/prism.min.js"></script>
<link rel="stylesheet" href="https://ux.verint.com/bootstrap-4.0.0/dist/other/prism-coy.min.css">
<div class="card">
<div class="card-header">Linear Progress Indicator <button id="toggleMarkup" type="button" class="btn btn-sm btn-outline-primary btn btn-fixed-width float-right m-0" onclick="$('pre' ).toggle()">Toggle Markup</button></div>
<div class="card-body">
<form>
<div class="form-group row">
<label for="inputKey" class="col-lg-2 col-form-label col-form-label-sm">Determinate</label>
<div class="col-lg-4">
<div class="progress">
<div class="progress-bar" role="progressbar" aria-valuenow="0" aria-valuemin="0" aria-valuemax="100"></div>
</div>
</div>
<div class="col-lg-6">
<pre class="language-html"><code><script type="prism-html-markup"><div class="progress">
<div class="progress-bar" role="progressbar" aria-valuenow="0" aria-valuemin="0" aria-valuemax="100"></div>
</div></script></code></pre>
</div>
</div>
<div class="form-group row">
<label for="inputKey" class="col-lg-2 col-form-label col-form-label-sm">Indeterminate</label>
<div class="col-lg-4">
<div class="intermediate-progress-bar animate">
<div class="intermediate-progress-bar-animation" role="progressbar" aria-valuenow="intermediate" aria-valuemin="0" aria-valuemax="100"></div>
</div>
</div>
<div class="col-lg-6">
<pre class="language-html"><code><script type="prism-html-markup"><div class="intermediate-progress-bar animate">
<div class="intermediate-progress-bar-animation" role="progressbar" aria-valuenow="intermediate" aria-valuemin="0" aria-valuemax="100"></div>
</div></script></code></pre>
</div>
</div>
<script>
var currentVal = 0;
function simulateProgress() {
setTimeout(function() {
$(".progress .progress-bar").width(100 - currentVal+"%");
$(".progress .progress-bar").attr("aria-valuenow", currentVal);
currentVal += 1;
if (currentVal <= 100) {
simulateProgress();
}
}, 200)
}
simulateProgress();
</script>
</form>
</div>
</div>
<div class="card">
<div class="card-header">Circular Progress Indicator</div>
<div class="card-body">
<form>
<div class="form-group row">
<label for="inputKey" class="col-lg-2 col-form-label col-form-label-sm">Determinate</label>
<div class="col-lg-4">
<div class="spinner" role="status">
<span class="sr-only">Loading...</span>
</div>
</div>
<div class="col-lg-6">
<pre class="language-html"><code><script type="prism-html-markup"><div class="spinner" role="status">
<span class="sr-only">Loading...</span>
</div></script></code></pre>
</div>
</div>
<div class="form-group row">
<label for="inputKey" class="col-lg-2 col-form-label col-form-label-sm">Indeterminate</label>
<div class="col-lg-4">
<div class="indeterminate-spinner" role="status">
<span class="sr-only">Loading...</span>
</div>
</div>
<div class="col-lg-6">
<pre class="language-html"><code><script type="prism-html-markup"><div class="indeterminate-spinner" role="status">
<span class="sr-only">Loading...</span>
</div></script></code></pre>
</div>
</div>
</form>
</div>
</div> |