Legal
Accessibility
Last updated: 2 August 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.
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
- 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 across English, Arabic, French, and Spanish, with correct right-to-left layout for Arabic.
- 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:
- Two question types are visual by nature: dropping a pin on an image, and placing a dot on a two-axis map. These are difficult to complete with a keyboard or screen reader alone. A host who needs a fully accessible session can choose the other question types (multiple choice, word cloud, open text, rating, ranking, Q&A), which do not have this limitation.
- 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.