<div class="cap-steps" data-variant="inline" id="steps-inline">
<ol class="cap-steps-list" aria-label="Reminder sequence, 5 steps">
<li class="cap-step"><span class="cap-pill" data-tone="info">Email, day 0</span></li>
<li class="cap-step"><span class="cap-pill" data-tone="info">Email, day 3</span></li>
<li class="cap-step"><span class="cap-pill" data-variant="outline">Retry, day 5</span></li>
<li class="cap-step"><span class="cap-pill" data-tone="info">Email, day 7</span></li>
<li class="cap-step"><span class="cap-pill" data-tone="info">Email, day 14</span></li>
</ol>
</div>
Ordered: one row per step with what it says beside it
<div class="cap-steps" data-variant="ordered" id="steps-ordered">
<ol class="cap-steps-list" aria-label="What happens to a failed payment">
<li class="cap-step"><span class="cap-step-number" aria-hidden="true">01</span><span class="cap-step-name">The payment fails and the first reminder goes out</span><span class="cap-step-meta">Day 0</span></li>
<li class="cap-step"><span class="cap-step-number" aria-hidden="true">02</span><span class="cap-step-name">The card is tried again</span><span class="cap-step-meta">Day 3</span></li>
<li class="cap-step"><span class="cap-step-number" aria-hidden="true">03</span><span class="cap-step-name">A last reminder, with a link to update the card</span><span class="cap-step-meta">Day 7</span></li>
</ol>
</div>
API reference
Parts and data attributes
Class
Is
.cap-step
its own class
.cap-step-dot
its own class
.cap-step-meta
its own class
.cap-step-name
its own class
.cap-step-number
its own class
.cap-steps
the root
.cap-steps-counter
a part
.cap-steps-heading
a part
.cap-steps-list
a part
Attribute
Values
data-state
complete
data-variant
inlineorderedstations
State
Read from
[aria-current="step"]
an attribute
Accessibility
Nothing to operate: it is text. Tab passes it by.
ol with aria-label="Steps"; each step's state in words as well as in the bar.
Forced colors: the done and current bars are drawn in Highlight, and the tick in CanvasText.