Horizontal Stepper

A stepper is a navigation component that guides users through sequential steps in a process, displaying progress and providing clear direction across tasks.

Overview

Usage

When to use this component?

Stepper components are essential in multi-step processes where clear navigation and progress visualization are crucial. They are ideal for guiding users through forms, checkout processes, and complex workflows, providing a visual representation of which steps have been completed, which are active, and which are yet to be done.

How it works

A stepper component typically displays a sequence of steps, each represented by numbers, icons, or labels. The current step is distinctly highlighted, while completed steps and upcoming steps have different visual markers to clearly delineate progress. Steppers can be oriented either horizontally or vertically and may include additional text labels to offer more context for each step, ensuring users always know their location and what's required next in the process.

Code

<dda-horizontal-stepper
    steps='[{"title":"Step 1","subtitle":"Subtitle 1","description":"Lorem Ipsum&nbsp;is simply dummy text of the printing and typesetting industry."},{"title":"Step 2","subtitle":"Subtitle 2","description":"Lorem Ipsum&nbsp;is simply dummy text of the printing and typesetting industry."},{"title":"Step 3","subtitle":"Subtitle 3","description":"Lorem Ipsum&nbsp;is simply dummy text of the printing and typesetting industry."}]'
    current_step="1"
    custom_class=''
    mode='light'
></dda-horizontal-stepper>

Properties

Property
Description
Type

type

Defines the style of the tab. It can either be text (just the text of the tab) or text-icon (a combination of text and an icon next to the text). Defaults to 'text'.

string

hover_style

Specifies the hover style for the tabs. Options include different background or border styles that change when a tab is hovered over. Defaults to 'dda-tab-default'.

'dda-tab-default' | 'dda-tab-filed' | 'dda-tab-underline' | 'dda-tab-underline-filled'

custom_class

Allows the user to apply custom CSS classes to the tabs container for additional styling. Defaults to an empty string (no custom class).

string

component_mode

Optionally defines a mode for the component ('light' or 'dark'), which could be used for conditional styling or behavior. Defaults to 'light'.

string

button_ids

Specifies an array of button IDs used to identify and manage tab buttons. Useful for targeting specific buttons in scripting or accessibility features.

string

aria_label

Defines an accessible label for the tab buttons, improving accessibility by describing the purpose of the buttons for screen readers.

string

tab_texts

Defines an array of text labels for each tab. These labels are displayed on the tab buttons and help users navigate between different content sections.

string

button_name

Specifies the name attribute for the button element

string

tab_type

Defines tab layout style (e.g., "dda-horizontal-tab", "dda-vertical-tab").

string

Anatomy

Anatomy Options

Complete: Indicates a completed step in the process, typically shown with a checkmark or a specific color to signify completion.

Current: Highlights the step currently in progress or being viewed, providing a visual indication of the active step.

Dashed Lines: Connects steps to indicate progression. Dashed styling suggests steps that are yet to be completed.

Default: Represents steps that are pending, often displayed with a neutral or inactive style to indicate future actions.

Dos and Don'ts

Dos
Don'ts

Clearly label each step to ensure users understand what each part of the process entails.

Use ambiguous or unclear labels that might confuse users about what is expected of them.

Highlight the current step distinctly to help users know exactly where they are in the process.

Make it difficult to distinguish between completed, current, and upcoming steps.

Use visual markers like icons or numbers to indicate progress and guide users through the steps.

Clutter the stepper with excessive details that might overwhelm users.

Provide directional controls if the process requires users to navigate back and forth between steps.

Allow navigation to steps that depend on completion of previous steps without proper validation.

Last updated