Accessibility
Accessibility statement
We want ConsoleAI to work for everyone, including people who use a screen reader, a keyboard, voice input, zoom or reduced motion. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
What we do today
- Our public pages and most in-app screens have a “Skip to content” link, a page title and one main heading.
- Everything works with a keyboard, and the focused item has a clear outline.
- Pages never block zooming, and text uses your device’s own fonts at 16 px or larger for body text.
- If your device asks for reduced motion, we turn off animations and transitions.
- Form fields have labels; errors on our public forms and the progress of a new workspace being built are announced by screen readers.
- Charts show the numbers in text next to them, and an empty chart says so instead of drawing a made-up line.
- Voice is optional: anything you can say, you can type.
- Automated checks: our public home page scored 100 for accessibility in Google Lighthouse (mobile) when last measured. We check new pages the same way before they go live.
Known limitations
- The knowledge graph view is a visual map; its contents are also available as searchable lists, but the map itself is not usable with a screen reader.
- The main chat screen (/app) does not have a “Skip to content” link yet, and some older in-app screens use small text in dense tables on phones. We are moving them to the new design.
- Google’s sign-in page and your browser’s speech and install prompts are run by those companies, not by us.
- We have not yet had an independent accessibility audit. Until then this statement is based on our own testing.
Tell us about a problem
If something is hard or impossible to use, please tell us what page you were on and what happened. We aim to reply within 5 working days.
Send us a message and choose “Accessibility”.
Last reviewed November 16, 2026.