Accessible by default, not by accommodation

Most digital products treat accessibility as something to add later: alt text, screen reader support, keyboard navigation. All of which is good and necessary and rarely done as well as it should be.

Voice chat is one of the few platforms where the core experience is accessible by default. The thing you do on XES — talk to another person — doesn’t require sight at all. The thing the other person does — listen and reply — doesn’t either. The medium itself is the accessibility.

For a visually impaired or blind user, this is structurally different from a video platform. On a video site you’re either invisible to the other side (camera off, which on most sites brands you as suspicious), or you’re visible without being able to see them back, which is its own thing. On XES everyone is in the same position regardless of sight. The bio plays as a voice clip rather than text. The matchmaker doesn’t care if you can see the interest tags; they’re read out as part of the introduction. The chat strip and the controls are all keyboard-and-screen-reader navigable (we have some way to go on this; if you’ve hit a snag, please email).

The places we still need to do better are the marketing pages and the lobby UI. The marketing site is image-heavy. The lobby has some controls (mute, filters) that are easier to find by sight than by keyboard. We’re working on both. If you’re a screen reader user and you’ve had a specific problem on XES, contact me directly. Accessibility patches go to the front of the queue.

The wider point is that voice chat is one of the few corners of the internet where blind users don’t have to adapt to a sighted-first design. The medium is on your side. The platform’s job is just not to mess that up.

← Back to Blog