Kairo · Public information
Accessibility Statement
Effective and last updated: 1 November 2026
Kairo aims to make its public pages and core web app usable with a keyboard, screen reader, zoom and strong contrast. Accessibility is an ongoing engineering requirement, not a one-time claim of perfect conformance.
What is built in
Core controls use native buttons, links, inputs and dialogs; visible keyboard focus is provided; pages expose a skip link; informative public images have text alternatives; status and error messages use live regions where appropriate; and layouts adapt to mobile screens and text resizing.
Known limits
AI-generated artifacts, third-party embeds, provider authorization pages and experimental canvas-based features may not always have equivalent accessibility. Kairo does not claim complete WCAG conformance until an independent audit has been completed.
Report a barrier
Email [email protected] with the page, device/browser, assistive technology if relevant, and what you were trying to do. Do not include passwords or sensitive chat content. We will prioritize a practical alternative and a fix.