#
#
ARIA Attributes
Since version 7.0.0, Pagy introduced a consistent set of ARIA-compliant attributes across all its helpers.
Pagy provides a customizable aria-label for the root element of its helpers. It is usually a nav element. For
the few helper styles that use a different root element, Pagy adds a role="navigation" attribute.
The default string for the aria-label of the root element is "Page" / "Pages" (translated and pluralized according to the total
number of pages). This is arguably a better description of the navigation content than just "Pagination" (which is also difficult
to translate in certain languages).
Help us with your languages!
Please, check the pagy.aria_label.nav in the locale files
used by your app to ensure correctness in translation and pluralization. If it isn't, please post your translation in the issue linked
within the file. Thank you!
Don't rely on ARIA default with multiple nav elements!
The nav elements are landmark roles, and should be distinctly labeled.
Override the default :aria_labels for multiple navs with distinct values!
<%# Explicitly set the aria_label %>
<%== @pagy.series_nav(aria_label: 'Search result pages') %>Links to the previous and next pages are rendered as "<" and ">" and are aria-labelled as translated
"Previous"and"Next". You can customize both the link text and thearia-labelby editing thepagy.prev,pagy.next,pagy.aria_label.prev, andpagy.aria_label.nextvalues in the locale files.By design, page links do not include an
aria-labelattribute because their text is a simple number (read by screen readers in the user's native language), making an explicit attribute redundant and inefficient.Disabled links include the
aria-disabled="true"attribute.The current page is marked with the
aria-current="page"attribute.The
role="link"attribute is applied to link elements in styles that lack anatag or ahrefattribute.The
role="separator"is applied to the:gap.