Accessibility is component behavior
A visible, testable contract.
Gummy UI targets WCAG 2.2 AA for the public website and shipped component states. Automated checks support—but never replace—keyboard, screen-reader, zoom, contrast, touch, RTL, and reduced-motion review.
What every component must provide
- Native semantics first, with Base UI where managed focus or composite behavior is required.
- Visible labels, instructions, validation, and non-colour-only state cues.
- Complete keyboard paths, visible focus, 44px touch targets where applicable, and focus restoration.
- Light and dark contrast, 200% zoom/reflow, RTL, and reduced-motion behavior.
- Automated axe coverage plus behavior tests against real rendered source.
Current evidence
The local catalogue test suite covers all nine dependency groups, including representative axe checks, native relationships, focus movement, controlled state, RTL keys, and clean registry installation. Manual browser and assistive-technology smoke tests are recorded as a release gate rather than represented as already complete.
Report a barrier
Email support@kreydlabs.com with the page, component or task, what happened, and the browser or assistive technology involved. We aim to send a first reply within two UK business days. This is a target, not an SLA.