OTPInput Accessibility
Out of the box, the Kendo UI for jQuery OTP provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
The OTP 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 defining the purpose of the component.
| Selector | Attribute | Usage |
|---|---|---|
.k-otp | role=group | Sets the proper role for the OTP. |
.k-otp>input | type=hidden | The hidden input holding the OTP inputs value. |
aria-hidden=true | Hides the hidden input from assistive technologies. | |
.k-otp-input .k-input-inner | label for or aria-label or aria-labelledby | The input needs an accessible name to be assigned to it. |
aria-required=true | The attribute is rendered only when the OTP is in a form HTML element and announces the required state of the component. | |
aria-describedby=.k-form-hint id/.k-form-error id | Points to the hint for the input, or if the input is invalid, to the error message. This attribute should only be present when a hint is set or when the input is invalid. | |
autocomplete=off | Sets the default autocomplete for the input. | |
.k-invalid .k-input-inner,.ng-invalid .k-input-inner | aria-invalid=true | The attribute is rendered only when the OTP 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 OTP is disabled. |
Resources
WAI-ARIA Specification for the TextBox
Section 508
The OTP is fully compliant with the Section 508 requirements.
Testing
The OTP 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 OTP has been tested with the following screen readers and browsers combinations:
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |
Test Example
To test the OTPInput component, refer to the OTPInput Accessibility Demo.
Keyboard Navigation
For details on how the OTPInput keyboard navigation works, refer to the OTPInput Keyboard Navigation article.