Sync with Kendo UI Professional

Author: kendo-bot

docs-aspnet/accessibility/accessibility-compliance-table.html

@@ -1,21 +1,45 @@
 ---
-title: Accessibility Compliance
-page_title: Accessibility Support
-description: "A list of the {{ site.product }} components in terms of the accessibility and keyboard navigation support they provide."
+title: Compliance
+page_title: Accessibility Compliance
+description: "Compliance with the accessibility standards and requirements in the {{ site.product }} suite."
 slug: compliance_accessibility
-position: 90
+position: 2
 ---
 
-# {{ site.product }} Accessibility {% if site.core %}Compliance{% else %}Support{% endif %}
+# Accessibility Standards Compliance
 
-<a href="assets/KendoUI-VPAT2.4RevINT.doc" download>Here</a> you can download the latest version of the VPAT Template, describing the {{ site.product }} accessibility compliance state.
+This article lists the accessibility compliance of the {{ site.product }} components.
 
-The following table lists the {{ site.product }} components which support accessibility and keyboard navigation options.
+## Accessibility Conformance Report
+
+The <a href="https://www.section508.gov/sell/acr/" target="_blank">Accessibility Conformance Report (ACR)</a> is a document that explains how information and communication technology products such as software, hardware, electronic content, and support documentation conform to leading global accessibility standards. {{ site.product }} provides an ACR through the <a href="https://www.itic.org/policy/accessibility/vpat" target="_blank">Voluntary Product Accessibility Template (VPAT®)</a>.
+
+>tip Download the latest version of the <a href="assets/kendo-ui-vpat2.4.doc" download>{{ site.product }} Accessibility Conformance Report</a>.
+
+## Compliance Table
+
+The table below specifies the level of WCAG 2.2 compliance of each {{ site.product }} component.
+
+* The *Accessibility Example* column links to component-specific accessibility demo. For general information on how the keyboard support works, see the [Keyboard Navigation]({%slug overview_accessibility%}#keyboard-navigation) section.
+* The *Accessibility Documentation* column links to component-specific details and information about WAI-ARIA attributes.
+* For information about **Section 508** of the US Rehabilitation Act, the **European Accessibility Act** in the EU, or any other national accessibility legislation, see section [Legal and Technical Compliance]({%slug overview_accessibility%}#legal-and-technical-compliance).
+
+Also check the [notes below the table](#accessibility-compliance-notes).
 
 {% include_relative accessibility-compliance-table.html %}
 
-> The DropDownTree widget will be identified as not compliant to the WAI-ARIA spec when tested with static HTML analyzer if there is no selection in the widget and the `placeholder` configuration is not used. That is because the DropDownTree wrapper element, which has `role="listbox"` will not contain any `option` elements. That should be considered a known limitation in the widget. Detailed information on the scenario could be found in [this GitHub issue](https://github.com/telerik/kendo-ui-core/issues/6558#issuecomment-938449528).
+## Accessibility Compliance Notes
+
+The information in the compliance table above is subject to the following considerations:
+
+* All components implement the required WAI-ARIA attributes without the need for any extra configuration. Some components may provide parameters that render additional optional WAI-ARIA attributes, for example, `aria-label` or `aria-describedby`.
+* The compliance levels are achievable with the [*Default Ocean Blue A11y* theme swatch]({%slug overview_accessibility%}#color-contrast) or any other [custom theme swatch]({%slug sassbasedthemes_customization_telerikui%}) that provides the minimum required color contrast.
+* The accessibility and compliance of some components may depend on the enabled features. In such cases, the compliance table information is based on the default component configuration.
+* Component templates introduce custom markup that may not be accessible. Test any modifications to ensure the web content still meets the desired level of accessibility compliance. Be mindful of components that work with user input such as images, text, or HTML content.
+* Due to the complexity of some components, there are scenarios that are not covered by the WAI-ARIA specification.
+
+## See Also
 
-## Suggested Links  
+* [Accessibility Overview]({%slug overview_accessibility%})
+* [Globalization Overview]({%slug overview_globalization_core%})
 
-* [Overview of Accessibility]({% slug overview_accessibility %})