Keyboard Navigation

Kumo components adhere to the WAI-ARIA Authoring Practices to provide basic keyboard accessibility out of the box. This is critical for users who have difficulty using a pointer device, but it's also important for users who prefer navigating with a keyboard or other input mode.

Many components provide support for arrow keys, alphanumeric keys, Home, End, Enter, and Esc.

Focus Management

Kumo components manage focus automatically following a user interaction. Additionally, some components provide props like initialFocus and finalFocus, to configure focus management.

While Kumo components manage focus, it's the developer's responsibility to visually indicate focus. This is typically handled by styling the :focus or :focus-visible CSS pseudo-classes. WCAG provides guidelines on focus appearance.

Color Contrast

When styling elements, it's important to meet the minimum requirements for color contrast between each foreground element and its corresponding background element. Unless your application has strict requirements around compliance with current standards, consider adhering to APCA, which is slated to become the new standard in WCAG 3.

Accessible Labels

Kumo provides components like Field, Input, and Checkbox to automatically associate form controls. Additionally, you can use the native HTML <label> element to provide context to corresponding inputs.

Most applications will present custom controls that require accessible names provided by markup features such as alt, aria-label or aria-labelledby. WAI-ARIA provides guidelines on providing accessible names to custom controls.

Testing

Kumo components, built on Base UI, are tested on a broad spectrum of browsers, devices, platforms, screen readers, and environments to ensure accessibility across different user contexts.