Blazor TextArea Accessibility
Out of the box, the Telerik UI for Blazor TextArea provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
The TextArea is compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AAA 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.
| Selector | Attribute | Usage |
|---|---|---|
.k-input-inner |
role=textbox or nodeName=textarea
|
Describes the role of the component. |
label for or aria-label or aria-labelledby
|
The input requires an accessible name that will be assigned to it. | |
aria-multiline=true |
Announces the multi-line behavior of the TextArea. | |
aria-invalid=true |
The attribute is rendered only when the TextArea is in a form and announces the valid state of the component. | |
.k-disabled .k-input-inner |
disabled=disabled or aria-disabled=true
|
The attribute is rendered only when the TextArea is disabled. |
Resources
WAI-ARIA Specification for the TextBox
Section 508
The TextArea is fully compliant with the Section 508 requirements.
Testing
The TextArea 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 TextArea has been tested with the following screen readers and browsers combinations:
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |