Out of the box, the Telerik UI for ASP.NET MVC 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.
This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
Selector Attribute Usagediv[contenteditable='true'] role=textbox Specifies the role of the component as text input. label for or aria-label or aria-labelledby The component focusable element needs an accessible name to be assigned to it. .k-editor.k-readonly div[contenteditable=false] aria-readonly=true Attribute is rendered only when the Editor is readonly. Resources
WAI-ARIA specification for textbox
Section 508The Editor is fully compliant with the Section 508 requirements.
TestingThe Editor has been extensively tested automatically with axe-core and manually with the most popular screen readers.
Screen ReadersTo report any accessibility issues, contact the team through the Telerik Support System.
The Editor has been tested with the following screen readers and browsers combinations:
Environment Tool Firefox NVDA Chrome JAWS Microsoft Edge JAWS Test ExampleTo test the Editor component, refer to the Editor Accessibility Demo.
Keyboard NavigationFor details on how the Editor keyboard navigation works, refer to the Editor Keyboard Navigation article.
See AlsoRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4