Accessibility

As of October 27, 2026

Leer en español · اقرأ بالعربية

Wassaaa is for everyone who is in the place. This page says what we aim for, what works today, what does not yet, and how to tell us when something gets in your way.

What we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, in the Wassaaa app for iPhone and Android and on the web pages a guest sees.

What works today

  • Built for a screen reader, through the whole visit. Every button has a name and can be pressed with VoiceOver on an iPhone or TalkBack on Android, from finding a place to ordering. When you and someone both say yes, when a message arrives and at each step of your order, the app says so aloud.
  • A camera that speaks. The selfie step tells you when no face is in view, which way to move the phone, and when you can take the photo.
  • Your phone's largest text. The app follows the text size you set on your phone, up to the largest, and its screens rearrange themselves rather than cut words off.
  • Reduced motion. If your phone is set to reduce motion, the app's animations become a short fade or stop.
  • Contrast. Text, and the parts of a button or a field that you need to see, stand out from what is behind them, in the night theme and in the daylight one.
  • A tap for every gesture. Anything you can do with a swipe, a drag or a press and hold, you can also do with a plain tap.
  • The list, not only the map. Every place on the map is also in the list, which is the way to a place with a screen reader.
  • Choosing a size or a milk, built for a screen reader. On a menu item with choices, each choice says its rule (for example, "Pick one · Required"), each option says whether it is chosen, a sold-out option says so, and the Add button says what is still to choose. The page a table code opens works this way today, as a form; the next version of the app is built the same way. When something you are choosing sells out, it is said once.
  • Pictures on a menu come with words. A place must write words that describe the picture of an item, and they are read first.

What we know falls short

  • Nobody has yet used the app with a screen reader on a real phone. Our tests read each screen the way a screen reader does, and we walked the app on a simulator, which cannot speak. If something reads wrongly or in the wrong order, we want to hear it.
  • What another guest sends you has no description. For a photo, a voice message or a GIF you will hear "Photo", "Voice message" or "GIF", and nothing about what is in it.
  • Some clocks cannot be stopped. A place's question with a closing time, a visit (it ends eight hours after you came in, and cannot be made longer) and a chat (it ends when your visit or the other person's does) run on their own time. What you had typed is kept when a chat ends.
  • Things that move by themselves have no stop button. A breathing dot, a floating drawing and a GIF stop when your phone is set to reduce motion, and only then.
  • At the very largest text a few things stop growing: the map's pins and a screen's title in its top bar. The list of places says everything the map does, at any size.
  • The selfie camera works with the phone upright only.
  • A phone held on its side, and an iPad, are not yet drawn as carefully as a phone held upright. On some screens of the app as it is today, a word or a button can sit under the camera's island or the rounded corners when the phone is on its side. The next version of the app is built to keep words and buttons clear of them; we have checked that only with automated tests, not on a real phone.
  • On a voice message, the bars that show how much has played are faint. The time under them says the same.
  • What a place writes is read as it wrote it. The words for a menu picture and the names of a menu's choices are typed by the place and are not translated.
  • The pages for a place's owner and team are in English only: signing a place up, and the staff console.

How it was tested

This is our own testing. It is not a certificate, and nobody outside Wassaaa has audited it.

We checked the app's screens with automated tests that read each screen as a screen reader does, at the largest text sizes, with reduced motion, and in both themes. We walked the app on a simulator from finding a place to an order being ready, using only what a screen reader is given. We measured the contrast of the colours, and we measured these web pages in a browser, with a keyboard and at a narrow width. Since October 26, 2026 those tests also draw each screen on an iPhone held on its side and on an 11-inch iPad. We have not yet tested with a screen reader on a real phone, or with people who use one every day.

Last tested: October 27, 2026.

Tell us about a barrier

If something in Wassaaa does not work for you, write to support@sigmaton.com. It helps if you tell us:

  • the phone you use;
  • the screen reader or the setting you use (VoiceOver, TalkBack, larger text, reduced motion);
  • what you were trying to do.

A person reads every message, and we answer.