Editor Accessibility

The Editor is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.

For more information, refer to:

Kendo UI for jQuery Kendoka image

The Accessibility is part of Kendo UI for jQuery, a professional grade UI library with 110+ components for building modern and feature-rich applications. To try it out sign up for a free 30-day trial.

Out of the box, the Kendo UI for jQuery Editor provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.

The Editor is compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standards](https://www.w3.org/TR/WCAG22/) 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.

The Editor component has two distinctive modes - one with <textarea> and an <iframe> containing an HTML document and another one with only a contenteditable <div> (Inline Editor). The inline mode of the Editor does not require any particular ARIA attributes to be present in the widget.

Editor with textarea

Selector Attribute Usage
.k-iframe tabindex=0 The element must be part of the page tabsequence.
label for or aria-label or aria-labelledby The component focusable element needs an accessible name to be assigned to it.

Editor with contenteditable div

When in its inline mode (with a contenteditable div element), the editor does not represent a form input. Hence, no additional attributes are required in that scenario.

Resources

WAI-ARIA specification for textbox

Section 508

The Editor is fully compliant with the Section 508 requirements.

Testing

The Editor 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 Editor has been tested with the following screen readers and browsers combinations:

Environment Tool
Firefox NVDA
Chrome JAWS
Microsoft Edge JAWS

Automated Testing

The Editor has been tested with axe-core.

Test Example

A live test example of the Editor component could be found here: https://demos.telerik.com/kendo-ui/accessibility/editor

See Also

In this article