diff --git a/docs-aspnet/backwards-compatibility/2024-backwards-compatibility.md b/docs-aspnet/backwards-compatibility/2024-backwards-compatibility.md
index 6e8d83a03ac..3ebe24a1cda 100644
--- a/docs-aspnet/backwards-compatibility/2024-backwards-compatibility.md
+++ b/docs-aspnet/backwards-compatibility/2024-backwards-compatibility.md
@@ -24,6 +24,9 @@ As of the Q2 2024 release, the `Telerik.Web.Captcha` package targets .NET Framew
 
 **Telerik.Web.Spreadsheet**
 As of the Q2 2024 release, the `Telerik.Web.Spreadsheet` package targets .NET Framework 4.6.2
+
+**Kendo.Mvc.Export**
+As of the Q2 2024 release, the `Kendo.Mvc.Export.dll` assembly targets .NET Framework 4.6.2
 {% endif %}
 
 ### Chart
diff --git a/docs/controls/dialog/accessibility/overview.md b/docs/controls/dialog/accessibility/overview.md
new file mode 100644
index 00000000000..fc5f9eb88b1
--- /dev/null
+++ b/docs/controls/dialog/accessibility/overview.md
@@ -0,0 +1,79 @@
+---
+title: Overview
+page_title: jQuery Dialog Documentation | Dialog Accessibility
+description: "Get started with the jQuery Dialog by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
+slug: accessibility_kendoui_dialog_widget
+position: 1
+---
+
+# Dialog Accessibility
+
+The Dialog is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
+
+ For more information, refer to [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %}).
+
+
+
+
+Out of the box, the Kendo UI for jQuery 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](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.
+
+## 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](https://www.w3.org/WAI/ARIA/apg/example-index/dialog-modal/dialog)
+
+## Section 508
+
+
+The Dialog is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
+
+## Testing
+
+
+The Dialog has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The Dialog has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+The Dialog has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+### Test Example
+A live test example of the Dialog component could be found here: https://demos.telerik.com/kendo-ui/accessibility/dialog
+## See Also
+* [Keyboard Navigation by the Dialog (Demo)](https://demos.telerik.com/kendo-ui/dialog/keyboard-navigation)
+* [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/dropdownbutton/accessibility/overview.md b/docs/controls/dropdownbutton/accessibility/overview.md
index 02aec94abbd..03b3cdbedf3 100644
--- a/docs/controls/dropdownbutton/accessibility/overview.md
+++ b/docs/controls/dropdownbutton/accessibility/overview.md
@@ -1,6 +1,6 @@
 ---
 title: Overview
-page_title: jQuery DropDownButton Documentation - Accessibility
+page_title: jQuery DropDownButton Documentation | DropDownButton Accessibility
 description: "Get started with the jQuery DropDownButton by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
 slug: accessibility_kendoui_dropdownbutton_widget
 position: 1
@@ -10,26 +10,83 @@ position: 1
 
 The DropDownButton is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
 
-For more information, refer to:
+ For more information, refer to:
 * [Keyboard navigation by the Kendo UI DropDownButton]({% slug keynav_kendoui_dropdownbutton_widget %})
 * [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
 
+
+
+
+Out of the box, the Kendo UI for jQuery DropDownButton provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The DropDownButton 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.
+
 ## WAI-ARIA
 
-The widget 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 %}).
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+### Main Button Element
+
+
+The following table summarizes the selectors and attributes supported by the main `button` element of the DropDownButton:
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-menu-button` | `role=button` or `nodeName=button` | Omitted if the `<button>` DOM element is used. |
+|  | `aria-label` | The attribute must be present when no text is initially visible in the button. |
+|  | `aria-expanded=true/false` | Announces the state of the popup visibility. |
+|  | `aria-haspopup=menu` | Indicates the presence of a menu popup. |
+|  | `aria-controls=.k-menu-group id` | Points to the popup element. Builds a relationship between the button and the popup. |
+| `.k-menu-button.k-disabled` | `aria-disabled=true` | Rendered only when the button is disabled and the `disabled` attribute cannot be used. Applicable to the `<button>` or `<input type="button">` elements. |
+
+### Popup Menu Element
+
+
+The following table summarizes the selectors and attributes supported by the popup `menu` element of the DropDownButton:
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-menu-group` | `role=menu` | Announces the `menu` role of the popup. |
+|  | `aria-labelledby=.k-menu-button id` | Points to the `button` element. |
+| `.k-menu-item` | `role=menuitem` | Announces the `menuitem` role of the popup items. |
+
+## Resources
+
+[WAI-ARIA Authoring Practices: Navigation Menu Button Example](https://www.w3.org/WAI/ARIA/apg/example-index/menu-button/menu-button-links.html)
 
 ## Section 508
 
-The DropDownButton 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 %}).
 
-## WCAG 2.2
+The DropDownButton is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
 
-The DropDownButton 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 %}).
+## Testing
 
-## See Also
 
