Our commitment
We design against WCAG 2.1 Level AA and treat accessibility as part of the product's design system, not an afterthought.
What we do today
- Contrast. Text and interactive colors in both light and dark themes are checked against WCAG AA contrast ratios, and those checks run as automated tests on every change.
- Motion.Animations respect your system's "reduce motion" preference. When it is set, decorative motion is disabled.
- Semantics. Pages use semantic HTML landmarks and ARIA attributes so screen readers can navigate structure, state, and controls.
- Language. The interface declares its language to assistive technology and is available in 10 languages.
- Keyboard. Core flows — signing up, chatting with your babot, reviewing Sanctum cards, managing settings — are operable by keyboard.
Known limitations
We have not yet completed a formal third-party accessibility audit. Areas we know need work:
- Some complex interactive surfaces (the Arena battle view, the Studio brain viewer) rely on visual metaphors that do not yet have full non-visual equivalents.
- A "skip to content" link is not yet available on every page.
- Some media content may lack text alternatives.
Feedback and contact
If you hit an accessibility barrier anywhere in Babots, tell us and we will prioritize it: use the contact route on our Trust & Safety page or email accessibility@babots.ai and include "Accessibility" in the subject. We aim to respond within 14 days.
Enforcement
If you are in the European Union and believe we have not responded adequately, you may contact the market-surveillance / enforcement authority in your member state.