Skip to content

Pager

alpha

Sequential navigation between content pages—links to the previous and next page at the end of an article, with each destination’s title.

Navigation · 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.

Previous and next

html

When to use

  • The content has an intended reading order, like a guide, a tutorial, or a chapter.
  • When people finish a page, moving on to the next one is the natural step.
  • You want to show where each side leads, not just an arrow.

When not to use

  • It’s a dataset split into numbered pages → pagination.
  • There’s no real order between the pages → sidebar or toc.

Do

  • Show the destination’s title, not just “Next.”
  • On the first or last page, show only one side. Don’t invent destinations.

Don’t

  • Don’t use it when the order is arbitrary. It promises a sequence that doesn’t exist.

TaishoDS Core

Doesn’t need JavaScript—it’s markup and CSS.

Two <a> links, previous and next.

From the CDN, without a build, load taisho.pager.css along with taisho.base.css. Also load:

  • taisho.icon.css

For how Core works in general, see Behavior.

Accessibility

  • It goes in a <nav> with an aria-label. The controls are links (<a href>) whose accessible name is their full text (direction and page title).

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.