Displays the user's current location within a linear task flow, such as a wizard.
Progress trackers are positioned beneath the page title and above the rest of the content.
All progress trackers require a minimum of 2 steps.
Standard User Progress Trackers are represented with a linear bar and can have a maximum of 6 steps.
Dropdown User Progress Trackers are used when there are more than 6 steps.
Typically, users have the option to navigate backwards in their workflow by clicking on any previous tracker step that is not disabled.
Disabled steps are used when backward navigation is not possible to those steps.
For linear bar trackers, the link-label beneath each step is replaced with a show-hide on smaller breakpoints.
Reverse the direction of a progress tracker for right-to-left languages.
If possible, the first step of a form should explain how many steps will follow. Each step should inform the user about the progress they are making.
Title case, 2-3 words maximum.
Do not combine actions in a label (exception: "Customize & Buy").
If standard labels don't fit the button's purpose, align label with the task the user is attempting.
Please refer to the Dell Technologies branding website, https://brand.delltechnologies.com/faq/#voice, for further information regarding call-to-action labels and usage.
To be determined.
Ensure that overall instructions are visible from every step.
The progressbar role should be used for an element that displays the progress status for a task that consists of several steps.
The progress element, like other form elements, is a component from the operating system rendered directly on the website. Those components are animated in some operating systems, which would violate WCAG 2.0’s 2.2.2 Pause, Stop, Hide success criteria (requires that users are able to disable an animation that starts automatically, lasts more than 5 seconds and is presented in parallel with other content). The animation can be stopped by using custom styling with browser-specific CSS.
Each step should identify progress in relation to the total number of steps (e.g. "Step 1 of 4").
Leverage the h1 page title for disclosing progress (e.g. "Dell Cart - Sign In (Step 2 of 6)").
Make it easy to recognize and skip optional steps, such as purchasing add-ons.
Don't set a time limit to complete the workflow. If a time limit is required (as with auto-logout), then provide a feature for extending the time limit.
Make use of the HTML5 "progress" element.
Save changes as they're made within each step in case progress is lost.
Add an ".sr-only" helper class that is only readable by screen readers (and invisible for all other users).
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A)
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A)