Trust
Accessibility statement
Meetings are for everyone. Here is what works today, where we still fall short, and how to tell us.
We aim for WCAG 2.2 level AA across the public site and the meeting interface. We test with a keyboard and screen readers and treat accessibility problems as bugs, not as feature requests.
Keyboard access
Pages and meeting controls can be reached and used with the keyboard. Focus is clearly visible, menus and drawers can be closed with Escape, and a “skip to content” link is offered at the top of each page.
Screen readers
We use semantic landmarks and one main heading per page, label buttons and form fields, announce form errors and success messages, and hide purely decorative visuals from assistive technology.
Contrast and themes
Light and dark themes are both designed for readable contrast, follow your system preference by default, and can be switched at any time. Information is never conveyed by colour alone.
Reduced motion
If your system asks for reduced motion, decorative animations, parallax and flip effects are turned off and the same content is shown statically.
Languages
The interface is available in English, French, Spanish and Kinyarwanda; German, Portuguese, Swahili and Arabic are being added. It follows your browser language on first visit and remembers your choice. The page language and reading direction are updated, so right-to-left languages such as Arabic lay out correctly and screen readers pronounce text properly.
Captions and transcription
Live AI captions show what each speaker says, keep a session history and can be moved anywhere on screen. The AI assistant can also transcribe and write minutes. Machine captions can contain mistakes, especially with accents, names and background noise, so please treat them as an aid.
Zoom, small screens and low bandwidth
Pages reflow from 320 px wide up to large monitors and work with browser zoom and text enlargement. You can turn your camera off to keep audio flowing on a weak connection.
Hands-free gesture controls
Optionally, your camera can recognise a few hand gestures on your device: an open palm raises your hand, a fist lowers it, and thumbs up, victory or a heart sign send a reaction. Nothing leaves your browser, and it is off until you turn it on in Settings → Accessibility. The 3D layouts can also be driven entirely with the keyboard.
Live translation and captions
Live captions and translated chat help deaf and hard-of-hearing people and people who speak another language. Captions come from each speaker’s browser and can be wrong, so they are an aid and not an official record. Chat translation works on your device where the browser supports it.
Safety codes and device badges
Safety codes and device badges are plain text, so a screen reader can read them and people can compare them by voice. Nothing about them depends on colour.
Known limitations
Some collaborative tools, such as the pixel-art canvas and games, are visual and pointer-oriented and are harder to use with a keyboard or screen reader. Shared video and screen content is only as accessible as what people share. We are working on alternatives and welcome your priorities.
The Android app and the 3D layouts (Virtual House and VR conference) have had less accessibility testing than the website. We have not yet completed a full screen-reader audit of the Android app. Right-to-left layout for Arabic is new and may have rough edges.
Report an accessibility problem
Tell us which page or feature, what you were trying to do, and the browser and assistive technology you use. We reply within one working day and will suggest a workaround while we fix it.