Blazor Dialog Accessibility
Out of the box, the Telerik UI for Blazor Dialog provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
The Dialog 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.
Dialog component
| Selector | Attribute | Usage |
|---|---|---|
.k-dialog |
role=dialog |
Announces the dialog role of the component. |
aria-labelledby=.k-dialog-titlebar id |
Associate the title of the dialog. | |
aria-describedby=.k-dialog-content id |
Associate the dialog content to the wrap element. | |
.k-overlay + .k-dialog |
aria-modal=true |
Announces that the dialog is modal. Attribute is added only when the dialog is modal. |
Predefined dialogs
| Selector | Attribute | Usage |
|---|---|---|
.k-dialog.k-prompt,.k-dialog.k-alert,.k-dialog.k-confirm |
role=alertdialog |
Announces the dialog role of the component. |
Resources
ARIA practices Modal Dialog Example
Section 508
The Dialog is fully compliant with the Section 508 requirements.
Testing
The Dialog 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 Dialog has been tested with the following screen readers and browsers combinations:
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |