Blazor Splitter Accessibility
The Telerik UI for Blazor Splitter component is WCAG 2.1 AA and Section 508 compliant. The component also follows the WAI-ARIA best practices for implementing the keyboard navigation for its component role, and is tested against the popular screen readers.
Wai-Aria
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-labelattribute 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.
Resources
WAI-ARIA specification for separator
MDN reference for the separator role
Section 508
The Splitter is compliant with the Section 508 requirements
Testing
The component has been extensively tested automatically with static code analyzers and manually with the most popular screen readers.
Any Accessibility Issues could be reported in Telerik Support System.
Screen Readers
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |