Accessibility
Last updated: June 12, 2026
A restaurant storefront that only works for some guests is a broken storefront. We build SyncBite so that people who use screen readers, keyboard navigation, voice control or magnification can browse a menu, place an order and track it, the same as anyone else. That goes for the restaurant side too: the dashboard and kitchen display should work for every member of staff.
The standard we work to
We aim for WCAG 2.2 Level AA across the marketing site, the customer storefront and order tracking. That also covers the requirements of EN 301 549 and the European Accessibility Act for our EU customers, and ADA expectations in the U.S.
What this looks like in practice
- Every page can be used with a keyboard alone, with a visible focus indicator and a skip-to-content link.
- Order status updates on the tracking page are announced to screen readers as they happen, not just repainted on screen.
- Colour contrast in both light and dark themes meets AA ratios, and colour is never the only way we signal something.
- Forms have real labels, error messages in text, and no puzzles or CAPTCHAs at sign-in. Password managers and paste work everywhere.
- Touch targets in the cart and ordering flow are at least 24×24 px.
- Animations respect your "reduce motion" system setting.
Known limitations
We would rather tell you where it is rough than pretend it is finished. Right now:
- Some charts in the restaurant analytics dashboard lack text alternatives. The underlying numbers are available in tables on the same pages.
- The drag-and-drop floor plan editor does not yet have a full keyboard equivalent. Table details can be edited through the regular forms instead.
- Menu photos on storefronts are treated as decorative because the dish name sits next to them in text, so screen readers hear each dish once. Photos restaurants upload in other places may still lack descriptions.
Found a problem?
If something on SyncBite or on a restaurant storefront we power does not work with your assistive tech, email [email protected] with the page and what happened. Accessibility reports jump the support queue, and we will reply within two business days.