Accessibility Standards Compliance
This article lists the accessibility compliance of the Kendo UI for Angular components.
Accessibility Conformance Report
The Accessibility Conformance Report (ACR) is a document that explains how information and communication technology products such as software, hardware, electronic content, and support documentation conform to leading global accessibility standards. Kendo UI for Angular provides an ACR through the Voluntary Product Accessibility Template (VPAT®).
Download the latest version of the Kendo UI for Angular Accessibility Conformance Report.
Compliance Table
The table below specifies the level of WCAG 2.2 compliance of each Kendo Angular component.
- The Keyboard Navigation column links to component-specific online demos or keyboard shortcut lists. For general information on how the keyboard support works, see the Keyboard Navigation section.
- The Accessibility Documentation column links to component-specific details and information about WAI-ARIA attributes.
- For information about Section 508 of the US Rehabilitation Act, the European Accessibility Act in the EU, or any other national accessibility legislation, see section Legal and Technical Compliance.
Also check the notes below the table.
The following packages provide methods and directives which delivers specific functionalities (exporting and saving files, formatting, animations, etc.). The components do not require keyboard navigation or accessibility support.
| Component | WCAG 2.2 | Keyboard Navigation | Accessibility Documentation |
|---|---|---|---|
| Data Query | N/A | N/A | N/A |
| Date Math | N/A | N/A | N/A |
| Drag and Drop | N/A | N/A | N/A |
| Drawing | N/A | N/A | N/A |
| Excel Export | N/A | N/A | N/A |
| File Saver | N/A | N/A | N/A |
| PDF Export | N/A | N/A | N/A |
| Ripple | N/A | N/A | N/A |
| Typography | N/A | N/A | N/A |
Special Considerations
-
The components that represent or directly extend a native HTML element (for example Button, CheckBox) do not require additional accessibility functionality to provide their respective level of compliance.
-
Components that are built using other components and/or native HTML elements that are fully accessible (for example, Card, AppBar, Pager) achieve their respective level of compliance through their building blocks.
-
Components that do not provide end-user interaction and serve only as visual representation of a specific state, value, actions, and others (for example, Icons and ProgressBars) are neither focusable, nor navigable. Adding descriptive labels, WAI-ARIA attributes, or a
tabindexto such components, necessitated by a specific use case, is in the hands of the developer. -
Assistive technologies treat components like the various Gauges as images. To make them accessible, add a descriptive label or an alternative representation of the data. For example, a Gauge may be represented by a NumericTextBox or label.
Accessibility Compliance Notes
The information in the compliance table above is subject to the following considerations:
- All components implement the required WAI-ARIA attributes without the need for any extra configuration. Some components may provide parameters that render additional optional WAI-ARIA attributes, for example,
aria-labeloraria-describedby. - The compliance levels are achievable with the Default Ocean Blue A11y theme swatch or any other custom theme swatch that provides the minimum required color contrast.
- The accessibility and compliance of some components may depend on the enabled features. In such cases, the compliance table information is based on the default component configuration.
- Component templates introduce custom markup that may not be accessible. Test any modifications to ensure the web content still meets the desired level of accessibility compliance. Be mindful of components that work with user input such as images, text, or HTML content.
- Due to the complexity of some components, there are scenarios that are not covered by the WAI-ARIA specification.