In addition,as pages likely have more than one such navigation section,it’s advisable to provide a descriptive aria-labelfor 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".
Pagination links are customizable for different circumstances. Use .disabledfor links that appear un-clickable and .activeto indicate the current page.
While the .disabledclass uses pointer-events:noneto tryto disable the link functionality of <a>s,that CSS property is not yet standardized and doesn’t account for keyboard navigation. As such,you should always add tabindex="-1"on disabled links and use custom JavaScript to fully disable their functionality.
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.
In addition,as pages likely have more than one such navigation section,it’s advisable to provide a descriptive aria-labelfor 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".
Looking to use an icon or symbol in place of text for some pagination links? Be sure to provide proper screen reader support with ariaattributes.
Fancy larger or smaller pagination? Add .pagination-lgor .pagination-smfor additional sizes.