Skip to content

Commit a30a81b

Browse files
committed
Sync with Kendo UI Professional
1 parent 13b234c commit a30a81b

File tree

16 files changed

+1107
-61
lines changed

16 files changed

+1107
-61
lines changed

docs-aspnet/backwards-compatibility/2024-backwards-compatibility.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,13 @@ position: 1
99
# 2024 Releases
1010

1111
This article lists the breaking or important changes in the 2024 releases of {{ site.product }}.
12+
{% if site.core %}
13+
## {{ site.product }} Q4 2024
14+
15+
### Checkbox
16+
17+
The `Rounded` configuration hor the HTML Helpers now expects [`Kendo.Mvc.UI.Rounded`](https://docs.telerik.com/aspnet-core/api/kendo.mvc.ui/rounded) enum instead of [`Kendo.Mvc.UI.BasicRounded`](https://docs.telerik.com/aspnet-core/api/kendo.mvc.ui/basicrounded), exposing an additional `Full` option.
18+
{% endif %}
1219

1320
## {{ site.product }} Q2 2024
1421

20.7 KB
Loading
25.9 KB
Loading
23.3 KB
Loading

docs-aspnet/html-helpers/charts/chart-types/overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,25 +18,25 @@ The Charts support a wide range of series types.
1818

1919
[Categorical charts]({% slug htmlhelpers_categoricalcharts_aspnetcore %}) provide built-in support for displaying dates. The categories represent unique values which are not mathematically related to each other.
2020

21-
Examples of categorical charts are [Area]({% slug areacharts_aspnetcore_htmlhelper %}), [Bar]({% slug barcharts_aspnetcore_htmlhelper %}), [Box Plot]({% slug boxplotcharts_aspnetcore_htmlhelper %}), [Bullet]({% slug bulletcharts_aspnetcore_htmlhelper %}), and [Line Charts]({% slug linecharts_aspnetcore_htmlhelper %}).
21+
Examples of categorical charts are [Area]({% slug areacharts_aspnetcore_htmlhelper %}), [Bar]({% slug barcharts_aspnetcore_htmlhelper %}), [Box Plot]({% slug boxplotcharts_aspnetcore_htmlhelper %}), [Bullet]({% slug bulletcharts_aspnetcore_htmlhelper %}), and [Line charts]({% slug linecharts_aspnetcore_htmlhelper %}).
2222

2323
## Circular Charts
2424

2525
Circular charts are divided in slices representing statistical data, which proportionally corresponds to the quantity input of each slice. Circular charts are widely used in the business world and the mass media.
2626

27-
Examples of circular charts are [Pie Charts]({% slug piecharts_aspnetcore_htmlhelper %}).
27+
Examples of circular charts are [Pie charts]({% slug piecharts_aspnetcore_htmlhelper %}), [Donut charts]({% slug donutcharts_aspnetcore_htmlhelper %}), and [Polar charts]({% slug polarcharts_aspnetcore_htmlhelper %}).
2828

2929
## Freeform Charts
3030

3131
Freeform charts adopt different forms and use variously structured portions to display data.
3232

33-
Examples of freeform charts are [Funnel Charts]({% slug funnelchart_aspnetcore_htmlhelper %}).
33+
Examples of freeform charts are [Funnel charts]({% slug funnelchart_aspnetcore_htmlhelper %}).
3434

3535
## Scatter Charts
3636

3737
[Scatter charts]({% slug htmlhelpers_scattercharts_aspnetcore %}) are suitable for displaying and comparing different sets of numerical values, for showing the relationships between the values of the data sets, and for plotting two-dimensional data as a series of XY coordinates.
3838

39-
Example of scatter charts are [Bubble Charts]({% slug bubblecharts_aspnetcore_htmlhelper %}).
39+
Example of scatter charts are [Bubble charts]({% slug bubblecharts_aspnetcore_htmlhelper %}).
4040

4141
## See Also
4242

docs-aspnet/html-helpers/charts/chart-types/polar-charts.md

Lines changed: 448 additions & 0 deletions
Large diffs are not rendered by default.

docs-aspnet/html-helpers/charts/overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -328,6 +328,7 @@ The Telerik UI for {{ site.framework }} Chart supports an extensive set of serie
328328
| [Funnel Charts]({% slug funnelchart_aspnetcore_htmlhelper %}) | Funnel Charts are suitable for representing stages in a sales process and for showing the amount of the potential revenue from each stage. |
329329
| [Line Charts]({% slug linecharts_aspnetcore_htmlhelper %}) | Line Charts are suitable for displaying quantitative data by using continuous lines passing through points defined by the values of their items. |
330330
| [Pie Charts]({% slug piecharts_aspnetcore_htmlhelper %}) | Pie Charts display data as single-series sectors from a two-dimensional circle which is useful for rendering data as a part of the whole. |
331+
| [Polar Charts]({% slug polarcharts_aspnetcore_htmlhelper %}) | Polar Charts represent the relationships between data points in terms of radiuses and angles in a circular coordinate system. |
331332
| [Donut Charts]({% slug donutcharts_aspnetcore_htmlhelper %}) | Donut Charts are a Pie chart variation with the ability to display data as single-series sectors from a two-dimensional circle. |
332333

333334
## Referencing Existing Instances
Lines changed: 67 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Overview
3-
page_title: jQuery Slider Documentation - Slider Accessibility
3+
page_title: jQuery Slider Documentation | Slider Accessibility
44
description: "Get started with the jQuery Slider by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
55
slug: accessibility_kendoui_slider
66
position: 1
@@ -10,25 +10,83 @@ position: 1
1010

1111
The Slider is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
1212

13-
For more information, refer to:
13+
For more information, refer to:
1414
* [Keyboard navigation by the Kendo UI Slider]({% slug keynav_kendoui_slider %})
1515
* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
1616

17+
18+
19+
20+
Out of the box, the Kendo UI for jQuery Slider provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
21+
22+
23+
The Slider is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2 AA](https://www.w3.org/TR/WCAG22/) standards](https://www.w3.org/TR/WCAG22/) and [Section 508](http://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.
24+
1725
## WAI-ARIA
1826

19-
The component follows the WAI-ARIA Authoring Practices for implementing the keyboard navigation for its component role and is tested against the popular screen readers. For more information, refer to the article on [WAI-ARIA support in Kendo UI for jQuery]({% slug wai_aria_accessibility_support %}).
27+
28+
This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
29+
30+
### Slider Drag Handle
31+
32+
| Selector | Attribute | Usage |
33+
| -------- | --------- | ----- |
34+
| `.k-draghandle` | `role=slider` | Sets the proper role for Slider. |
35+
| | `aria-label` or `aria-labelledby` or `title` | The Slider needs an accessible name to be assigned to it. |
36+
| | `aria-valuetext` | Specifies the text that would be announced based on the currently selected value in the Slider. |
37+
| | `aria-readonly=true` | Attribute is rendered only when the Slider is readonly. |
38+
| | `aria-invalid=true` | Attribute is rendered only when the Slider is in form and announces the valid state of the component. |
39+
| | `tabindex=0` | The element must be focusable. |
40+
| `.k-draghandle:not(.k-hsv-draghandle)` | `aria-valuenow` | Specifies the currently selected value in the Slider. |
41+
| | `aria-valuemin` | Specifies the minimum available value in the Slider. |
42+
| | `aria-valuemax` | Specifies the maximum available value in the Slider. |
43+
| `.k-slider-vertical .k-draghandle` | `aria-orientation=vertical` | Present only when slider is vertical. |
44+
| `.k-disabled .k-draghandle` | `aria-disabled=true` | Attribute is rendered only when the Slider is disabled. |
45+
46+
> Note that using an `<a>` element for `role="slider"` is not allowed.
47+
48+
### Slider Buttons
49+
50+
51+
When present, the Slider Buttons must implement the specification for the **Button** component.
52+
53+
[Button accessibility specification]({{button_a11y_link}})
54+
55+
## Resources
56+
57+
[WAI-ARIA specification for slider](https://www.w3.org/TR/wai-aria-1.2/#slider)
2058

2159
## Section 508
2260

23-
The Slider is compliant with the Section 508 requirements. For more information, refer to the article on [Section 508 support in Kendo UI for jQuery]({% slug section508_accessibility_support %}).
2461

25-
## WCAG 2.2
62+
The Slider is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
2663

27-
The Slider supports the standards for providing accessible web content which are set by the [Web Content Accessibility Guidelines 2.1](https://www.w3.org/TR/WCAG/). For more information, refer to the article on [WCAG 2.2 compliance in Kendo UI for jQuery]({% slug section508_wcag21_accessibility_support %})
64+
## Testing
65+
66+
67+
The Slider has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
68+
69+
> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
70+
71+
### Screen Readers
2872

29-
## See Also
3073

74+
The Slider has been tested with the following screen readers and browsers combinations:
75+
76+
| Environment | Tool |
77+
| ----------- | ---- |
78+
| Firefox | NVDA |
79+
| Chrome | JAWS |
80+
| Microsoft Edge | JAWS |
81+
82+
83+
84+
### Automated Testing
85+
The Slider has been tested with [axe-core](https://github.com/dequelabs/axe-core).
86+
### Test Example
87+
A live test example of the Slider component could be found here: https://demos.telerik.com/kendo-ui/accessibility/slider
88+
## See Also
3189
* [Keyboard Navigation by the Slider (Demo)](https://demos.telerik.com/kendo-ui/slider/keyboard-navigation)
32-
* [Keyboard Navigation by the Slider]({% slug keynav_kendoui_slider %})
90+
* [Keyboard Navigation by the Slider]({% slug accessibility_kendoui_slider %})
3391
* [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
34-
* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
92+
* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
---
2+
title: Overview
3+
page_title: jQuery Splitter Documentation | Splitter Accessibility
4+
description: "Get started with the jQuery Splitter by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
5+
slug: accessibility_kendoui_splitter_widget
6+
position: 1
7+
---
8+
9+
# Splitter Accessibility
10+
11+
The Splitter is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
12+
13+
For more information, refer to [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %}).
14+
15+
16+
17+
18+
Out of the box, the Kendo UI for jQuery Splitter provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
19+
20+
21+
The Splitter is compliant with the [Web Content Accessibility Guidelines (WCAG) 2.2 AA](https://www.w3.org/TR/WCAG22/) standards](https://www.w3.org/TR/WCAG22/) and [Section 508](http://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.
22+
23+
## WAI-ARIA
24+
25+
26+
This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
27+
28+
### Slitter Pane
29+
30+
| Selector | Attribute | Usage |
31+
| -------- | --------- | ----- |
32+
| `.k-pane` | `role=group` | Sets the proper role for the Splitter pane that identifies a set of user interface objects that is not intended to be included in the page's summary or table of contents. |
33+
34+
> Note: The value of the `aria-label` attribute of the split-bar elements will be provided to their respective preceding pane element through the API.
35+
36+
### SplitBar
37+
38+
| Selector | Attribute | Usage |
39+
| -------- | --------- | ----- |
40+
| `.k-splitbar` | `role=separator` | Sets the proper role for the Splitter split-bar element. |
41+
| | `aria-label` | An accessible name, with aria-label should be included if there is more than one focusable separator. The value is set through the corresponding SplitterPane API. |
42+
| `.k-splitbar-horizontal` | `aria-orientation=vertical` | When a splitbar separates two panes horizontally, its aria-orientation must be explicitly set to 'vertical'. |
43+
44+
> Note: Setting the value-now attribute of the separator element is not applicable, as the Splitter is a complex layout component allowing splitting the content into multiple panes across any number and level of nested Splitters and panes, thus announcing a value would not convey any meaningful information. Moreover, there is no specification, or WAI-ARIA recommendation that explains how value should be set in multiple panes scenario. Further information on this complicated scenario could be found in the following WAI-ARIA GitHub issue:
45+
46+
[WAI-ARIA Practices on GitHub](https://github.com/w3c/aria-practices/issues/129#issuecomment-456976215)
47+
48+
## Resources
49+
50+
[WAI-ARIA specification for separator](https://www.w3.org/TR/wai-aria-1.2/#separator)
51+
52+
[MDN reference for the separator role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/separator_role)
53+
54+
## Section 508
55+
56+
57+
The Splitter is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
58+
59+
## Testing
60+
61+
62+
The Splitter has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
63+
64+
> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
65+
66+
### Screen Readers
67+
68+
69+
The Splitter has been tested with the following screen readers and browsers combinations:
70+
71+
| Environment | Tool |
72+
| ----------- | ---- |
73+
| Firefox | NVDA |
74+
| Chrome | JAWS |
75+
| Microsoft Edge | JAWS |
76+
77+
78+
79+
### Automated Testing
80+
The Splitter has been tested with [axe-core](https://github.com/dequelabs/axe-core).
81+
### Test Example
82+
A live test example of the Splitter component could be found here: https://demos.telerik.com/kendo-ui/accessibility/splitter
83+
## See Also
84+
* [Keyboard Navigation by the Splitter (Demo)](https://demos.telerik.com/kendo-ui/splitter/keyboard-navigation)
85+
* [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
86+
* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})

0 commit comments

Comments
 (0)