Blazor NumericTextBox Accessibility
The Telerik UI for Blazor NumericTextBox component is WCAG 2.1 AA and Section 508 compliant. The component also follows the WAI-ARIA best practices for implementing the keyboard navigation for its component role, and is tested against the popular screen readers.
Wai-Aria
| Selector | Attribute | Usage |
|---|---|---|
| .k-input-inner | role=spinbutton |
Announces the spinbutton capabilities of the numerictextbox. |
label for or aria-label or aria-labelledby
|
The input needs an accessible name to be assigned to it. | |
aria-valuemnow |
Announces the value for the component. | |
aria-valuemin |
Announces the minimum value allowed for the component. | |
aria-valuemax |
Announces the maximum value allowed for the component. | |
aria-invalid=true |
Attribute is rendered only when the numerictextbox is in form and announces the valid state of the component. | |
| .k-disabled .k-input-inner |
disabled=disabled or aria-disabled=true
|
Attribute is rendered only when the numerictextbox is disabled. |
| .k-spin-button>.k-button |
role=button or nodeName=button
|
Announces the spinbutton capabilities of the numerictextbox. |
aria-label |
Button element must have discernible text. |
Resources
Section 508
The NumericTextBox is compliant with the Section 508 requirements
Testing
The component has been extensively tested automatically with static code analyzers and manually with the most popular screen readers.
Any Accessibility Issues could be reported in Telerik Support System.
Screen Readers
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |