Accessibility in EJ2 TypeScript Button group control
24 Jan 20243 minutes to read
The Button group 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 Button group 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 | |
| Accessibility Checker Validation | |
| Axe-core Accessibility Validation | |
- All features of the component meet the requirement.
- Some features of the component do not meet the requirement.
- The component does not meet the requirement.Keyboard interaction
The Button group 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 Button group component.
Normal behavior
| Press | To do this |
|---|---|
| Tab | Focuses the next button in the ButtonGroup. |
| Enter/Space | Activates the focussed button in the ButtonGroup. |
Checkbox behavior
| Press | To do this |
|---|---|
| Tab | Focuses the next button in the ButtonGroup. |
| Space | Activates the focussed button in the ButtonGroup. |
Radiobutton behavior
| Press | To do this |
|---|---|
| Tab | Focuses the active button in the ButtonGroup. |
| Right | Activates next/previous button in the ButtonGroup. |
Ensuring accessibility
The Button group component’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Button group component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Button group component with accessibility tools.