Skip to content

Progress

A determinate (with data-ts-value) or indeterminate (is-indeterminate, continuous animation) progress bar that shows how far along a task is. It has sizes, color variants, and an aria-label as its accessible name. It can also be split into segments (is-steps, is-stacked) for quotas, or drawn as a ring (shape-circle).

Feedback and status · TaishoDS Core, in plain HTML.

Examples

One working example per case. Each example is the HTML of its preview—copy it as is, and with Core’s CSS and JS loaded, it looks and works the same.

Bar with label

html

Success variant

html

Indeterminate

html

Steps

html

Segments

html

Circular with value

72%
html

Class reference

Every value of each modifier, with its HTML ready to copy.

Size

Bar thickness: sm, md, or lg.

html

Variant

Bar color: default or a status color (success, danger, brand…).

html

Stepped

is-steps splits the bar into N equal steps; is-filled marks the filled ones (3 of 5 seats).

html

Segments

is-stacked shows several values in different colors on a single bar (used and reserved).

html

Shape

shape-circle shows progress as a ring; size sets the diameter.

60%
html

States

is-indeterminate for unknown progress (continuous animation).

html

Combinations

Size and color combined.

html

When to use

  • You know how much is left and can express it as a percentage, like an upload, an import, or step 3 of 5.
  • The wait is long, and seeing progress keeps the user from giving up.
  • You want to show what portion of something is complete (a quota, a checklist).
  • It’s a quota in segments. Use is-steps for “3 of 5 seats” and is-stacked for a plan’s used and reserved amounts.
  • The space is small or square (a cell, a card). Use shape-circle.

When not to use

  • The wait is short and you don’t know how much is left → spinner.
  • It’s subtle activity inside text or a button → loading-dots.
  • Content that will take up space is loading → skeleton.

Do

  • Give it an aria-label. It’s the bar’s accessible name.
  • If you can’t calculate real progress, use is-indeterminate instead of making up a number.
  • With is-stacked, show a color legend next to it. Color alone isn’t enough to tell the segments apart.

Don’t

  • Don’t fake progress. A bar that jumps to 90% and stays there is worse than none.
  • Don’t use a bar for a half-second wait. It flickers and gets annoying.

TaishoDS Core

Needs Core’s JS, which hooks in through data-ts-* attributes.

The fill width is a continuous value. The stylesheet reads it from --ts-progress-value (0% by default), and Core writes that variable. Until Core runs, the bar looks empty instead of showing its value.

Core hooks into it through these attributes. They go in the markup, and there’s nothing to initialize.

  • data-ts-value

What it does: Write data-ts-value="40" (a percentage) on each [data-progress-fill], including stacked segments. Core copies it to --ts-progress-value on init and whenever the attribute changes. The indeterminate bar doesn’t take the attribute. There’s no interaction—it only sets the value at rest.

From the CDN, without a build, load taisho.progress.css along with taisho.base.css. That file is all you need.

For how Core works in general, see Behavior.

Accessibility

  • Uses role="progressbar" with aria-valuenow/min/max (omitted in indeterminate mode).
  • label provides the bar’s accessible name.
  • With is-steps or is-stacked, it carries aria-valuetext (“3 of 5”, “Used 40, Reserved 20 of 100”), so the screen reader announces the segments, not just a number. With shape-circle, the SVG is decorative (aria-hidden), and the visible percentage repeats the role="progressbar" value.
  • It isn’t interactive (no focus or keyboard). With prefers-reduced-motion, the arc advances instantly (the global duration tokens). The indeterminate spin keeps going, like the Spinner, because it’s the loading signal. The indeterminate bar stands still as a fixed stretch of the track (it still reads as indeterminate, with no aria-valuenow).

Verification

What was actually tested. Anything that wasn’t tested says so—we’d rather say “not verified” than claim too much.

  • axe WCAG 2.2 A + AA in a real browser, in light and dark mode, before every release.
  • keyboard Adds no keys of its own—it uses the browser’s native behavior.
  • screen reader Not verified with a screen reader. Test it in your own combination of components, not just here, where each one appears alone and on its happy path.