New to Kendo UI for Vue? Start a free 30-day trial

Accessibility Support

How the Kendo UI for Vue Team Approaches Accessibility

When implementing any Kendo UI for Vue component, the Kendo UI for Vue team follows the WAI-ARIA specification to ensure that the right foundation for the accessibility of each component is laid. From there, the team employs automated testing across the Kendo UI for Vue library through the Compliance Sheriff tool, which the team has found to be the tool that works best for automated accessibility testing of the product. Each component also goes through manual testing, which includes testing the components with various screen readers and testing out other aspects of accessibility such as keyboard navigation.

Due to the complexity of some of the components in the Kendo UI for Vue UI library, the team sometimes runs into scenarios not covered by the WAI-ARIA specification. In those cases, they tap into the web development accessibility know-how of the rest of the Progress organization, including feedback from accessibility-minded users, for expertise and feedback based on 10 years of creating web component libraries. This knowledge-sharing across internal teams and clients helps the team ensure that Kendo UI for Vue can reach a certain level of accessibility compliance even with its most advanced components.

The following table lists the accessibility compliance levels and keyboard navigation support provided by the Kendo UI for Vue UI components.

ComponentSection 508WCAG 2.0Keyboard Navigation
AutoCompleteYesAAYes
CalendarYesAAAYes
DropDownListYesAAYes
DateInputYesAAAYes
DatePickerYesAAAYes
ComboboxYesAAYes
DialogYesAAAYes
InputYesAAAYes
GridYesAAAYes
MaskedTextBoxYesAAAYes1
NumericTextBoxYesAAAYes
MultiSelectYesAAAYes
WindowYesAAAYes

1 - The component extends a native HTML element and does not require additional accessibility functionality to provide this level of compliance. 2 - The component is built by using other components that are fully accessible. Combining their accessibility with the built-in browser keyboard navigation support allows the component to achieve this level of accessibility.

In this article

Not finding the help you need?