Blazor Editor Accessibility
Out of the box, the Telerik UI for Blazor 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.
| Selector | Attribute | Usage |
|---|---|---|
div[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. |
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 |