Skip to content

Commit e518713

Browse files
kendo-botdimodi
kendo-bot
authored and
dimodi
committed
docs: update accessibility and keyboard-nav specs
1 parent 99e0bf8 commit e518713

File tree

6 files changed

+350
-1
lines changed

6 files changed

+350
-1
lines changed

‎components/card/accessibility/wai-aria-support.md‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
title: Wai-Aria Support
3+
page_title: Telerik UI for Blazor Card Documentation | Card Accessibility
4+
description: "Get started with the Telerik UI for Blazor Card and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
5+
tags: telerik,blazor,accessibility,wai-aria,wcag
6+
slug: button-wai-aria-support
7+
position: 50
8+
---
9+
10+
# Blazor Card Accessibility
11+
12+
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
13+
14+
15+
16+
Out of the box, the Telerik UI for Blazor Card provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
17+
18+
19+
The Card is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2 AA](https://www.w3.org/TR/WCAG22/) standards and [Section 508](https://www.section508.gov/) requirements, follows the [Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/WAI/ARIA/apg/) best practices for implementing the [keyboard navigation](#keyboard-navigation) for its `component` role, provides options for managing its focus and is tested against the most popular screen readers.
20+
21+
## WAI-ARIA
22+
23+
24+
This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
25+
26+
### Card Component
27+
28+
29+
The Card component is a UI container with styles for organized content. It does not have WAI ARIA and keyboard navigation unless used in a Card List.
30+
31+
| Selector | Attribute | Usage |
32+
| -------- | --------- | ----- |
33+
| `.k-card-list .k-card` | `role=listitem` | When the card is located in a list, it should accept the listitem role. |
34+
| | `tabindex=0` | The card component is focusable. By enabling navigatable setting in the card component, it is focusable and all inner elements are not until Enter key is pressed. |
35+
| | `aria-describedby=.k-card-title id` | Associate the card to the title element when going through the cards. |
36+
| | `aria-keyshortcuts=Enter` | Announces the bound Enter key for the Card component that will enable the navigation inside the card. |
37+
38+
## Section 508
39+
40+
41+
The Card is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
42+
43+
## Testing
44+
45+
46+
The Card has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
47+
48+
> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
49+
50+
### Screen Readers
51+
52+
53+
The Card has been tested with the following screen readers and browsers combinations:
54+
55+
| Environment | Tool |
56+
| ----------- | ---- |
57+
| Firefox | NVDA |
58+
| Chrome | JAWS |
59+
| Microsoft Edge | JAWS |
60+
61+
62+
63+
## Keyboard Navigation
64+
65+
For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
66+
67+
## See Also
68+
69+
* [Blazor Card Demos](https://demos.telerik.com/blazor-ui/card/overview)
70+
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})

‎components/form/accessibility/wai-aria-support.md‎

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
---
2+
title: Wai-Aria Support
3+
page_title: Telerik UI for Blazor Form Documentation | Form Accessibility
4+
description: "Get started with the Telerik UI for Blazor Form and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
5+
tags: telerik,blazor,accessibility,wai-aria,wcag
6+
slug: form-wai-aria-support
7+
position: 50
8+
---
9+
10+
# Blazor Form Accessibility
11+
12+
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
13+
14+
15+
16+
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.
17+
18+
19+
The Form is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2 AA](https://www.w3.org/TR/WCAG22/) standards and [Section 508](https://www.section508.gov/) requirements, follows the [Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/WAI/ARIA/apg/) best practices for implementing the [keyboard navigation](#keyboard-navigation) for its `component` role, provides options for managing its focus and is tested against the most popular screen readers.
20+
21+
## WAI-ARIA
22+
23+
24+
This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
25+
26+
### Form Component
27+
28+
29+
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.
30+
31+
| Selector | Attribute | Usage |
32+
| -------- | --------- | ----- |
33+
| `.k-form` | `role=form` or `nodeName=form` | Omitted if the `<form>` DOM element is used. |
34+
35+
### Input elements
36+
37+
38+
The Form field input element of the component should indicate if it is required and announce any hints or error messages.
39+
40+
## Section 508
41+
42+
43+
The Form is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
44+
45+
## Testing
46+
47+
48+
The Form has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
49+
50+
> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
51+
52+
### Screen Readers
53+
54+
55+
The Form has been tested with the following screen readers and browsers combinations:
56+
57+
| Environment | Tool |
58+
| ----------- | ---- |
59+
| Firefox | NVDA |
60+
| Chrome | JAWS |
61+
| Microsoft Edge | JAWS |
62+
63+
64+
65+
## Keyboard Navigation
66+
67+
For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
68+
69+
## See Also
70+
71+
* [Blazor Form Demos](https://demos.telerik.com/blazor-ui/form/overview)
72+
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})

