Blazor Window Accessibility
Out of the box, the Telerik UI for Blazor Window provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
The Window 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-window:not(.k-dialog) |
role=dialog |
Announces the dialog role of the component. |
aria-labelledby=.k-window-title id |
Associate the title of the dialog. | |
.k-overlay + .k-window |
aria-modal=true |
Announces that the dialog is modal. Attribute is added only when the dialog is modal. |
Action buttons follow the Button specification.
Button accessibility specification
Resources
ARIA practices Modal Dialog Example
Section 508
The Window is fully compliant with the Section 508 requirements.
Testing
The Window 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 Window has been tested with the following screen readers and browsers combinations:
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |