Pagination helps users move between a large number of items that are distributed across multiple screens in scenarios where there are too many results to show at once. Pagination is useful for table listings, search results, and directories.
Wherever possible, display the number of individual results available across all pages.
Ensure the clickable elements are large and easy for the user to select the correct option without error.
Clearly indicate the page the user is on by using the active state.
Next and previous controls should be disabled if users can’t move in the respective direction.
Avoid confusing patterns that use double arrows as ‘first’ and ‘last’ options.
Ensure single arrows for previous and next are accompanied by ‘previous’ and ‘next’ labels.
Do: Use button labels
Don't: Use icon buttons without labels
How it works
We use a large block of connected links for our pagination, making links hard to miss and easily scalable—all while providing large hit areas. Pagination is built with list HTML elements so screen readers can announce the number of available links. Use a wrapping <nav> element to identify it as a navigation section to screen readers and other assistive technologies.
In addition, as pages likely have more than one such navigation section, it’s advisable to provide a descriptive aria-label for the <nav> to reflect its purpose. For example, if the pagination component is used to navigate between a set of search results, an appropriate label could be aria-label="Search results pages".
Disabled and active states
Pagination links are customizable for different circumstances. Use .disabled for links that appear un-clickable and .active to indicate the current page.
You can optionally swap out active or disabled anchors for <span>, or omit the anchor in the case of the prev/next arrows, to remove click functionality and prevent keyboard focus while retaining intended styles.
Add .pagination-lg or .pagination-sm for additional sizes.