Pager Accessibility
The Pager is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
The Accessibility is part of Kendo UI for jQuery, a
professional grade UI library with 110+ components for building modern and feature-rich applications. To try it out sign up for a free 30-day trial.
For more information, refer to:
Out of the box, the Kendo UI for jQuery 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](https://www.w3.org/TR/WCAG22/) 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.
| Selector | Attribute | Usage |
|---|---|---|
.k-pager |
role=application |
Indicates that the pager element has its own keyboard navigation implemented. |
aria-roledescription=pager |
Clarifies the role of the Pager. | |
aria-keyshortcuts=Enter ArrowRight ArrowLeft |
Announces the available keyboard shortcuts while the pager element is focused. |
|
aria-label |
Announces the currently selected page and the number of available pages. | |
aria-controls |
Points to the id of the element that is being controlled, for example, a Grid. |
|
.k-pager-nav |
role=button or nodeName=button
|
Specifies the role of the element. |
aria-disabled=true |
The 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. |
|
title |
Specifies the purpose of each button. | |
.k-pager-numbers>.k-link |
role=button or nodeName=button
|
Specifies the role of the element. |
aria-label or title
|
Specifies the purpose of each link, for example, Page 6. |
|
aria-current=page |
The attribute must be present on the currently selected page element. | |
.k-pager-sizes>.k-dropdownlist |
aria-label |
The element requires an aria-label to specify its purpose. |
.k-pager-numbers-wrap>.k-dropdown |
aria-label |
The element requires an aria-label to specify its purpose. |
.k-pager-input>.k-input>.k-input-inner |
aria-label |
The 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:
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |
Automated Testing
The Pager has been tested with axe-core.
Test Example
A live test example of the Pager component could be found here: https://demos.telerik.com/kendo-ui/accessibility/pager