# Accessibility Overview

The UI for Blazor TreeView component is [WCAG 2.2 AA](https://www.w3.org/TR/WCAG22) and [Section 508](https://www.section508.gov/) compliant. The component also follows the [WAI-ARIA best practices](https://www.w3.org/WAI/ARIA/apg/) for implementing the keyboard navigation for its component [role](https://www.w3.org/TR/wai-aria/#roles), and is tested against the popular screen readers.

# Blazor TreeView Accessibility Example

WCAG 2.2 introduces the ["Dragging Movements"](https://www.w3.org/WAI/WCAG22/Understanding/dragging-movements) criterion as an important part of the Operable principle. Its primary goal is to guarantee that any feature reliant on drag actions offers an alternative method that can be executed with a single click, enhancing user accessibility.

In our illustrative example below, we've showcased the item reordering actions, achievable through our [Context Menu](https://www.telerik.com/blazor-ui/documentation/components/contextmenu/integration#context-menu-for-a-treeview-node). Our goal is to offer a versatile API that allows users to trigger all functions programmatically or externally, meeting diverse accessibility requirements for any applications.

The following example demonstrates the [accessibility compliance of the TreeView component](https://www.telerik.com/blazor-ui/documentation/components/treeview/accessibility/wai-aria-support). The described level of compliance is achievable with the [Ocean Blue A11y Accessibility Swatch](https://www.telerik.com/blazor-ui/documentation/accessibility/overview#color-contrast).

> caption TreeView accessibility compliance example

<demo metaUrl="client/treeview/accessibility/overview/example-1/" height="420"></demo>

## See Also

* [Live demo: TreeView Accessibility](https://demos.telerik.com/blazor-ui/treeview/keyboard-navigation)
