Accessibility

Built for keyboard, touch, and screen-reader users from the first pass.

Accessibility is part of how Chrysaor is designed, not something added afterward. Here’s what that means today, and how to tell us where we fall short.

Standards we target

We design toward WCAG 2.2 AA, including color contrast, visible focus states, and no reliance on color alone to convey meaning.

Keyboard support

Menus, tabs, accordions, dialogs, and compose sheets are built to be fully operable by keyboard, with a skip link on every page.

Screen readers

Semantic landmarks, labeled form fields, descriptive error messages, and ARIA live announcements for asynchronous states such as verification results.

Motion

We respect prefers-reduced-motion. Where motion is used, it stays brief and is never required to complete a task.

Known gaps

This is a preview build. Some interactive demos, such as the app-shell product previews, have not yet completed a full automated and manual accessibility audit across every state. We’re tracking this as part of the pre-launch checklist.

Tell us what’s not working

If something on this site is difficult to use with assistive technology, please tell us. Include the page, the assistive technology you used, and what happened.

Send accessibility feedback