Accessibility in Blazor Pager Component
28 Mar 20243 minutes to read
The Blazor Pager component followed the accessibility guidelines and standards, including ADA, Section 508, WCAG 2.2 standards, and WCAG roles that are commonly used to evaluate accessibility.
The accessibility compliance for the Blazor Pager component is outlined below.
Accessibility Criteria | Compatibility |
---|---|
WCAG 2.2 Support | |
Section 508 Support | |
Screen Reader Support | |
Right-To-Left Support | |
Color Contrast | |
Mobile Device Support | |
Keyboard Navigation Support | |
Axe-core Accessibility Validation |
WAI-ARIA
The Blazor Pager component followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Blazor Pager component:
- pager (role)
- button (role)
- navigation(role)
- aria-label (Attribute)
Keyboard navigation
The Blazor Pager component followed the keyboard interaction guideline, making it easy for people who use assistive technologies (AT) and those who completely rely on keyboard navigation. The following keyboard shortcuts are supported by the Blazor Pager component.
Interaction Keys | Description |
---|---|
Page down / Right arrow | Navigates to the next page. |
Page up / Left arrow | Navigates to the previous page. |
Enter / Space | Select the currently focused page. |
Tab | Focus on the next pager item. |
Shift + Tab | Focus on the previous pager item. |
Home | Navigates to the first page. |
End | Navigates to the last page. |
Alt + Page up | Navigates to the previous pager. |
Alt + Page down | Navigates to the next pager. |
Ensuring accessibility
The Blazor Pager component’s accessibility levels are ensured through an axe-core with playwright tests.
The accessibility compliance of the Blazor Pager component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Blazor Pager component with accessibility tools.