Blazor Form Accessibility
Out of the box, the Telerik UI for Blazor Form provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
The Form 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.
Form Component
The Form component provides a structured way to collect user inputs. It is designed to ensure accessibility and usability for all users, including those with disabilities.
| Selector | Attribute | Usage |
|---|---|---|
.k-form | role=form or nodeName=form | Omitted if the <form> DOM element is used. |
Input elements
The Form field input element of the component should indicate if it is required and announce any hints or error messages.
Section 508
The Form is fully compliant with the Section 508 requirements.
Testing
The Form 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 Form has been tested with the following screen readers and browsers combinations:
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |
Keyboard Navigation
For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the Accessibility Overview article.