Accessibility in EJ2 TypeScript Range navigator control
18 Jan 20242 minutes to read
The Range navigator control 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 Range navigator control 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 | |
| Accessibility Checker Validation | |
| Axe-core Accessibility Validation | |
- All features of the control meet the requirement.
- Some features of the control do not meet the requirement.
- The control does not meet the requirement.WAI-ARIA attributes
The Range navigator control followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Range navigator control:
- region (role)
- aria-label (attribute)
Keyboard interaction
The Range navigator control 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 Range navigator control.
| Press | To do this |
|---|---|
| Tab | Moves the focus to the Range navigator element. |
| Ctrl + P | Prints the Range navigator. |
Ensuring accessibility
The Range navigator control’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Range navigator control is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Range navigator control with accessibility tools.