Accessibility Statement
What we have built for accessibility, what we have not yet verified, and how to tell us about a barrier.
Where we stand
We build toward the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our design target. We have not completed a formal accessibility audit, so we do not claim conformance to it. We will say that we conform when someone qualified has checked and told us we do.
What is actually implemented
- Layout uses CSS logical properties throughout, so the interface mirrors correctly in right-to-left languages rather than being visually patched.
- Right-to-left support is a first-class mode, switched at the document level, and Hebrew is a fully translated language of the product.
- Elements that must remain a div or span but behave as buttons carry the button role, are keyboard focusable, and are activated by Enter and Space through a shared helper, so keyboard use matches native buttons.
- Modals close on Escape, and dialogs carry a dialog role with an accessible label.
- Animation is reduced when the operating system reports a preference for reduced motion.
- Colors come from a single token set applied per theme, including the dark themes, so contrast is tuned in one place rather than per screen.
- Font and theme preferences are user-configurable, including higher-contrast options.
What we have not verified
We have not completed a screen-reader pass across the whole product, we have not measured contrast on every state of every component, and we have no third-party audit report. Those are the honest gaps.
The complex interactive surfaces are the likeliest to give trouble: the presentation editor and the schedule grid in particular. We are working on them.
Tell us about a barrier
If something is unusable for you, email support@kavvim.com with the page and a description of what happened. We treat access barriers as priority bugs rather than feature requests, we will tell you what we are doing about it and when, and we will work with you on a way through in the meantime.