+The DropDownButton has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The DropDownButton has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+The DropDownButton has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+### Test Example
+A live test example of the DropDownButton component could be found here: https://demos.telerik.com/kendo-ui/accessibility/dropdownbutton
+## See Also
 * [Keyboard Navigation by the DropDownButton (Demo)](https://demos.telerik.com/kendo-ui/dropdownbutton/keyboard-navigation)
 * [Keyboard Navigation by the DropDownButton]({% slug keynav_kendoui_dropdownbutton_widget %})
 * [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
-* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/dropdowntree/accessibility/overview.md b/docs/controls/dropdowntree/accessibility/overview.md
new file mode 100644
index 00000000000..94f0343e76b
--- /dev/null
+++ b/docs/controls/dropdowntree/accessibility/overview.md
@@ -0,0 +1,106 @@
+---
+title: Overview
+page_title: jQuery DropDownTree Documentation | DropDownTree Accessibility
+description: "Get started with the jQuery DropDownTree by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
+slug: accessibility_kendoui_dropdowntree_widget
+position: 1
+---
+
+# DropDownTree Accessibility
+
+The DropDownTree is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
+
+ For more information, refer to [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %}).
+
+
+
+
+Out of the box, the Kendo UI for jQuery DropDownTree provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The DropDownTree 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.
+
+## WAI-ARIA
+
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+### DropDownTree Wrapping Element
+
+
+The following table summarizes the selectors and attributes supported by the DropDownTree wrapper element:
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-dropdowntree` | `role=combobox` | Announces the drop-down element of the button. |
+|  | `label for` or `aria-label` or `aria-labelledby` | The input requires an accessible name that will be assigned to it. |
+|  | `aria-haspopup=tree` | Indicates the presence of a popup with a tree navigation. |
+|  | `aria-expanded=true/false` | Announces the state of the popup visibility. |
+|  | `aria-controls=.k-treeview id` | Points to the `treeview` element. Signifies that the `combobox` element controls the `treeview` one. |
+|  | `aria-activedescendent=.k-treeview-item id` | Points to the focused item in the popup. The focused item is changed with the keyboard navigation. If the popup is not visible, the attribute must not point to any element or must be removed. |
+|  | `aria-readonly=true` | The attribute is rendered only when the drop-down is read-only. |
+|  | `aria-autocomplete=list` | The attribute is rendered and the value is set to `list` when the filtering feature is enabled. |
+|  | `aria-invalid=true` | The attribute is rendered only when the drop-down is in a form and announces the valid state of the component. |
+|  | `aria-busy=true` | The attribute is rendered only when the drop-down is loading data. |
+|  | `tabindex=0` | The element must be focusable. |
+| `.k-dropdowntree.k-disabled` | `aria-disabled=true` | The attribute is rendered only when the drop-down is disabled. |
+| `.k-input-button` | `role=button` or `nodeName=button` | The element must either be a `<button>` element or must have `role="button"` assigned. |
+|  | `aria-label` | The button requires an accessible name that will be assigned to it. |
+|  | `tabindex=-1` | The `button` element must not be focusable. |
+
+### Popup Listbox
+
+
+The popup element of the DropDownTree has to implement the WAI-ARIA specification for a Popup List component. The following table summarizes the selectors and attributes supported by the listbox popup of the DropDownTree:
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-animation-container` | `role=region` | When the component container is appended to the `<body>` element of the document, it requires you to assign a `landmark` role to it. Otherwise, it must be appended to an element with an appropriate `landmark` role. |
+|  | `aria-label` or `aria-labelledby` | Provides a label when the container has a `region` role assigned. |
+
+### TreeView
+
+
+The tree that is placed in the `popup` element of the component must implement the specification for a TreeView component.
+
+[TreeView accessibility specification]({{treeview_a11y_link}})
+
+## Resources
+
+[WAI-ARIA Authoring Practices: TreeView Example](https://www.w3.org/WAI/ARIA/apg/example-index/treeview/treeview-navigation)
+
+[WAI-ARIA Authoring Practices: Select-Only Combobox Example](https://www.w3.org/WAI/ARIA/apg/example-index/combobox/combobox-select-only.html)
+
+## Section 508
+
+
+The DropDownTree is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
+
+## Testing
+
+
+The DropDownTree has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The DropDownTree has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+The DropDownTree has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+### Test Example
+A live test example of the DropDownTree component could be found here: https://demos.telerik.com/kendo-ui/accessibility/dropdowntree
+## See Also
+* [Keyboard Navigation by the DropDownTree (Demo)](https://demos.telerik.com/kendo-ui/dropdowntree/keyboard-navigation) 
+* [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/editor/accessibility/overview.md b/docs/controls/editor/accessibility/overview.md
new file mode 100644
index 00000000000..8f5a5889381
--- /dev/null
+++ b/docs/controls/editor/accessibility/overview.md
@@ -0,0 +1,85 @@
+---
+title: Overview
+page_title: jQuery Editor Documentation | Editor Accessibility
+description: "Get started with the jQuery Editor by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
+slug: accessibility_kendoui_editor_widget
+position: 1
+---
+
+# Editor Accessibility
+
+The Editor is accessible by screen readers and provides [`WAI-ARIA`](https://www.w3.org/WAI/ARIA/apg/), [`Section 508`](https://www.section508.gov/), [`WCAG 2.2`](https://www.w3.org/TR/WCAG22/), and keyboard support.
+
+For more information, refer to:
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
+
+
+
+
+Out of the box, the Kendo UI for jQuery Editor provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The Editor 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.
+
+## WAI-ARIA
+
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+
+The Editor component has two distinctive modes - one with `<textarea>` and an `<iframe>` containing an HTML document and another one with only a contenteditable `<div>` (Inline Editor). The inline mode of the Editor does not require any particular ARIA attributes to be present in the widget.
+
+### Editor with textarea
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-iframe` | `tabindex=0` | The element must be part of the page tabsequence. |
+|  | `label for` or `aria-label` or `aria-labelledby` | The component focusable element needs an accessible name to be assigned to it. |
+
+### Editor with contenteditable div
+
+
+When in its inline mode (with a contenteditable `div` element), the editor does not represent a form input. Hence, no additional attributes are required in that scenario.
+
+## Resources
+
+[WAI-ARIA specification for textbox](https://www.w3.org/TR/wai-aria-1.2/#textbox)
+
+## Section 508
+
+
+The Editor is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
+
+## Testing
+
+
+The Editor has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The Editor has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+
+The Editor has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+
+### Test Example
+
+A live test example of the Editor component could be found here: https://demos.telerik.com/kendo-ui/accessibility/editor
+
+## See Also
+
+* [Keyboard Navigation by the Editor (Demo)](https://demos.telerik.com/kendo-ui/editor/keyboard-navigation)
+* [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/expansionpanel/accessibility/overview.md b/docs/controls/expansionpanel/accessibility/overview.md
new file mode 100644
index 00000000000..efacb8e16a6
--- /dev/null
+++ b/docs/controls/expansionpanel/accessibility/overview.md
@@ -0,0 +1,82 @@
+---
+title: Overview
+page_title: jQuery ExpansionPanel Documentation | ExpansionPanel Accessibility
+description: "Get started with the jQuery ExpansionPanel by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
+slug: accessibility_kendoui_expansionpanel_widget
+position: 1
+---
+
+# ExpansionPanel Accessibility
+
+The ExpansionPanel is accessible by screen readers and provides [`WAI-ARIA`](https://www.w3.org/WAI/ARIA/apg/), [`Section 508`](https://www.section508.gov/), [`WCAG 2.2`](https://www.w3.org/TR/WCAG22/), and keyboard support.
+
+For more information, refer to:
+* [Keyboard navigation by the Kendo UI ExpansionPanel]({% slug keynav_kendoui_expansionpanel_widget %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
+
+
+
+
+Out of the box, the Kendo UI for jQuery ExpansionPanel provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The ExpansionPanel 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.
+
+## WAI-ARIA
+
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+### ExpansionPanel Wrapping Element
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-expander-header` | `role=button` | Sets the proper role for the ExpansionPanel component. |
+|  | `aria-controls=.k-expander-content-wrapper id` | Points to the controlled element based on the given `id`. |
+|  | `aria-expanded=true/false` | Indicates the expanded state of the ExpansionPanel. |
+|  | `tabindex=0` | The element should be focusable. |
+| `.k-disabled .k-expander-header` | `aria-disabled=true/false` | The attribute is rendered only when the ExpansionPanel is disabled. |
+
+## Resources
+
+[ARIA Practices: Accordion Pattern](https://www.w3.org/WAI/ARIA/apg/patterns/accordion/)
+
+## Section 508
+
+
+The ExpansionPanel is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
+
+## Testing
+
+
+The ExpansionPanel has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The ExpansionPanel has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+
+The ExpansionPanel has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+
+### Test Example
+
+A live test example of the ExpansionPanel component could be found here: https://demos.telerik.com/kendo-ui/accessibility/expansionpanel
+
+## See Also
+
+* [Keyboard Navigation by the ExpansionPanel (Demo)](https://demos.telerik.com/kendo-ui/expansionpanel/keyboard-navigation)
+* [Keyboard Navigation by the ExpansionPanel]({% slug keynav_kendoui_expansionpanel_widget %})
+* [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/filemanager/accessibility/overview.md b/docs/controls/filemanager/accessibility/overview.md
index bc221a48551..1ac86cbb456 100644
--- a/docs/controls/filemanager/accessibility/overview.md
+++ b/docs/controls/filemanager/accessibility/overview.md
@@ -1,6 +1,6 @@
 ---
 title: Overview
-page_title: jQuery FileManager Documentation - FileManager Accessibility
+page_title: jQuery FileManager Documentation | FileManager Accessibility
 description: "Get started with the jQuery FileManager by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
 slug: accessibility_kendoui_filemanager_widget
 position: 1
@@ -8,31 +8,112 @@ position: 1
 
 # FileManager Accessibility
 
-The FileManager is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
+The FileManager is accessible by screen readers and provides [`WAI-ARIA`](https://www.w3.org/WAI/ARIA/apg/), [`Section 508`](https://www.section508.gov/), [`WCAG 2.2`](https://www.w3.org/TR/WCAG22/), and keyboard support.
 
 For more information, refer to:
 * [Keyboard navigation by the Kendo UI FileManager]({% slug keynav_kendoui_filemanager_widget %})
 * [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
 
+
+
+
+Out of the box, the Kendo UI for jQuery FileManager provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The FileManager 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.
+
 ## WAI-ARIA
 
-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 %}).
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+
+The FileManager component is a composite component that is used to represent file system-like structure. It contains:
+
+
+ - `ToolBar` - on top of the component
+ - `Splitter` - it separates the panes in the component
+ - `TreeView` - in its left pane.
+ - `Breadcrumb` - in the top of its center pane
+ - `ListView` or a `Grid` - in its center pane.
+ - `k-filemanager-preview` element - in its right pane
+
+
+Each component implements its own dedicated ARIA spec.
+
+
+The FileManager component integrates the ToolBar component and follows its WAI-ARIA spec:
+
+[ToolBar accessibility specification]({{toolbar_a11y_link}})
+
+
+The component that organizes the inner structure of the FileManager is a Splitter:
+
+[Splitter accessibility specification]({{splitter_a11y_link}})
+
+
+The main navigation component in the FileManager is the TreeView:
+
+[TreeView accessibility specification]({{treeview_a11y_link}})
+
+
+The helper navigation component in the FileManager is the Breadcrumb:
+
+[Breadcrumb accessibility specification]({{breadcrumb_a11y_link}})
+
+
+The component placed in the main pain of the FileManager can be a selectable ListView:
+
+[ListView accessibility specification]({{listview_a11y_link}})
+
+
+or it can be a Grid:
+
+[Grid accessibility specification]({{grid_a11y_link}})
+
+
+Apart from that the `.k-filemanager-preview` element must be focusable, so that its content would be comunicated to the users:
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-filemanager-preview` | `tabindex=0` | The element must be focusable, so that its content would be comunicated to the users. |
 
 ## Section 508
 
-The FileManager 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 %}).
 
-## WCAG 2.2
+The FileManager is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
 
-The FileManager 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/).
+## Testing
 
-For more information, refer to:
-* [WCAG 2.2 support by the FileManager (demo)](https://demos.telerik.com/kendo-ui/filemanager/index)
-* [WCAG 2.2 compliance in Kendo UI for jQuery]({% slug section508_wcag21_accessibility_support %})
+
+The FileManager has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The FileManager has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+
+The FileManager has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+
+### Test Example
+
+A live test example of the FileManager component could be found here: https://demos.telerik.com/kendo-ui/accessibility/filemanager
 
 ## See Also
 
 * [Keyboard Navigation by the FileManager (Demo)](https://demos.telerik.com/kendo-ui/filemanager/keyboard-navigation)
-* [Keyboard Navigation by the Grid]({% slug keynav_kendoui_grid_widget %})
+* [Keyboard navigation by the FileManager]({% slug keynav_kendoui_filemanager_widget %})
 * [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
-* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/filter/accessibility/overview.md b/docs/controls/filter/accessibility/overview.md
index 4a64010a226..54fbdb89da7 100644
--- a/docs/controls/filter/accessibility/overview.md
+++ b/docs/controls/filter/accessibility/overview.md
@@ -1,34 +1,87 @@
 ---
 title: Overview
-page_title: jQuery Filter Documentation - Filter Accessibility
-description: "Get started with the jQuery Filter and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
+page_title: jQuery Filter Documentation | Filter Accessibility
+description: "Get started with the jQuery Filter by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
 slug: accessibility_kendoui_filter_widget
 position: 1
 ---
 
 # Filter Accessibility
 
-The Filter is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
+The Filter is accessible by screen readers and provides [`WAI-ARIA`](https://www.w3.org/WAI/ARIA/apg/), [`Section 508`](https://www.section508.gov/), [`WCAG 2.2`](https://www.w3.org/TR/WCAG22/), and keyboard support.
 
 For more information, refer to:
 * [Keyboard navigation by the Kendo UI Filter]({% slug keynav_filter_jquery %})
 * [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
 
+
+
+
+Out of the box, the Kendo UI for jQuery Filter provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The Filter 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.
+
 ## WAI-ARIA
 
-The widget 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 %}).
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+
+The Filter component represents visually the structure of a filter object. As the filter object can contain nested objects, that hierarchical structure must be represented in the accessibility tree by the `role=tree` assigned to the component.
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-filter-container` | `role=tree` | Describes the hierarchical structure of the Filter component. |
+|  | `aria-label` | Specifies a label for the Filter component. |
+| `.k-filter-group-main,.k-filter-item` | `role=treeitem` | Each FilterGroup and FilterExpression represent a separate `treeitem` in the Filter component structure. |
+| `.k-filter-lines` | `role=group` | Represents a group if items in the Filter component. |
+| `.k-toolbar` | `role=toolbar` | The role represents a collection of tools. |
+|  | `aria-label` | Specifies a label for the toolbar. |
+
+
+Each toolbar in the Filter should follow the specification for a ToolBar component. The elements inside the FilterGroup follow the ARIA specification applicable to their specific roles.
+
+## Resources
+
+[WAI-ARIA specification for toolbar](https://www.w3.org/TR/wai-aria-1.2/#toolbar)
 
 ## Section 508
 
-The Filter 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 %}).
 
-## WCAG 2.2
+The Filter is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
 
-The Filter 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 %})
+## Testing
+
+
+The Filter has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The Filter has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+
+The Filter has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+
+### Test Example
+
+A live test example of the Filter component could be found here: https://demos.telerik.com/kendo-ui/accessibility/filter
 
 ## See Also
 
 * [Keyboard Navigation by the Filter (Demo)](https://demos.telerik.com/kendo-ui/filter/keyboard-navigation)
-* [Keyboard Navigation by the Filter]({% slug keynav_filter_jquery %})
+* [Keyboard navigation by the Filter]({% slug keynav_filter_jquery %})
 * [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
-* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/flatcolorpicker/accessibility/overview.md b/docs/controls/flatcolorpicker/accessibility/overview.md
index b403b14005f..a3b527c2268 100644
--- a/docs/controls/flatcolorpicker/accessibility/overview.md
+++ b/docs/controls/flatcolorpicker/accessibility/overview.md
@@ -1,34 +1,91 @@
 ---
 title: Overview
-page_title: jQuery FlatColorPicker Documentation - FlatColorPicker Accessibility
-description: "Get started with the jQuery FlatColorPicker and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
+page_title: jQuery FlatColorPicker Documentation | FlatColorPicker Accessibility
+description: "Get started with the jQuery FlatColorPicker by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
 slug: accessibility_kendoui_flatcolorpicker_widget
 position: 1
 ---
 
 # FlatColorPicker Accessibility
 
-The FlatColorPicker is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
+The FlatColorPicker is accessible by screen readers and provides [`WAI-ARIA`](https://www.w3.org/WAI/ARIA/apg/), [`Section 508`](https://www.section508.gov/), [`WCAG 2.2`](https://www.w3.org/TR/WCAG22/), and keyboard support.
+
+> The described level of compliance is achievable with the [`Ocean Blue A11y Accessibility Swatch`](/accessibility/themes-swatches).
 
 For more information, refer to:
 * [Keyboard navigation by the Kendo UI FlatColorPicker]({% slug keynav_flatcolorpicker_jquery %})
 * [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
 
+
+
+
+Out of the box, the Kendo UI for jQuery FlatColorPicker provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The FlatColorPicker 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.
+
 ## WAI-ARIA
 
-The widget 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 %}).
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+
+The FlatColorPicker contains in itself ColorGradient, ColorPalette, a UI to switch between them, Cancel, Apply, and a button to reset its value. All the containing elements must implement their own specification apart from the ColorGradient element where some changes are required.
+
+### FlatColorPicker Wrapping Element
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-flatcolorpicker` | `role=textbox` | The focusable wrapper of the component should be considered a `textbox`. That signifies it has a value that could be submitted. |
+|  | `aria-label` or `aria-labelledby` | The component needs an accessible name to be assigned to it. Must also include the currently selected value in the component. |
+|  | `aria-invalid=true` | Attribute is rendered only when the selected value in the component is not valid against the current validation rules. |
+|  | `tabindex=0` | The element must be focusable. |
+| `.k-flatcolorpicker.k-disabled` | `aria-disabled=true` | Attribute is rendered only when the ColorPalette is disabled. |
+
+### ColorGradient
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-colorgradient` | `role=none/` | The ColorGradient element must have its role removed. |
+|  | `aria-label` | The ColorGradient element must have its `aria-label` attribute removed. |
+|  | `tabindex=-1/` | The ColorGradient must be removed from the page tab sequence. |
 
 ## Section 508
 
-The FlatColorPicker 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 %}).
 
-## WCAG 2.2
+The FlatColorPicker is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
 
-The FlatColorPicker 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 %})
+## Testing
+
+
+The FlatColorPicker has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The FlatColorPicker has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+
+The FlatColorPicker has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+
+### Test Example
+
+A live test example of the FlatColorPicker component could be found here: https://demos.telerik.com/kendo-ui/accessibility/flatcolorpicker
 
 ## See Also
 
 * [Keyboard Navigation by the FlatColorPicker (Demo)](https://demos.telerik.com/kendo-ui/flatcolorpicker/keyboard-navigation)
 * [Keyboard Navigation by the FlatColorPicker]({% slug keynav_flatcolorpicker_jquery %})
 * [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
-* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/floatingactionbutton/accessibility/overview.md b/docs/controls/floatingactionbutton/accessibility/overview.md
index 6ce412c4d74..5041d664080 100644
--- a/docs/controls/floatingactionbutton/accessibility/overview.md
+++ b/docs/controls/floatingactionbutton/accessibility/overview.md
@@ -1,6 +1,6 @@
 ---
 title: Overview
-page_title: jQuery FloatingActionButton Documentation - FloatingActionButton Accessibility
+page_title: jQuery FloatingActionButton Documentation | FloatingActionButton Accessibility
 description: "Get started with the jQuery FloatingActionButton by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
 slug: accessibility_kendoui_floatingactionbutton_widget
 position: 1
@@ -8,27 +8,85 @@ position: 1
 
 # FloatingActionButton Accessibility
 
-The FloatingActionButton is accessible by screen readers and provides WAI-ARIA, Section 508, WCAG 2.2, and keyboard support.
+The FloatingActionButton is accessible by screen readers and provides [`WAI-ARIA`](https://www.w3.org/WAI/ARIA/apg/), [`Section 508`](https://www.section508.gov/), [`WCAG 2.2`](https://www.w3.org/TR/WCAG22/), and keyboard support.
+
+> The described level of compliance is achievable with the [`Ocean Blue A11y Accessibility Swatch`](/accessibility/themes-swatches).
 
 For more information, refer to:
 * [Keyboard navigation by the Kendo UI FloatingActionButton]({% slug keynav_floatingactionbutton_jquery %})
 * [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
 
+
+
+
+Out of the box, the Kendo UI for jQuery FloatingActionButton provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The FloatingActionButton 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.
+
 ## WAI-ARIA
 
-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 %}).
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+
+The FloatingActionButton features two distinct modes of operation: button-only and button-with-menu.
+
+### Button-Only Mode
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-fab` | `role=button` or `nodeName=button` | Omitted if the `<button>` DOM element is used. |
+|  | `aria-label` or `title` | The attribute must be present when no text is initially visible in the button. |
+| `.k-fab.k-disabled` | `aria-disabled=true` | Rendered only when the button is disabled and the `disabled` attribute cannot be used. Applicable for the `<button>` or `<input type="button">` elements. |
+
+### Button-with-Menu Mode
+
+
+In the button-with-menu mode, the FloatingActionButton must implement the specification for the DropDownButton component.
+
+[DropDownButton accessibility specification]({{dropdownbutton_a11y_link}})
+
+## Resources
+
+[WAI-ARIA Authoring Practices: Navigation Menu Button Example](https://www.w3.org/WAI/ARIA/apg/example-index/menu-button/menu-button-links.html)
 
 ## Section 508
 
-The FloatingActionButton 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 %}).
 
-## WCAG 2.2
+The FloatingActionButton is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
+
+## Testing
+
+
+The FloatingActionButton has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
 
-The FloatingActionButton 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 %})
+The FloatingActionButton has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+
+The FloatingActionButton has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+
+### Test Example
+
+A live test example of the FloatingActionButton component could be found here: https://demos.telerik.com/kendo-ui/accessibility/floatingactionbutton
 
 ## See Also
 
 * [Keyboard Navigation by the FloatingActionButton (Demo)](https://demos.telerik.com/kendo-ui/floatingactionbutton/keyboard-navigation)
 * [Keyboard Navigation by the FloatingActionButton]({% slug keynav_floatingactionbutton_jquery %})
 * [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
-* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/controls/gantt/accessibility/overview.md b/docs/controls/gantt/accessibility/overview.md
new file mode 100644
index 00000000000..62c6045d566
--- /dev/null
+++ b/docs/controls/gantt/accessibility/overview.md
@@ -0,0 +1,261 @@
+---
+title: Overview
+page_title: jQuery Gantt Documentation | Gantt Accessibility
+description: "Get started with the jQuery Gantt by Kendo UI and learn about its accessibility support for WAI-ARIA, Section 508, and WCAG 2.2."
+slug: accessibility_kendoui_gantt_widget
+position: 1
+---
+
+# Gantt Accessibility
+
+The Gantt is accessible by screen readers and provides [`WAI-ARIA`](https://www.w3.org/WAI/ARIA/apg/), [`Section 508`](https://www.section508.gov/), [`WCAG 2.2`](https://www.w3.org/TR/WCAG22/), and keyboard support.
+
+> The described level of compliance is achievable with the [`Ocean Blue A11y Accessibility Swatch`](/accessibility/themes-swatches).
+
+For more information, refer to:
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
+
+
+
+
+Out of the box, the Kendo UI for jQuery Grid provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
+
+
+The Grid 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.
+
+## WAI-ARIA
+
+
+This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
+
+
+The Grid is a composite component that consists of 4 logically separated structural elements:
+
+
+ - Toolbar (`role=toolbar`);
+ - Group header (`role=toolbar`);
+ - Data Grid (`role=grid`);
+ - Pager (`role=application`);
+
+### Grid Toolbar
+
+
+Grid Toolbar follows the specification of the ToolBar component.
+
+[ToolBar accessibility specification]({{toolbar_a11y_link}})
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-toolbar` | `role=toolbar` | The toolbar is a collection of command buttons and inputs. |
+|  | `aria-label` | Clarifies the purpose of the toolbar. |
+|  | `aria-controls=.k-grid-content>table id` | Pointing to the id of the element with `role=grid`. |
+
+### Grid Grouping Header
+
+
+Grid Grouping Header follows the specification of the ToolBar component.
+
+[ToolBar accessibility specification]({{toolbar_a11y_link}})
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grouping-header` | `role=toolbar` | The Grouping header is a ToolBar (collection of buttons). |
+|  | `aria-label` | Clarifies the purpose of the header. |
+|  | `aria-controls=.k-grid-content>table id` | Pointing to the id of the element with `role=grid`. |
+| `.k-grouping-header .k-chip-list .k-chip` | `role=button` | If the element used is not `<button>`, then the role must be specified. |
+| `.k-grouping-header .k-chip-list` | `role=none/` | The ChipList default listbox role is removed to keep the toolbar --> button roles hierarchy. |
+|  | `title` | Present on the element or its child if sorting is enabled for that field. |
+
+### Data Grid (excluding Toolbars and Pager)
+
+
+The element with `role=grid` must not include the ToolBar and the Pager elements as those do not belong to the `role=grid` element itself.
+
+
+In the Kendo jQuery Grid, the `role=grid` is assigned to the `<table>` in the `k-grid-content` element.
+
+#### Grid element
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid:not(.k-treelist) .k-grid-content>table` | `role=grid` | The role specifies the element is a Data Grid. |
+| `.k-grid-aria-root` | `aria-colcount` | The total number of columns in the Grid. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. If the total number of columns is unknown, the value of `aria-colcount` must be set to -1. |
+|  | `aria-rowcount` | The total number of rows in the table (header rows + master rows + detail rows + data rows + footer rows + aggregates rows). Needed only when Paging (and more that 1 page is present in the component), Virtual rows, or Master/Detail rows (Hierarchical Grid, Detail Template Grid) are enabled. If data is also Grouped, the proper number of all rows could not be calculated. In that case the value must be set to -1. |
+
+
+In scenarios when master and detail rows are present in the Grid (Hierarchical Grid, Detail Template Grid), the `aria-rowcount` (the total number of rows) must be calculated: 2 * (total number of items) + header rows + footer rows. That is because for each item in the Grid there is a master row and a detail row duplicating this way the number of rows.
+
+
+If the Grid is composed of a single table (there is no separate `<table>` element for its header), no `role` attributes should be set on its inner elements(`<thead>`, `<body>`, `<tr>`, `<th>`, and `<td>`). Their semantic meaning will be used instead.
+
+#### Grid header
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-header-wrap>table` | `role=presentation/none` | Negates the default semantic role of the `<table>` element. |
+| `.k-grid-header-wrap>table>thead` | `role=rowgroup` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `id` | Id must be present on the element, so that it can be properly referenced in the `role=grid` element. |
+| `.k-grid-header-wrap>table>thead>tr` | `role=row` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-rowindex` | Row number including all headers, data (including master and detail) rows, and footers starting from 1. Needed only when Paging (and more that 1 page is present in the component), Virtual rows, or Master/Detail rows (Hierarchical Grid, Detail Template Grid) are enabled. If data is also Grouped, the proper indexing could not be calculated. Hence, the attribute must not be set. |
+| `.k-grid-header-wrap>table>thead>tr>th:not(.k-hierarchy-cell):not(.k-group-cell):not(.k-drag-cell)` | `role=columnheader` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-sort=none/ascending/descending` | Present if sorting is enabled for that column. |
+|  | `title` or `aria-label` | Present on the element or its child if sorting is enabled for that field. |
+|  | `aria-colindex` | Col number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans. |
+|  | `aria-haspopup=dialog` | The attribute must be present if the column has a ColumnMenu. |
+|  | `aria-haspopup=dialog` | The attribute must be present if the column has a FilterMenu and no ColumnMenu. |
+
+#### Grid locked header
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-header-locked>table` | `role=none/presentation` | Negates the default semantic role of the `<table>` element. |
+| `.k-grid-header-locked>table>thead>tr>th` | `role=columnheader` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `title` or `aria-label` | Present on the element or its child if sorting is enabled for that field. |
+|  | `aria-colindex` | Col number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans. |
+|  | `id` | Id must be present on the element, so that it can be properly referenced in the respective `<tr>` element in the `k-grid-header-wrap <thead>` element. |
+| `.k-grid-header-locked .k-header[data-role='columnsorter']` | `aria-sort=none/ascending/descending` | Present if sorting is enabled for that column. |
+| `.k-grid-header-locked .k-header[data-role='columnmenu']` | `aria-haspopup=menu` | The attribute must be present if the column has a ColumnMenu. |
+| `.k-grid-header-locked .k-header[data-role='filtermenu']` | `aria-haspopup=dialog` | The attribute must be present if the column has a FilterMenu and no ColumnMenu. |
+
+#### Grid filter row
+
+
+Even if part of the `<thead>`, the Filter row must be composed of `<td>` elements.
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-header-wrap>table>thead>tr.k-filter-row>td` | `role=gridcell` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-label` | Has a label indicating that the cell is part of a filter row. |
+
+#### Grid locked filter row
+
+
+Even if part of the `<thead>`, the Filter row must be composed of `<td>` elements.
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-header-locked>table>thead>tr.k-filter-row>td` | `role=gridcell` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-label` | Has a label indicating that the cell is part of a filter row. |
+|  | `id` | Id must be present on the element, so that it can be properly referenced in the respective `<tr>` filter row element in the `k-grid-header-wrap <thead>` element. |
+
+#### Grid filter menu
+
+
+Implements the FilterMenu specification.
+
+[FilterMenu accessibility specification]({{filtermenu_a11y_link}})
+
+#### Grid column menu
+
+
+Implements the ColumnMenu specification.
+
+[ColumnMenu accessibility specification]({{columnmenu_a11y_link}})
+
+#### Grid content
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid:not(.k-treelist) .k-grid-content>table` | `role=grid` | This is the main focusable Grid element (see above). |
+| `.k-grid-content>table>tbody` | `role=rowgroup` | Required as the owner `<table>` element has its semantic role removed. |
+| `.k-grid-content>table>tbody>tr` | `role=row` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-rowindex` | Row number including all headers, data (including master and detail) rows, and footers starting from 1. Needed only when Paging (and more that 1 page is present in the component), Virtual rows, or Master/Detail rows (Hierarchical Grid, Detail Template Grid) are enabled. If data is also Grouped, the proper indexing could not be calculated. Hence, the attribute must not be set. In scenarios when master and detail rows are present in the Grid (Hierarchical Grid, Detail Template Grid), both master and detail rows must always be indexed. For example, if the first master row has `aria-rowindex=2`, even if its detail row is not present in the DOM, the next master row must have `aria-rowindex=4`. When rendered, the detail row must receive the missing index between the two master rows. In this example it would be `aria-rowindex=3`. |
+| `.k-grid-content tr.k-selected` | `aria-selected=true` | Set on the currently selected row(s). Only used wen selection mode is set to `row`. |
+| `.k-grid-content-locked + .k-grid-content tr` | `aria-owns` | If the Grid contains locked columns, the attribute points to the ids of the locked cells belonging visually to the same row. |
+| `.k-grid-content>table>tbody>tr>td` | `role=gridcell` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-colindex` | Col number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans. |
+| `td.k-selected` | `aria-selected=true` | Set on the currently selected cell(s). Only used when selection mode is set to cell. |
+| `.k-master-row .k-hierarchy-cell,.k-grouping-row>td` | `aria-expanded=true/false` | Optionally for cells holding grouping criteria values and for Master row cells in Detail template scenario. |
+| `.k-drag-cell` | `aria-label` | Must be present in a Drag Row scenario on the cell containing the drag handle. |
+
+#### Grid locked content
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-content-locked>table` | `role=none/presentation` | Negates the default semantic role of the `<table>` element. |
+| `.k-grid-content-locked>table>tbody>tr>td` | `role=gridcell` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-colindex` | Col number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans. |
+|  | `id` | Id must be present on the element, so that it can be properly referenced in the respective `<tr>` element in the `k-grid-content <tbody>` element. |
+
+#### Grid footer
+
+
+The Aggregates totals are placed within a `<tfoot>` element in the Content `<table>`.
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-footer-wrap>table` | `role=none/presentation` | Negates the default semantic role of the `<table>` element. |
+| `tfoot` | `role=rowgroup` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `id` | Id must be present on the element, so that it can be properly referenced in the `role=grid` element. |
+| `tfoot>tr` | `role=row` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-rowindex` | Row number including all headers, data (including master and detail) rows, and footers starting from 1. Footer rows are always the last ones in a Grid. Needed only when Paging (and more that 1 page is present in the component), Virtual rows, or Master/Detail rows (Hierarchical Grid, Detail Template Grid) are enabled. If data is also Grouped, the proper indexing could not be calculated. Hence, the attribute must not be set. |
+| `tfoot>tr>td` | `role=gridcell` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-colindex` | Col number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans. |
+
+#### Grid locked footer
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-footer-locked>table` | `role=none/presentation` | Negates the default semantic role of the `<table>` element. |
+| `.k-grid-footer-locked>table>tfoot>tr>td` | `role=gridcell` | Required as the owner `<table>` element has its semantic role removed. |
+|  | `aria-colindex` | Col number, based on leaf columns, starting from 1. Needed only for Virtual columns and Hidden columns scenarios, when not all columns are rendered in the DOM. Otherwise, can be interpreted from the DOM structure. Can be calculated by summing previous columns colspans. |
+|  | `id` | Id must be present on the element, so that it can be properly referenced in the respective `<tr>` element in the `k-grid-footer-wrap <tfoot>` element. |
+
+### Pager
+
+
+For the Grid Pager WAI-ARIA spec, please review the Pager component.
+
+[Pager accessibility specification]({{pager_a11y_link}})
+
+#### Grid selection aggregates
+
+
+The selection aggregates are placed within a `.k-grid-selection-aggregates` element after the Grid `.k-grid-aria-root` element.
+
+| Selector | Attribute | Usage |
+| -------- | --------- | ----- |
+| `.k-grid-selection-aggregates` | `aria-live=polite` | Ensures that changes in the calculated selection aggregates are announced by assistive technologies. |
+
+## Resources
+
+[WAI-ARIA specification for grid](https://www.w3.org/TR/wai-aria-1.2/#grid)
+
+## Section 508
+
+
+The Grid is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
+
+## Testing
+
+
+The Grid has been extensively tested automatically with [axe-core](https://github.com/dequelabs/axe-core) and manually with the most popular screen readers.
+
+> To report any accessibility issues, contact the team through the [Telerik Support System](https://www.telerik.com/account/support-center).
+
+### Screen Readers
+
+
+The Grid has been tested with the following screen readers and browsers combinations:
+
+| Environment | Tool |
+| ----------- | ---- |
+| Firefox | NVDA |
+| Chrome | JAWS |
+| Microsoft Edge | JAWS |
+
+
+
+### Automated Testing
+
+The Gantt has been tested with [axe-core](https://github.com/dequelabs/axe-core).
+
+### Test Example
+
+A live test example of the Gantt component could be found here: https://demos.telerik.com/kendo-ui/accessibility/gantt
+
+## See Also
+
+* [Keyboard Navigation by the Gantt (Demo)](https://demos.telerik.com/kendo-ui/gantt/keyboard-navigation)
+* [Keyboard Support in Kendo UI for jQuery]({% slug keyboard_shortcuts_accessibility_support %})
+* [Accessibility in Kendo UI for jQuery]({% slug overview_accessibility_support_kendoui %})
\ No newline at end of file
diff --git a/docs/knowledge-base/keep-step-numbers-visible-kendo-ui-wizard.md b/docs/knowledge-base/keep-step-numbers-visible-kendo-ui-wizard.md
new file mode 100644
index 00000000000..f92c15b2b3a
--- /dev/null
+++ b/docs/knowledge-base/keep-step-numbers-visible-kendo-ui-wizard.md
@@ -0,0 +1,70 @@
+---
+title: Keeping Step Numbers Visible in Completed Steps for Kendo UI Wizard
+description: Learn how to maintain the visibility of step numbers on the Kendo UI Wizard component for completed steps, using custom logic.
+type: how-to
+page_title: How to Keep Step Numbers Visible on Completed Steps in Kendo UI Wizard
+slug: keep-step-numbers-visible-kendo-ui-wizard
+tags: kendo-ui, wizard, stepper, activate-event, custom-logic
+res_type: kb
+ticketid: 1647918
+---
+
+## Environment
+
+| Product | Kendo UI for jQuery Wizard / 2024.1.130 | 
+| --- | --- |
+
+## Description
+
+I want to keep the numbers on the Wizard Stepper visible for completed steps instead of changing them to check marks. 
+
+This KB article also answers the following questions:
+- How can I display step numbers for completed steps in the Kendo UI Wizard?
+- Is it possible to prevent the Wizard Stepper from showing check marks for completed steps?
+- What method can I use to show numerical indicators for finished steps in the Wizard component?
+
+## Solution
+
+To keep the step numbers visible for completed steps in the [Kendo UI Wizard](https://docs.telerik.com/kendo-ui/api/javascript/ui/wizard/events/activate), utilize custom logic inside the `activate` event handler. The following example demonstrates how to replace the check marks with the corresponding step numbers:
+
+```javascript
+activate: function(e) {
+    $("span.k-svg-i-check").each(function(idx, el) {
+        var step = idx + 1;
+        $(el).replaceWith("<span class='k-step-indicator-text'>" + step + "</span>" );
+    })
+},
+```
+
+This solution iterates through each element marked with a checkmark and replaces it with a span element that displays the step number. 
+
+```dojo
+    <div id="wizard"></div>
+    <script>
+      $("#wizard").kendoWizard({
+        steps: [
+          {
+            title: "Initial step"
+          },{
+            title: "Second step"
+          },
+          {
+            title: "Third step"
+          }
+        ],
+        activate: function(e) {
+          $("span.k-svg-i-check").each(function(idx, el) {
+            var step = idx+1;
+            $(el).replaceWith("<span class='k-step-indicator-text'>"+ step + "</span>" );
+          })
+        }
+      });
+    </script>
+```
+
+## See Also
+
+- [Wizard Activate Event Documentation](https://docs.telerik.com/kendo-ui/api/javascript/ui/wizard/events/activate)
+- [Wizard Overview (Demo)](https://demos.telerik.com/kendo-ui/wizard/index)
+
+---