Blazor DateInput Accessibility
Out of the box, the Telerik UI for Blazor DateInput provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
The DateInput 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 |
|---|---|---|
.k-input-inner |
role=textbox or nodeName=input
|
The element should either be an <input type="text"> element or should have role="textbox" assigned. |
label for or aria-label or aria-labelledby
|
The input needs an accessible name to be assigned to it. | |
readonly=readonly or aria-readonly=true
|
Attribute is rendered only when the DateInput is readonly. | |
tabindex=0 |
The element should be focusable. | |
.k-disabled .k-input-inner |
disabled=disabled or aria-disabled=true
|
Attribute is rendered only when the DateInput is disabled. |
Resources
ARIA practices Date Picker Dialog Example
Section 508
The DateInput is fully compliant with the Section 508 requirements.
Testing
The DateInput 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 DateInput has been tested with the following screen readers and browsers combinations:
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |