You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article lists the compliance with the various accessibility standards that the Telerik UI for Blazor components provide.
14
15
15
-
For details on the keyboard support, see the [Keyboard Navigation]({%slug accessibility-keyboard-navigation%}) article.
16
+
For details on the keyboard support and how it works, see the [Keyboard Navigation]({%slug accessibility-overview%}#keyboard-navigation) section.
16
17
17
18
All components implement the required WAI-ARIA attributes without the need for any extra configuration.
18
19
19
-
Due to the complexity of some of the components in the suite, we sometimes run into scenarios not covered by the WAI-ARIA specification. In those cases, we tap into the web development accessibility know-how of the rest of the Progress organization, including feedback from accessibility-minded users, for expertise and feedback based on 10 years of creating web component libraries. This knowledge-sharing across internal teams and clients helps us ensure that UI for Blazor can reach a certain level of accessibility compliance even with its most advanced components.
20
+
Due to the complexity of some of the components in the suite, we sometimes run into scenarios that are not covered by the WAI-ARIA specification. In those cases, we benefit from the know-how of the dedicated accessibility professionals at Progress Software and feedback from accessibility-minded users.
20
21
21
-
This article will be updated with details on the Section 508 and WCAG 2.2 compatibility levels.
22
+
The Telerik UI for Blazor components are highly extensible and customizable. This means that, depending on the level of customization applied, you may be introducing rendering that is not accessible. Therefore, it is recommended that you test any modifications and templates you create to ensure the components still meet the desired level of accessibility standards. Additionally, be mindful of components working with custom input (images, text, HTML content, and so on) and make sure your content is accessible too.
22
23
23
-
<!--
24
-
>caption Accessibility compliance levels support provided by the Telerik UI for Blazor components.
25
-
-->
24
+
## Voluntary Product Accessibility Template
26
25
26
+
A [Voluntary Product Accessibility Template (VPAT®)](https://www.section508.gov/sell/vpat/) is a document that explains how information and communication technology (ICT) products such as software, hardware, electronic content, and support documentation meet (conform to) the Revised 508 Standards for IT accessibility.
27
27
28
+
>tip Download and review the latest version of the <ahref="assets/BlazorVPAT.doc"download>Telerik UI for Blazor VPAT document</a>.
28
29
30
+
## Compliance Table
29
31
30
-
31
-
32
-
The Telerik UI for Blazor components are highly extensible and customizable. This means that, depending on the level of customization applied, you may be introducing rendering that is not accessible. Therefore, it is recommended that you test any modifications and templates you create to ensure the components still meet the desired level of accessibility standards. Additionally, be mindful of components working with custom input (images, text, HTML content, and so on) and make sure your content is accessible, too.
32
+
> The compliance and accessibility of some components may depend on the enabled features. The compliance levels in the table below are achievable with the [*Default Ocean Blue A11y* theme swatch]({%slug accessibility-overview%}#color-contrast).
| ColorPicker | Yes | AA |[Enhanced](https://demos.telerik.com/blazor-ui/colorpicker/overview) <br /> Also see the [ColorGradient](https://demos.telerik.com/blazor-ui/colorgradient/keyboard-navigation) and [ColorPalette](https://demos.telerik.com/blazor-ui/colorpalette/keyboard-navigation).|[Documentation]({%slug colorpicker-wai-aria-support%}) |
60
60
| ComboBox | Yes | AA |[Enhanced](https://demos.telerik.com/blazor-ui/combobox/keyboard-navigation)|[Documentation]({%slug combobox-wai-aria-support%}) |
61
61
| ContextMenu | Yes | AA |[Enhanced](https://demos.telerik.com/blazor-ui/contextmenu/keyboard-navigation)|[Documentation]({%slug contextmenu-wai-aria-support%}) |
62
62
| DateInput | Yes | AA |[Enhanced](https://demos.telerik.com/blazor-ui/dateinput/keyboard-navigation)|[Documentation]({%slug dateinput-wai-aria-support%}) |
63
63
| DatePicker | Yes | AA |[Enhanced](https://demos.telerik.com/blazor-ui/datepicker/keyboard-navigation)|[Documentation]({%slug datepicker-wai-aria-support%}) |
64
64
| DateRangePicker | Yes | AA |[Enhanced](https://demos.telerik.com/blazor-ui/daterangepicker/keyboard-navigation)|[Documentation]({%slug daterangepicker-wai-aria-support%}) |
65
65
| DateTimePicker | Yes | AA |[Enhanced](https://demos.telerik.com/blazor-ui/datetimepicker/keyboard-navigation)|[Documentation]({%slug datetimepicker-wai-aria-support%}) |
0 commit comments