• What is KendoReact
  • Getting Started
  • Components
    • Animation
    • Barcodes
    • Buttons
    • Charts
    • Common Utilitiesupdated
    • Conversational UI
    • Data Gridupdated
    • Data Query
    • Data Tools
    • Date Inputsupdated
    • Date Math
    • Dialogs
    • Drawing
    • Dropdownsupdated
    • Editor
    • Excel Export
    • File Saver
    • Form
    • Gantt
    • Gauges
    • Indicators
    • Inputsupdated
    • Labels
    • Layoutupdated
    • ListBox
    • ListView
    • Map
    • Notification
    • PDF Processing
    • PDFViewer
    • PivotGrid
    • Popup
    • Progress Bars
    • Ripple
    • Scheduler
    • ScrollView
    • Sortable
    • Spreadsheetnew
    • TaskBoard
    • Tooltips
    • TreeList
    • TreeView
    • Upload
  • Sample Applications
  • Styling & Themes
  • Common Features
  • Project Setup
  • Knowledge Base
  • Changelog
  • Updates
  • Troubleshooting

Chip Accessibility

Out of the box, the Kendo React 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.1 AA standards](https://www.w3.org/TR/WCAG21/) 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.


The following table lists the selectors, attributes, and behavior patterns supported by the Chip component:

*:not(.k-chip-list) > .k-chiprole=buttonAnnounces that a chip is an optional inner component within the Chip list.
*:not(.k-chip-list) > .k-chip.k-selectedaria-pressed=trueAnnounces that the Chip has been selected.
*:not(.k-chip-list) > .k-chip:not(.k-selected)aria-pressed=falseAnnounces that the Chip has not benn selected.


WAI-ARIA Authoring Practices: Button Pattern

Section 508

The Chip is fully compliant with the Section 508 requirements.


The Chip has been extensively tested automatically with static code analyzers and manually with the most popular screen readers.

To report any accessibility issues, contact the team through the Telerik Support System.

Screen Readers

The following table lists the screen readers supported by the Chip:

Microsoft EdgeJAWS

See Also