Accessibility Overview
The Kendo UI for Angular Splitter is WCAG 2.2 AA and Section 508 compliant. The component also follows the WAI-ARIA best practices for its separator role and keyboard navigation, and it is tested with popular screen readers.
Due to the rich feature set of the library and complexity of some components, the specific combination of configuration options may lead to inaccessible component rendering. Perform thorough testing on any modifications applied to the Kendo UI for Angular components to ensure that they continue to comply with the desired level of accessibility standards.
The following example demonstrates the accessibility compliance of the Splitter component. Open the example in a new window to evaluate it with Axe Core or other accessibility tools.
The described level of compliance is achievable with the Ocean Blue A11y Accessibility Swatch.
WCAG 2.2 Compliance
To comply with the WCAG 2.2 AA accessibility requirements, set the splitbarWidth property to the desired pixel value.
The following example demonstrates a Splitter that is fully compliant with the latest WCAG 2.2 AA accessibility guidelines.
WAI-ARIA Support
All relevant internal elements of the Splitter component include the ARIA attributes and roles required for WCAG 2.2 compliance.
Setting the
aria-valuenowattribute on the separator element is not applicable. The Splitter can render multiple panes and nested Splitters, so a single numeric value would not communicate meaningful state. If your application requires more attributes on the split bar, use thesplitterBarAttributesoption.
Section 508
The Splitter component is compliant with the Section 508 requirements.
Static Analyzers
The tool used for Automated Testing is Axe Core.
Screen Readers
| Environment | Tool |
|---|---|
| Firefox | NVDA |
| Chrome | JAWS |
| Microsoft Edge | JAWS |