Back to home
Accessibility
We're building Ballastra to be usable by everyone — honestly.
Accessibility is not finished at Ballastra. This page says plainly what already works, what we are actively working on, and how to tell us when something gets in your way.
What already works
- Reduced-motion is honored across the site and app — animations and auto-cycling content stop for people who ask for it.
- Ballastra installs as a PWA and runs in the browser, with real headings, landmarks and form labels on the pages we have finished auditing.
- Voice rooms offer hold-to-talk and push-to-talk, so speaking is always an option alongside the interface.
- Text, buttons and controls scale with the browser, and the site remains usable with keyboard and screen-reader on the public pages.
What we're working on
- A full screen-reader pass across the authenticated app (settings, voice controls, messaging).
- A high-contrast theme and colour-blind-friendly handling for roles, presence and status indicators.
- Complete keyboard-navigation coverage and focus management in every screen, not just the public pages.
- Clear, tested alt text and captions for images, embeds and media as they ship.
How we treat it
Accessibility work is scheduled alongside features, not after them, and every barrier we are told about is treated as a bug. We know this page will change as the app improves — it is meant to.
Hit a barrier? Tell us about it — a screenshot, a description, an assistive-tech note: any of these helps us fix it faster.