• What is KendoReact
  • Getting Started
  • Server Components
  • Components
  • Sample Applications
  • Styling & Themes
  • Common Features
  • Project Setup
  • Knowledge Base
  • Changelog
  • Updates
  • Troubleshooting

Pager Accessibility

Out of the box, the Kendo React Pager provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.

The Pager is compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standards and Section 508 requirements, follows the Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA) best practices for implementing the keyboard navigation for its component role, provides options for managing its focus and is tested against the most popular screen readers.

WAI-ARIA

This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.

The PageSize select must be implemented either as a DropDownList component with no filtering or through a native <select> element.

The Page select, which is present for mobile devices and smaller screens with kimited space for page links, must be a native <select> element.

SelectorAttributeUsage
.k-pagerrole=applicationIndicates that the pager element has its own keyboard navigation implemented.
aria-roledescription=pagerClarifies the role of the Pager.
aria-keyshortcuts=Enter ArrowRight ArrowLeftAnnounces the available keyboard shortcuts while the pager element is focused.
aria-labelAnnounces the currently selected page and the number of available pages.
aria-controlsPoints to the id of the element that is being controlled, for example, a Grid.
.k-pager-navrole=button or nodeName=buttonSpecifies the role of the element.
aria-disabled=trueThe attribute is present when the the Arrow button is disabled, for example, present on the Previous button when the current page is the first one.
titleSpecifies the purpose of each button.
.k-pager-numbers>.k-linkrole=button or nodeName=buttonSpecifies the role of the element.
aria-label or titleSpecifies the purpose of each link, for example, Page 6.
aria-current=pageThe attribute must be present on the currently selected page element.
.k-pager-sizes>.k-dropdownlistaria-labelThe element requires an aria-label to specify its purpose.
.k-pager-numbers-wrap>.k-dropdownaria-labelThe element requires an aria-label to specify its purpose.
.k-pager-input>.k-input>.k-input-inneraria-labelThe element requires an aria-label to specify its purpose.

Resources

WAI-ARIA Specification for Navigation

Accessibility Style Guide: Pagination

Section 508

The Pager is fully compliant with the Section 508 requirements.

Testing

The Pager has been extensively tested automatically with axe-core and manually with the most popular screen readers.

To report any accessibility issues, contact the team through the Telerik Support System.

Screen Readers

The Pager has been tested with the following screen readers and browsers combinations:

EnvironmentTool
FirefoxNVDA
ChromeJAWS
Microsoft EdgeJAWS

See Also