We want everyone to be able to use this website and the booking pages we build for restaurants, including people who use a keyboard instead of a mouse, a screen reader, zoom or magnification, voice control, or reduced motion settings.
This statement covers the website at https://tablestial.com. A separate section below describes the booking service we provide to restaurants.
We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA. We use the European standard EN 301 549 V3.2.1 as the reference for what accessible digital services must do.
This website partially meets WCAG 2.2 level AA. Most of the site meets the standard. The parts that do not yet, or that we have not yet checked, are listed below with a date for each.
These were problems in our review and are now fixed and tested again:
- You can pause the films and every animation on the site, from a button at the top of the home page or from the footer of every page. Your choice is remembered. If your device asks for reduced motion, everything starts paused.
- The home page says what we make from the first moment, in text. Keyboard focus never lands on a control you cannot see.
- A "Skip to main content" link, labelled navigation, the current page marked, and the header and footer kept outside the main content.
- Focus stays in the right place after you jump within a page, and is never hidden under the fixed header.
- Enough contrast for footer text, labels, form placeholders, the booking summary and the newsletter field.
- On the contact form, each error appears under its field, focus moves to the first error, and the result is announced.
- Tables and sliders that scroll sideways can be reached and scrolled with a keyboard.
- No text smaller than 12 pixels, links and buttons at least 24 pixels in size, and no text lost when you increase line, letter or word spacing.
- Content stays readable with scripts switched off and in forced colours (high contrast) mode.
- In the demo booking room, a warning appears one minute before a table hold ends, with a button to keep holding the table.
- No sideways scrolling at 320 pixels wide, the same as 400 percent zoom on a laptop.
| Item | What does not work yet | Who it affects | When we plan to fix it |
|---|---|---|---|
| K2 | The 3D dining room runs a few small animations of its own, such as a pulse on the table markers and a loading bar. The "Pause animations" control does not stop them yet. (WCAG 2.2.2) | People who are distracted by movement | 11 December 2026 |
| K3 | Turning the mouse wheel over the 3D room on the page both scrolls the page and zooms the model. The full-screen view does not do this, and every view can also be reached with buttons and the keyboard. | Mouse users who want to scroll past the room | 11 December 2026 |
| K4 | On the booking pages we build for restaurants, the table hold counts down and does not yet let a guest ask for more time. (WCAG 2.2.1) See also the booking service section below | Guests who need more time to fill in their details | Our check of the booking flow reports by 27 November 2026, with a fix date for each finding |
| K7 | "Pause animations" does not switch off the smooth scrolling the site adds to the mouse wheel. Smooth scrolling is already off if your device asks for reduced motion. This is not a level AA failure | People sensitive to motion who have not set reduced motion on their device | Decision by 13 November 2026 |
Watched closely. Text over the home page film meets the contrast minimum, but only just (the lowest measured figure is 4.6 to 1, against a minimum of 4.5 to 1). We measure it again every time the film or the top of the home page changes. The next scheduled check is on 13 November 2026.
Other languages. Every page is in English today. Before we publish Latvian and Russian versions of our legal pages, we will make sure each one declares its language correctly, so that screen readers use the right voice: Latvian by 13 November 2026, Russian by 20 November 2026.
The booking room and back office demos inside our pages. The demo booking room and the demo back office that appear inside the demo page, the case study and the home page come from our booking software. Our review did not check inside them. We will write the assessment plan by 13 November 2026, and report what we find, with a fix date for each issue, by 27 November 2026.
Testing we have not done yet:
- No test with screen readers (VoiceOver on Mac and iPhone, NVDA on Windows) yet. Planned for 13 November 2026, on the home page, the contact page and the demo page.
- No testing with disabled users yet. From launch we invite feedback through the contact route below, and we will review what arrives on 11 December 2026.
- No full check against every clause of EN 301 549 yet. Planned for 11 December 2026.
We last reviewed the site on 30 October 2026 and checked it again on 1 November 2026, after the fixes. We tested it ourselves, on the site as built before launch. We will test it again on the live address when it launches.
Automated checks. axe-core 4.10 with the WCAG 2.0, 2.1 and 2.2 level A and AA rules, on the main pages (home, platform, contact, journal and one article, privacy, terms, cookies, demo and the case study), on a phone-sized and a laptop-sized screen, at the top of each page and again after scrolling to the bottom.
Manual checks:
- a full keyboard walk with Tab, Shift+Tab, Enter, Space and Escape, on a phone-sized and a laptop-sized screen;
- reduced motion switched on, scripts switched off, and forced colours switched on;
- text spacing increased to the WCAG values, looking for cut-off text;
- reflow at 320 and 720 pixels wide;
- contrast over the home page film, measured from the picture at every second of the film;
- the contact form with empty, mistyped and valid input;
- the pause control, including after a reload;
- the full-screen dining room with the mouse wheel, Tab and Escape.
This site uses no accessibility overlay or widget, and we do not plan to add one. We fix the site itself instead.
Tablestial gives each client restaurant a website with a booking page built in. This is how a guest books a table:
- Choose the number of guests, the date and the time.
- See the dining room as a floor plan, or in 3D on devices that support it, and pick a free table.
- The table is held for five minutes while the guest enters their name and contact details.
- Confirm the booking.
- If the restaurant takes deposits, pay the deposit on the payment page of the restaurant's own card payment provider (Stripe by default). The restaurant receives the money directly.
- See the confirmation on screen, with a way to manage the booking.
How it is made accessible. We build every step to WCAG 2.2 AA: it should work with a keyboard, a screen reader and zoom, with visible focus, labelled fields, clear error messages, enough contrast, and motion that can be paused. The floor plan is the default and the 3D view is optional.
Where it stands. Our check of the booking flow is in progress and reports by 27 November 2026 (known issue K4). Until it reports, we say the booking flow is built to WCAG 2.2 AA, not that it fully meets it.
How we keep it accessible. We test each release of the booking flow against WCAG 2.2 AA, keep a record of each test, fix faults we find or are told about, and update this statement and the restaurant's own statement when something changes.
Who does what. We are responsible for the booking flow, the deposit step and the website templates. Each restaurant is responsible for the content it adds, such as its texts, photos and their descriptions, menus and documents, and publishes its own accessibility statement on its site, which we prepare for it.
If something on this site or on a booking page we built does not work for you, please tell us:
- email hello@tablestial.com;
- or use the form below.
Tell us the page, what went wrong, and, if you like, the device or assistive technology you use. We reply in writing within one month. If we need longer to look into it, we will tell you why within that month, and reply within two months at most.
If you need anything on this site in another format, for example as plain text by email, ask us and we will send it.
- Consumers in Latvia, about our booking service: if our reply does not solve the problem, or we do not reply in time, you can complain to the Consumer Rights Protection Centre (Patērētāju tiesību aizsardzības centrs), www.ptac.gov.lv. Please attach our reply, if you have one.
- In the United Kingdom: the Equality Advisory and Support Service (equalityadvisoryservice.com) gives free advice on discrimination, including websites you cannot use. The Equality and Human Rights Commission enforces the Equality Act 2010.
- Elsewhere in the EU: the authority in your country that supervises accessibility of services.
| Version | Date | What changed |
|---|---|---|
| 1.0 | 1 November 2026 | First statement. Based on our review of 30 October 2026 and the re-check of 1 November 2026 |
We review this statement at least every three months, and every time we fix a known issue or finish an assessment listed above.