Accessibility is a top priority for Clock. Built on Base UI, Clock components handle many complex accessibility details including ARIA attributes, role attributes, pointer interactions, keyboard navigation, and focus management. The goal is to provide an accessible user experience out of the box, with intuitive APIs for configuration.

This page highlights some of Clock’s key accessibility features, as well as ways you will need to augment the library to ensure that your application is accessible to everyone.

Keyboard Navigation

Clock 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

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

While Clock 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

Clock 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

Clock CI validates the fork’s build, types, lint rules, component tests, and supported React versions. The broader cross-browser, device, platform, and screen-reader testing claim in the inherited documentation originated upstream; ComHora has not yet published an independent matrix reproducing that coverage for Clock. Test the components in the browsers and assistive technologies required by your application.

---

For more detailed information about the accessibility features provided by Base UI, visit the official accessibility documentation.