# Accessibility Overview

The UI for Blazor Splitter component is <a href="https://www.w3.org/TR/WCAG22" target="_blank">WCAG 2.2 AA</a> and <a href="https://www.section508.gov" target="_blank">Section 508</a> compliant. The component also follows the <a href="https://www.w3.org/WAI/ARIA/apg/" target="_blank">WAI-ARIA best practices</a> for implementing the keyboard navigation for its component <a href="https://www.w3.org/TR/wai-aria/#roles" target="_blank">role</a>, and is tested against the popular screen readers.

# Blazor Splitter Accessibility Example

WCAG 2.2 introduces the <a href="https://www.w3.org/WAI/WCAG22/Understanding/dragging-movements" target="_blank">"Dragging Movements"</a> 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.

The illustrative example below shows the tile resize action, achievable through the [Context Menu](https://www.telerik.com/blazor-ui/documentation/components/contextmenu/overview). Telerik UI for Blazor 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 Splitter component](https://www.telerik.com/blazor-ui/documentation/components/splitter/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 Splitter accessibility compliance example

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

## See Also

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