Accessibility
Accessibility
VUEMesh should be usable by everyone who makes or joins a show. This page says how close it is, what has been checked, what is known not to work well yet, and how to tell us about a barrier. It describes the site at vuemesh.com.
Updated 14 November 2026 (VUEMesh 0.91.0): calls' controls, captions in a call, and the redesigned pages.
The standard we aim for
The Web Content Accessibility Guidelines (WCAG) 2.2, level AA. VUEMesh partially conforms: some parts don't meet it yet (below).
What has been checked
- Every public page (home, tour, privacy, terms, collaborate, what's new, and the studio, camera, watch, share, remote and TV pages) is checked with the automated tool axe against WCAG 2.2 AA, in both light and dark themes, and passes.
- Pages work at any zoom and on a phone's width, follow your system's light or dark setting, and use real buttons, labels and headings.
- Calls (
/call): each of its views (starting or joining, before joining, waiting to be let in, in a call with captions on and someone waiting to come in, the people and invite panels) is checked with axe against WCAG 2.2 AA and passes. - Automated tools catch only some barriers. The checks above don't replace testing with a screen reader or a keyboard alone, which is still to do for most of the studio and for calls.
In a call
- Every control has a word, not just an icon: Mic, Camera, Share, People, More and Leave on a phone, the rest under More. Whether the microphone or camera is on is shown by its icon (slashed when off) and told to screen readers as the button being pressed or not.
- Muted is a struck microphone after a person's name, read out as "muted".
- Someone waiting to come in gets a bar across the top of the call with their name, Let in and Turn away. It stays until it's answered, and is announced to screen readers.
- Captions never look on when nothing's coming. A picture whose browser can't make captions shows a struck-through CC, with the reason given on hover and to screen readers. On a device that can't make them, Captions turns on only if someone in the call is making them, and otherwise stays off and says why.
Known limits
- The studio is a dense, live control surface. Audio meters, the timeline and some monitors are drawn as pictures, so a screen reader can't read them yet, and not every control can be reached and used from the keyboard alone.
- Live video and sound come from the people at the show. A host can turn on live captions (in Chrome 139 or later, or Edge, on a computer): the browser recognises what's said on the program, on that computer, and the captions go on the picture and are saved with the recording as a captions file. They're made by a machine, live, so they lag a moment behind and can get words wrong, and they aren't in every language or browser. VUEMesh doesn't add audio description; a host can add lower thirds and slates.
- In a call, anyone can turn on captions (Captions, under More on a phone): each person's words appear on their picture, worked out on their own device by its browser's on-device speech recognition and sent to the others over the call's own encrypted links. Each person chooses whether to see them, how big (Aa), and at the bottom or top of the pictures (↕). They're made by a machine, live, so they lag a moment and can get words wrong, and they come only from browsers that can recognise speech on the device (Chrome 139 or later, or Edge, on a computer, in their languages), not from an iPhone, Safari or Firefox for now. Those can still show the captions of others whose devices make them. A sign language interpreter can join a call like anyone, and a tap on their picture keeps it big; captioning by a person or an outside captioning service isn't built in yet. Someone waiting, joining or leaving, a studio in the call, and its recording, are also said to screen readers.
- Some status is shown by colour (for example red for on air); we are adding words or shapes alongside wherever we find it, as calls now do for a muted microphone or camera.
Tell us about a barrier
If something on VUEMesh keeps you from doing what you came to do, please write to info@vuemesh.com or open an issue. Say which page, what you were trying to do, and what you use (browser, screen reader or other tools) if you like. We aim to reply within 30 days. VUEMesh is run by one person, so a reply can take a while, but every report is read and kept.
Last full review November 2026, with VUEMesh 0.70; calls, the join pages and these pages checked again with axe for 0.91.0.