Legal

Accessibility

Last updated: 2 October 2026

Nabad is used by audiences who join on their own phones, often people we will never meet. We want the join-and-vote experience to work for as many of them as possible, including people who use screen readers, keyboards, or larger text.

Access across languages

Language is the barrier Nabad was built around. Everyone who joins reads the questions in their own language and can answer in the language they think in. The presenter's screen can show those answers translated into the room's languages, and on Pro each phone shows them translated too.

Standard we aim for

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 level AA, focusing first on the flow that matters most: joining a session with a code and answering questions.

What we have done

On 2 October 2026, every page on nabad.live passed an automated WCAG 2.1 AA check (axe-core) on computer and phone screens.
The join and vote screens use semantic HTML, and every control has a text label that a screen reader can announce.
Form fields (the join code, text and word answers, ratings, and the optional name) carry accessible names.
Error messages and confirmations are announced to screen readers, not shown by colour alone.
Keyboard focus is always visible, and the flow can be operated with a keyboard.
The interface is fully translated into 86 languages, including English, Arabic, Persian, Hindi, Chinese and Swahili, with correct right-to-left layout for Arabic, Hebrew, Persian, Urdu and Pashto.
Text reflows on small screens and can be zoomed without breaking the layout.

Known limitations

We are honest about where we are not there yet:

We have not yet completed a formal third-party accessibility audit.

Get help or report a problem

If any part of Nabad is hard to use, or you need a session run in a different way, email info@nabad.live. Tell us what happened and the device or assistive technology you were using, and we will help and prioritise a fix.