Accessibility in Angular Chips component
24 Jan 20243 minutes to read
The Chips 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 Chips 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.WAI-ARIA attributes
The Chips component followed the WAI-ARIA patterns to meet the accessibility. The following ARIA attributes are used in the Chips component:
| Attributes | Purpose |
|---|---|
role=listbox |
Indicates the ChipList component wrapper element as listbox. |
role=option |
Used to convey a significant and contextual message to the user(ChipList). |
role=button |
Used to convey a significant and contextual message to the user(Single Chip). |
aria-label |
Provides an accessible name for the Chip. |
aria-selected |
Indicates the element is selected. |
aria-disabled |
Indicates element is perceivable but disabled. |
aria-multiselectable |
Indicates multiple items to be selected. |
Keyboard interaction
The Chips 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 Chips component.
| Keyboard shortcuts | Actions |
|---|---|
| Enter / Space | Selects the targeted chip from the ChipList/ChipCollection. |
| Delete / Backspace | Deletes the targeted chip from the ChipList/ChipCollection. |
Ensuring accessibility
The Chips component’s accessibility levels are ensured through an accessibility-checker and axe-core software tools during automated testing.
The accessibility compliance of the Chips component is shown in the following sample. Open the sample in a new window to evaluate the accessibility of the Chips component with accessibility tools.