TableQR

Accessibility Statement

Last updated: October 14, 2026

Table QR LLC runs TableQR, the service venues use to publish their menus and take orders from guests (“TableQR”, “we”, “us”). This statement describes how accessible the pages guests open from a venue’s QR code are, what does not work well yet, and how to tell us about a problem.

1. What this statement covers

It covers the guest pages of every venue on TableQR: the venue page, its menus and dishes, search and filters, the cart and ordering, order status, table requests and the bill, the reservation form and the cookie consent banner.

Every venue’s pages also link to a statement made for that venue. It adds what depends on the venue’s own choices, such as its colours and its content, and how to reach the venue.

2. Accessibility standard

We aim for the guest pages to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA and the requirements for web pages of the European standard EN 301 549, which the European Accessibility Act relies on.

3. Conformance status

The guest pages are partially conformant with WCAG 2.2 level AA: some parts do not fully meet the standard yet. They are listed under Known limitations.

4. Known limitations

We know of the following limitations:

  • Each venue chooses its own colours, and some choices have low contrast in the standard view. Guests can switch on the low-vision mode, which raises contrast and enlarges text; it also turns on by itself when the device is set to increase contrast or to use forced colours.
  • Banner images that venues upload may contain text inside the picture, which cannot be enlarged, translated or read aloud.
  • Dish names, descriptions, photos and translations are written by each venue, which is responsible for them.
  • Screen readers are tested by hand with VoiceOver on iOS and TalkBack on Android only; other screen readers are not tested.

5. How we test

We check the guest pages in these ways:

  • Automated checks with axe run on the components of the guest pages in our component tests.
  • Automated checks with axe run on the menu, dish details, cart, checkout, order status, table requests and the reservation form in end-to-end tests of the running product.
  • Low-vision runs check those pages at 400% zoom (a screen 320 pixels wide), with text enlarged to 200% and with forced colours.
  • Before each release that changes the guest pages, a person walks through the menu, a dish, the cart, an order and its status with VoiceOver on iOS and TalkBack on Android.

6. Feedback and contact

If something on the guest pages is hard to use, or you find a problem that is not listed here, write to support@table-qr.com. Tell us the address of the page, what you were trying to do, and the device, browser and any assistive technology you used.

For something a venue wrote — a dish name, a description, a photo or a translation — please also tell the venue: the statement linked at the bottom of its pages says how to reach it.

7. Enforcement

If you are not satisfied with our answer, you can contact the market surveillance authority responsible for accessibility in your EU country.

8. About this statement

This statement was prepared on October 14, 2026 and last reviewed on October 14, 2026. It is based on our own assessment: a review of the code and the tests described above.