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
Copy file name to clipboardExpand all lines: accessibility/compliance.md
+15-11Lines changed: 15 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,19 +21,13 @@ The [Accessibility Conformance Report (ACR)](https://www.section508.gov/sell/acr
21
21
22
22
## Compliance Table
23
23
24
-
The table below specifies the level of WCAG 2.2 compliance of each Telerik component for Blazor. The table also provides links to information about keyboard shortcuts, WAI-ARIA attributes, and additional component-specific accessibility documentation.
24
+
The table below specifies the level of WCAG 2.2 compliance of each Telerik component for Blazor.
25
25
26
-
The information is subject to the following considerations:
26
+
* The *Keyboard Navigation* column links to component-specific online demos or keyboard shortcut lists. For general information on how the keyboard support works, see the [Keyboard Navigation]({%slug accessibility-overview%}#keyboard-navigation) section.
27
+
* The *Accessibility Documentation* column links to component-specific details and information about WAI-ARIA attributes.
28
+
* For information about **Section 508** of the US Rehabilitation Act, the **European Accessibility Act** in the EU, or any other national accessibility legislation, see section [Legal and Technical Compliance]({%slug accessibility-overview%}#legal-and-technical-compliance).
27
29
28
-
* All components implement the required WAI-ARIA attributes without the need for any extra configuration. Some components may provide parameters that render additional optional WAI-ARIA attributes, for example, `aria-label` or `aria-describedby`.
29
-
* The compliance levels are achievable with the [*Default Ocean Blue A11y* theme swatch]({%slug accessibility-overview%}#color-contrast).
30
-
* The accessibility and compliance of some components may depend on the enabled features. In such cases, the compliance level below is based on the default component configuration.
31
-
* Component templates introduce custom markup that may not be accessible. Test any modifications to ensure the web content still meets the desired level of accessibility compliance. Be mindful of components that work with user input such as images, text, or HTML content.
32
-
* Due to the complexity of some components, there are 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.
33
-
34
-
For information about **Section 508** of the US Rehabilitation Act, the **European Accessibility Act** in the EU, or any other national accessibility legislation, see section [Legal and Technical Compliance]({%slug accessibility-overview%}#legal-and-technical-compliance).
35
-
36
-
The *Keyboard Navigation* column links to component-specific online demos or keyboard shortcut lists. For general information on how the keyboard support works, see the [Keyboard Navigation]({%slug accessibility-overview%}#keyboard-navigation) section.
30
+
Also check the [notes below the table](#accessibility-compliance-notes).
@@ -138,6 +132,16 @@ The *Keyboard Navigation* column links to component-specific online demos or key
138
132
| Window | AA |[Enhanced](https://demos.telerik.com/blazor-ui/window/keyboard-navigation)|[Documentation]({%slug window-wai-aria-support%}) |
139
133
| Wizard | AA |[Enhanced](https://demos.telerik.com/blazor-ui/wizard/keyboard-navigation)|[Documentation]({%slug wizard-wai-aria-support%}) |
140
134
135
+
## Accessibility Compliance Notes
136
+
137
+
The information in the compliance table above is subject to the following considerations:
138
+
139
+
* All components implement the required WAI-ARIA attributes without the need for any extra configuration. Some components may provide parameters that render additional optional WAI-ARIA attributes, for example, `aria-label` or `aria-describedby`.
140
+
* The compliance levels are achievable with the [*Default Ocean Blue A11y* theme swatch]({%slug accessibility-overview%}#color-contrast) or any other [custom theme swatch]({%slug themes-customize%}) that provides the minimum required color contrast.
141
+
* The accessibility and compliance of some components may depend on the enabled features. In such cases, the compliance table information is based on the default component configuration.
142
+
* Component templates introduce custom markup that may not be accessible. Test any modifications to ensure the web content still meets the desired level of accessibility compliance. Be mindful of components that work with user input such as images, text, or HTML content.
143
+
* Due to the complexity of some components, there are 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.
Copy file name to clipboardExpand all lines: accessibility/overview.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,10 @@ Web applications are accessible when they provide control over their features to
21
21
22
22
## Legal and Technical Compliance
23
23
24
-
Accessibility compliance can be considered from a legal and technical perspective, but these ultimately merge. <ahref="https://www.w3.org/WAI/policies/"target="_blank">Different countries have different regulations about web content accessibility compliance</a>, for example, Section 508 of the US Rehabilitation Act or the EU European Accessibility Act.
24
+
Accessibility compliance can be considered from a legal and technical perspective, but these ultimately merge. <ahref="https://www.w3.org/WAI/policies/"target="_blank">Different countries have different regulations about web content accessibility compliance</a>, for example:
25
+
26
+
* Section 508 of the US Rehabilitation Act
27
+
* The EU European Accessibility Act
25
28
26
29
The national regulations normally share the following characteristics:
27
30
@@ -36,6 +39,7 @@ From technical point of view, Telerik UI for Blazor achieves accessibility throu
36
39
*[WAI-ARIA attributes](#wai-aria)
37
40
*[Keyboard navigation](#keyboard-navigation)
38
41
*[Color contrast](#color-contrast)
42
+
*[Best practices in component development and testing](#development-practices)
39
43
40
44
## Web Context Accessibility Guidelines
41
45
@@ -78,7 +82,16 @@ You can [obtain and use the Default Ocean Blue A11y swatch]({%slug themes-overvi
78
82
*[Telerik UI for Blazor version 4.0.1](https://www.telerik.com/support/whats-new/blazor-ui/release-history/ui-for-blazor-4-0-1)
79
83
*[Themes version 6.0.3](https://github.com/telerik/kendo-themes/releases/tag/v6.0.3). Check section [Theme Version Compatibility]({%slug themes-overview%}#compatibility-and-maintenance) on how to align Telerik UI for Blazor versions with theme versions.
80
84
81
-
## Screen Readers
85
+
## Development Practices
86
+
87
+
When implementing a Telerik Blazor component, the team:
88
+
89
+
* Follows the WCAG standard and WAI-ARIA specification to lay the right foundation for the component accessibility.
90
+
* Implements automated unit tests guarantee accessible and semantically correct rendering.
91
+
* Localizes messages for labels, titles, and other elements.
92
+
* Manually tests the component to with regard to its keyboard navigation and usage with screen readers.
93
+
94
+
### Screen Readers
82
95
83
96
There are a lot of existing screen readers, for example:
For details on how the AutoComplete keyboard navigation works, refer to the [Blazor AutoComplete Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/autocomplete/keyboard-navigation).
11
+
8
12
## See Also
9
13
10
-
* [Blazor AutoComplete Accessibility and Keyboard Navigation (Demo)](https://demos.telerik.com/blazor-ui/autocomplete/keyboard-navigation)
11
14
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
For details on how the Breadcrumb keyboard navigation works, refer to the [Blazor Breadcrumb Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/breadcrumb/keyboard-navigation).
11
+
8
12
## See Also
9
13
10
-
* [Blazor Breadcrumb Accessibility and Keyboard Navigation (Demo)](https://demos.telerik.com/blazor-ui/breadcrumb/keyboard-navigation)
11
14
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
For details on how the Button keyboard navigation works, refer to the [Blazor Button Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/button/keyboard-navigation).
11
+
8
12
## See Also
9
13
10
-
* [Blazor Button Accessibility and Keyboard Navigation (Demo)](https://demos.telerik.com/blazor-ui/button/keyboard-navigation)
11
14
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
For details on how the ButtonGroup keyboard navigation works, refer to the [Blazor ButtonGroup Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/buttongroup/keyboard-navigation).
11
+
8
12
## See Also
9
13
10
-
* [Blazor ButtonGroup Accessibility and Keyboard Navigation (Demo)](https://demos.telerik.com/blazor-ui/buttongroup/keyboard-navigation)
11
14
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
For details on how the Calendar keyboard navigation works, refer to the [Blazor Calendar Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/calendar/keyboard-navigation).
11
+
8
12
## See Also
9
13
10
-
* [Blazor Calendar Accessibility and Keyboard Navigation (Demo)](https://demos.telerik.com/blazor-ui/calendar/keyboard-navigation)
11
14
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
For details on how the Carousel keyboard navigation works, refer to the [Blazor Carousel Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/carousel/keyboard-navigation).
11
+
8
12
## See Also
9
13
10
-
* [Blazor Carousel Accessibility and Keyboard Navigation (Demo)](https://demos.telerik.com/blazor-ui/carousel/keyboard-navigation)
11
14
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})
For details on how the Chart keyboard navigation works, refer to the [Blazor Chart Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/chart/keyboard-navigation).
For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
0 commit comments