New to Telerik UI for ASP.NET CoreStart a free 30-day trial

Editor Accessibility

Out of the box, the Telerik UI for ASP.NET Core 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 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

SelectorAttributeUsage
.k-iframetabindex=0The element must be part of the page tabsequence.
label for or aria-label or aria-labelledbyThe component focusable element needs an accessible name to be assigned to it.
.k-editor.k-readonly div[contenteditable=false]aria-readonly=trueAttribute is rendered only when the Editor is readonly.

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:

EnvironmentTool
FirefoxNVDA
ChromeJAWS
Microsoft EdgeJAWS

Test Example

To test the Editor component, refer to the Editor Accessibility Demo.

Keyboard Navigation

For details on how the Editor keyboard navigation works, refer to the Editor Keyboard Navigation article.

See Also