Blazor Chip Accessibility
Out of the box, the Telerik UI for Blazor Chip provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
The Chip is compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standards 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.
| Selector | Attribute | Usage |
|---|---|---|
*:not(.k-chip-list) > .k-chip | role=button | Announces that a chip is an optional inner component within the Chip list. |
*:not(.k-chip-list) > .k-chip.k-selected | aria-pressed=true | Announces that the Chip has been selected. |
*:not(.k-chip-list) > .k-chip:not(.k-selected) | aria-pressed=false | Announces that the Chip has not benn selected. |
Resources
WAI-ARIA Authoring Practices: Button Pattern
Section 508
The Chip is fully compliant with the Section 508 requirements.
Testing
The Chip 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 Chip has been tested with the following screen readers and browsers combinations:
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |
Keyboard Navigation
For details on how the Chip keyboard navigation works, refer to the Blazor Chip Accessibility and Keyboard Navigation Demo.