Accessibility statement
Last reviewed October 25, 2026.
Crossover Labs wants everyone to be able to use Vibebook, including people who use a screen reader, a keyboard instead of a mouse, voice control, screen magnification or captions.
The standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the W3C.
Where we are today
Vibebook partially conforms to WCAG 2.2 Level AA. That means most of it meets the standard and some parts don't yet. The gaps we know about:
- Every member's profile canvas is custom HTML built from their own description, so its colors, fonts, layout and motion are theirs. We check canvases for safety, but we can't promise every canvas has enough color contrast, clear headings or reduced motion. Everything around the canvas (name, wall, friends, photos, comments) is ours, and we fix problems there when we find them.
- Our automated checks cover the pages anyone can open. The signed-in pages (feed, profile editor, Explore, friends, notifications, settings) have not had a full manual review with every major screen reader yet.
What we do about it
- We run automated WCAG 2.2 AA checks on our pages and fix what they find.
- We check new features with a keyboard and a screen reader before we release them.
- We fix problems in the code itself. We don't use accessibility overlay widgets.
Tell us about a problem
If something on Vibebook doesn't work for you, email hello@crossoverlabs.ai. Tell us the page or screen and what went wrong. We reply within 5 business days. While we fix it, we'll help you get the information or finish the task another way.
Technical details
Vibebook uses HTML, CSS and JavaScript and is built to work with current versions of the major browsers and screen readers (VoiceOver, NVDA, JAWS, TalkBack).