‎components/panelbar/accessibility/wai-aria-support.md‎

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: Wai-Aria Support
3+
page_title: Telerik UI for Blazor PanelBar Documentation | PanelBar Accessibility
4+
description: "Get started with the Telerik UI for Blazor PanelBar and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
5+
tags: telerik,blazor,accessibility,wai-aria,wcag
6+
slug: panelbar-wai-aria-support
7+
position: 50
8+
---
9+
10+
# Blazor PanelBar Accessibility
11+
12+
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
13+
14+
15+
16+
Out of the box, the Telerik UI for Blazor PanelBar provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
17+
18+
19+
The PanelBar is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2 AA](https://www.w3.org/TR/WCAG22/) standards and [Section 508](https://www.section508.gov/) requirements, follows the [Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/WAI/ARIA/apg/) best practices for implementing the [keyboard navigation](#keyboard-navigation) for its `component` role, provides options for managing its focus and is tested against the most popular screen readers.
20+
21+
## WAI-ARIA
22+
23+
24+
This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
25+
26+
| Selector | Attribute | Usage |
27+
| -------- | --------- | ----- |
28+
| `.k-panelbar` | `role=tree` | The root element of the PanelBar has role `tree`. |
29+
| | `aria-activedescendant=.k-item id` | Points to the currently focused item in the PanelBar. |
30+
| `.k-panelbar-group` | `role=group` | The `ul` element that wraps child nodes. |
31+
| `[aria-expanded='false']>.k-panelbar-group` | `aria-hidden=true` | Hides the `group` element from assistive technologies when its parent is not expanded. |
32+
| `.k-item` | `role=treeitem` | The `li` element rendered for a PanelBar item. |
33+
| | `aria-expanded=true/false` | Announces the expanded state of the item (if expandable). It is `true` when expanded, and `false` when collapsed. |
34+
| | `aria-selected=true/false` | Announces the selected state of the item. |
35+
36+
## Resources
37+
38+
[ARIA practices Navigation Treeview Example](https://www.w3.org/WAI/ARIA/apg/example-index/treeview/treeview-navigation.html)
39+
40+
## Section 508
41+
42+
43+
The PanelBar is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
44+
45+
## Testing
46+
47+
48+
The PanelBar has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
49+
50+
> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
51+
52+
### Screen Readers
53+
54+
55+
The PanelBar has been tested with the following screen readers and browsers combinations:
56+
57+
| Environment | Tool |
58+
| ----------- | ---- |
59+
| Firefox | NVDA |
60+
| Chrome | JAWS |
61+
| Microsoft Edge | JAWS |
62+
63+
64+
65+
## Keyboard Navigation
66+
67+
For details on how the PanelBar keyboard navigation works, refer to the [Blazor PanelBar Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/panelbar/keyboard-navigation).
68+
69+
## See Also
70+
71+
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})

