New to Telerik UI for Blazor? Download free 30-day trial

Blazor TextBox Accessibility

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

The TextBox 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.

No role attribute is implemented as the html input type="text" element is sufficient for definining the purpose of the component.

Selector Attribute Usage
.k-input-inner role=textbox or nodeName=input 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-invalid=true The attribute is rendered only when the TextBox 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 TextBox is disabled.

Resources

WAI-ARIA Specification for the TextBox

Section 508

The TextBox is fully compliant with the Section 508 requirements.

Testing

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

Environment Tool
Firefox NVDA
Chrome JAWS
Microsoft Edge JAWS

See Also

In this article