Sync with Kendo UI Professional

Author: kendo-bot

docs-aspnet/html-helpers/conversational-ui/aiprompt/accessibility/overview.md

@@ -14,10 +14,12 @@ The AIPrompt is compliant with the [Web Content Accessibility Guidelines (WCAG)
 
 ## WAI-ARIA
 
+
 This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
 
 ### AIPrompt
 
+
 The AIPrompt component is a composite one and integrates the accessibility of the Toolbar, TextArea, Card List container.
 
 ### TextArea Component
@@ -26,15 +28,16 @@ The AIPrompt component is a composite one and integrates the accessibility of th
 
 ### Prompt Suggestion Component
 
-The Prompt Suggestion list implements roving tabindex navigation. Meaning that only one suggestion has `tabindex=0`. The display of the suggestion list is controlled by the expand button.
+
+The Prompt suggestion list implements roving tabindex navigation. Meaning that only one suggestion has tabindex=0. The display of the suggestion list is controlled by the expand button.
 
 | Selector | Attribute | Usage |
 | -------- | --------- | ----- |
 | `.k-prompt-expander .k-button` | `aria-controls=.k-prompt-expander-content id` | Points to the controlled element based on the given `id`. |
 |  | `aria-expanded=true/false` | Indicates the expanded state of the prompt expander content. |
 | `.k-prompt-expander .k-prompt-expander-content` | `role=list` | Indicates that the suggestion container element is a list. |
 | `.k-prompt-expander .k-prompt-suggestion` | `role=listitem` | Indicates that the suggestion element is a listitem. |
-|  | `tabindex=0/-1` | The element must be focusable. |
+|  | `tabindex=0/-1` | The element should be focusable. |
 
 ### Toolbar Component
 
@@ -46,16 +49,19 @@ The Prompt Suggestion list implements roving tabindex navigation. Meaning that o
 
 ## Section 508
 
-The AIPrompt is fully compliant with the [Section 508 requirements](https://www.section508.gov/).
+
+The AIPrompt is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
 
 ## Testing
 
+
 The AIPrompt 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 AIPrompt has been tested with the following screen readers and browsers combinations:
 
 | Environment | Tool |
@@ -64,6 +70,8 @@ The AIPrompt has been tested with the following screen readers and browsers comb
 | Chrome | JAWS |
 | Microsoft Edge | JAWS |
 
+
+
 ### Test Example
 
 To test the AIPrompt component, refer to the [ActionSheet Accessibility Demo](https://demos.telerik.com/{{ site.platform }}/accessibility/aiprompt).

docs-aspnet/html-helpers/conversational-ui/chat/accessibility/overview.md

@@ -10,10 +10,12 @@ position: 1
 
 Out of the box, the {{ site.product }} Chat provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.
 
+
 The Chat 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.
 
 ## WAI-ARIA
 
+
 This section lists the selectors, attributes, and behavior patterns supported by the component and its composite elements, if any.
 
 | Selector | Attribute | Usage |
@@ -40,16 +42,19 @@ Chat ToolBar follows the specification for the the ToolBar component.
 
 ## Section 508
 
-The Chat is fully compliant with the [Section 508 requirements](https://www.section508.gov/).
+
+The Chat is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
 
 ## Testing
 
+
 The Chat 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 Chat has been tested with the following screen readers and browsers combinations:
 
 | Environment | Tool |
@@ -58,6 +63,8 @@ The Chat has been tested with the following screen readers and browsers combinat
 | Chrome | JAWS |
 | Microsoft Edge | JAWS |
 
+
+
 ### Test Example
 
 To test the Chat component, refer to the [Chat Accessibility Demo](https://demos.telerik.com/{{ site.platform }}/accessibility/chat).

docs-aspnet/html-helpers/data-management/filemanager/accessibility/overview.md

@@ -8,67 +8,86 @@ position: 1
 
 # FileManager Accessibility
 
+
+
+
+
 Out of the box, the {{ site.product }} 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 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.
 
 ## WAI-ARIA
 
+
 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
+
+ - `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]({% slug accessibility_toolbar_overview %})
 
+
 The component that organizes the inner structure of the FileManager is a Splitter:
 
 [Splitter accessibility specification]({% slug accessbility_aspnetcore_splitter %})
 
+
 The main navigation component in the FileManager is the TreeView:
 
 [TreeView accessibility specification]({% slug accessibility_aspnetcore_treeview %})
 
+
 The helper navigation component in the FileManager is the Breadcrumb:
 
 [Breadcrumb accessibility specification]({% slug accessibility_aspnetcore_breadcrumb %})
 
+
 The component placed in the main pain of the FileManager can be a selectable ListView:
 
 [ListView accessibility specification]({% slug accessibility_htmlhelpers_listview %})
 
+
 or it can be a Grid:
 
 [Grid accessibility specification]({% slug accessibility_aspnetcore_grid %})
 
-Apart from that, the `.k-filemanager-preview` element must be focusable so that its content can be communicated to the users:
+
+Apart from that the `.k-filemanager-preview` element must be focusable, so that its content would be communicated to the users:
 
 | Selector | Attribute | Usage |
 | -------- | --------- | ----- |
-| `.k-filemanager-preview` | `tabindex=0` | The element must be focusable, so that its content can be communicated to the users. |
+| `.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 fully compliant with the [Section 508 requirements](https://www.section508.gov/).
+
+The FileManager is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
 
 ## Testing
 
+
 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 |
@@ -77,6 +96,8 @@ The FileManager has been tested with the following screen readers and browsers c
 | Chrome | JAWS |
 | Microsoft Edge | JAWS |
 
+
+
 ### Test Example
 
 To test the FileManager component, refer to the [FileManager Accessibility Demo](https://demos.telerik.com/{{ site.platform }}/accessibility/filemanager).

docs-aspnet/html-helpers/data-management/filter/accessibility/overview.md

@@ -8,14 +8,21 @@ position: 1
 
 # Filter Accessibility
 
+
+
+
+
 Out of the box, the {{ site.product }} 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 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.
 
 ## WAI-ARIA
 
+
 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 |
@@ -27,24 +34,28 @@ The Filter component represents visually the structure of a filter object. As th
 | `.k-toolbar` | `role=toolbar` | The role represents a collection of tools. |
 |  | `aria-label` | Specifies a label for the toolbar. |
 
-Each toolbar in the Filter must follow the specification for a ToolBar component. The elements inside the FilterGroup follow the ARIA specification applicable to their specific roles.
+
+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 fully compliant with the [Section 508 requirements](https://www.section508.gov/).
+
+The Filter is fully compliant with the [Section 508 requirements](http://www.section508.gov/).
 
 ## 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 |
@@ -53,6 +64,8 @@ The Filter has been tested with the following screen readers and browsers combin
 | Chrome | JAWS |
 | Microsoft Edge | JAWS |
 
+
+
 ### Test Example
 
 To test the Filter component, refer to the [Filter Accessibility Demo](https://demos.telerik.com/{{ site.platform }}/accessibility/filter).