Blazor Splitter Accessibility

Out of the box, the Telerik UI for Blazor Splitter provides extensive accessibility support and enables users with disabilities to acquire complete control over its features.

The Splitter is compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 AA standards](https://www.w3.org/TR/WCAG21/) and Section 508 requirements, follows the Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA) best practices for implementing the 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.

Slitter Pane

Selector	Attribute	Usage
`.k-pane`	`role=group`	Sets the proper role for the Splitter pane that identifies a set of user interface objects that is not intended to be included in the page's summary or table of contents.

Note: The value of the aria-label attribute of the split-bar elements will be provided to their respective preceding pane element through the API.

SplitBar

Selector	Attribute	Usage
`.k-splitbar`	`role=separator`	Sets the proper role for the Splitter split-bar element.
	`aria-label`	An accessible name, with aria-label should be included if there is more than one focusable separator. The value is set through the corresponding SplitterPane API.
`.k-splitbar-horizontal`	`aria-orientation=vertical`	When a splitbar separates two panes horizontally, its aria-orientation must be explicitly set to 'vertical'.

Note: Setting the value-now attribute of the separator element is not applicable, as the Splitter is a complex layout component allowing splitting the content into multiple panes across any number and level of nested Splitters and panes, thus announcing a value would not convey any meaningful information. Moreover, there is no specification, or WAI-ARIA recommendation that explains how value should be set in multiple panes scenario. Further information on this complicated scenario could be found in the following WAI-ARIA GitHub issue:

WAI-ARIA Practices on GitHub