‎components/rating/accessibility/wai-aria-support.md‎

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
title: Wai-Aria Support
3+
page_title: Telerik UI for Blazor Rating Documentation | Rating Accessibility
4+
description: "Get started with the Telerik UI for Blazor Rating and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
5+
tags: telerik,blazor,accessibility,wai-aria,wcag
6+
slug: rating-wai-aria-support
7+
position: 50
8+
---
9+
10+
# Blazor Rating Accessibility
11+
12+
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
13+
14+
15+
16+
Out of the box, the Telerik UI for Blazor Rating provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
17+
18+
19+
The Rating is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2 AA](https://www.w3.org/TR/WCAG22/) standards and [Section 508](https://www.section508.gov/) requirements, follows the [Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/WAI/ARIA/apg/) best practices for implementing the [keyboard navigation](#keyboard-navigation) for its `component` role, provides options for managing its focus and is tested against the most popular screen readers.
20+
21+
## WAI-ARIA
22+
23+
24+
This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
25+
26+
| Selector | Attribute | Usage |
27+
| -------- | --------- | ----- |
28+
| `.k-rating` | `role=slider` | Announces the `slider` role of the Rating element. |
29+
| | `aria-label` or `aria-labelledby` or `title` | The Rating needs an accessible name to be assigned to it. |
30+
| | `tabindex=0` | The element must be focusable. |
31+
| | `aria-valuenow` | Specifies the currently selected value in the Rating. |
32+
| | `aria-valuemin` | Specifies the minimum available value in the Rating. |
33+
| | `aria-valuemax` | Specifies the maximum available value in the Rating. |
34+
35+
## Resources
36+
37+
[WAI-ARIA specification for slider](https://www.w3.org/TR/wai-aria-1.2/#slider)
38+
39+
## Section 508
40+
41+
42+
The Rating is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
43+
44+
## Testing
45+
46+
47+
The Rating has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
48+
49+
> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
50+
51+
### Screen Readers
52+
53+
54+
The Rating has been tested with the following screen readers and browsers combinations:
55+
56+
| Environment | Tool |
57+
| ----------- | ---- |
58+
| Firefox | NVDA |
59+
| Chrome | JAWS |
60+
| Microsoft Edge | JAWS |
61+
62+
63+
64+
## Keyboard Navigation
65+
66+
For details on how the Rating keyboard navigation works, refer to the [Blazor Rating Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/rating/keyboard-navigation).
67+
68+
## See Also
69+
70+
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})

‎components/skeleton/accessibility/wai-aria-support.md‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Wai-Aria Support
3+
page_title: Telerik UI for Blazor Skeleton Documentation | Skeleton Accessibility
4+
description: "Get started with the Telerik UI for Blazor Skeleton and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
5+
tags: telerik,blazor,accessibility,wai-aria,wcag
6+
slug: skeleton-wai-aria-support
7+
position: 50
8+
---
9+
10+
# Blazor Skeleton Accessibility
11+
12+
@[template](/_contentTemplates/common/parameters-table-styles.md#table-layout)
13+
14+
15+
16+
Out of the box, the Telerik UI for Blazor Skeleton provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
17+
18+
19+
The Skeleton is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2 AAA](https://www.w3.org/TR/WCAG22/) standards and [Section 508](https://www.section508.gov/) requirements, follows the [Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/WAI/ARIA/apg/) best practices for implementing the [keyboard navigation](#keyboard-navigation) for its `component` role, provides options for managing its focus and is tested against the most popular screen readers.
20+
21+
## WAI-ARIA
22+
23+
24+
This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
25+
26+
27+
The Skeleton component does not have accessibility on its own as it is only visual indicator and should be integrated within an element that refers to the loading state. When integrated on a page, you might:
28+
29+
30+
- use `aria-busy` attribute to illustrate that the focusable element is loading
31+
- use `role="alert"` to announce the loading
32+
33+
## Section 508
34+
35+
36+
The Skeleton is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
37+
38+
## Testing
39+
40+
41+
The Skeleton has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
42+
43+
> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
44+
45+
### Screen Readers
46+
47+
48+
The Skeleton has been tested with the following screen readers and browsers combinations:
49+
50+
| Environment | Tool |
51+
| ----------- | ---- |
52+
| Firefox | NVDA |
53+
| Chrome | JAWS |
54+
| Microsoft Edge | JAWS |
55+
56+
57+
58+
## Keyboard Navigation
59+
60+
For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
61+
62+
## See Also
63+
64+
* [Blazor Skeleton Demos](https://demos.telerik.com/blazor-ui/skeleton/overview)
65+
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})

‎components/tilelayout/accessibility/wai-aria-support.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,9 @@ The TileLayout has been tested with the following screen readers and browsers co
6161

6262
## Keyboard Navigation
6363

64-
For details on how the TileLayout keyboard navigation works, refer to the [Blazor TileLayout Accessibility and Keyboard Navigation Demo](https://demos.telerik.com/blazor-ui/tilelayout/keyboard-navigation).
64+
For details on how the keyboard navigation works in Telerik UI for Blazor, refer to the [Accessibility Overview]({%slug accessibility-overview%}#keyboard-navigation) article.
6565

6666
## See Also
6767

68+
* [Blazor TileLayout Demos](https://demos.telerik.com/blazor-ui/tilelayout/overview)
6869
* [Accessibility in Telerik UI for Blazor]({%slug accessibility-overview%})

0 commit comments

Comments
 (0)