Accessibility statement

We want everyone to be able to read a menu, order, book a table and run a restaurant with the platform, whatever device, browser or assistive technology they use. Our target is level AA of the Web Content Accessibility Guidelines (WCAG) 2.2, the standard the European Accessibility Act and EN 301 549 point to. This statement covers the public site, the pages guests open from a restaurant’s link or QR code, and the restaurant back office.

Accessibility is checked as part of building the product, not once a year:

• An automated accessibility scan (axe) covers the guest pages, the staff screens and this site, and the serious problems it reports are the first we fix.
• Every page can be used with a keyboard alone, with a visible focus ring, and opens with a link to skip to the main content.
• Text and controls meet the 4.5:1 contrast ratio, and buttons and links are at least 44 pixels tall on touch screens.
• Form fields have labels, errors are announced, and icons that act as buttons have a name a screen reader can read.
• Pages follow the reader’s language and its direction, right to left for Arabic, in nine languages, and respect a device set to reduce motion.

The platform is partially conformant with WCAG 2.2 level AA: most of it meets the standard, and the parts listed below do not yet. We have not had an independent audit; this statement is our own assessment, last reviewed on a date given on request.

These are the known gaps, and we are working on them:

• The kitchen display has no high-contrast or large-text mode yet, and its timers change colour as well as text.
• Arranging tables on the floor plan is done by dragging; there is no keyboard-only way to move a table yet.
• Printed receipts and tickets, and the PDF versions of invoices, are not tagged for screen readers.
• On a small phone, the booking bar pinned to the foot of the reservation page can cover part of the list of times while you scroll.

Each restaurant writes its own menu, dish descriptions and photos. We ask for a description of every photo and give restaurants the tools to translate their menu, but we cannot check what each one writes. If a restaurant’s page is hard to use, tell the restaurant and tell us.

Some steps happen on another company’s pages: paying by card on the payment provider’s checkout, adding a card to a phone wallet, or signing in with Google, Apple or Microsoft. Their accessibility is their own; we choose providers that publish an accessibility statement of their own.

If something on the platform is hard or impossible for you to use, write to the contact page or use the contact page. Say which page and what happened. We reply within five working days, and if we cannot fix the problem quickly we will give you the information or the service another way.

If our answer does not resolve your problem, you can contact the body that enforces accessibility law where you live. For the platform’s home country this is the national body responsible for digital accessibility.