Skip to main content

Accessibility Statement

Last updated

Concept project. Dummy Waiter is a concept and portfolio project built by an independent developer. It is not a commercial service. No hardware is for sale, no payments are taken, and nothing on this site is an offer to sell. This page describes how the demonstration site and working prototype actually behave.

This statement describes how accessible Dummy Waiter is today, what is known to fall short, and how to tell us about a problem.

In short

  • The target is WCAG 2.2 Level AA across the whole site.
  • Status: partially conformant. This is a self-assessment, not an independent audit.
  • If something blocks you, email hello@dummywaiter.com with the subject “Accessibility”.

1.Our commitment

Dummy Waiter is a portfolio project, and accessibility is part of the craft it is meant to show. The aim is a site that people can use with a keyboard, a screen reader, voice control, magnification, or a reduced-motion setting, as well as with a mouse or touchscreen.

The target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab) at Level AA.

2.Conformance status and scope

Partially conformant. That means some parts of the site meet WCAG 2.2 AA and some do not yet. The known gaps are listed below.

This statement covers the public website (landing page and legal pages), the no-login demo, and the sign-in dashboard prototype. It is based on a self-assessment by the developer. No independent third-party audit has been carried out.

3.What has been done

The legal pages, the cookie notice, and the footer were built to these standards:

  • Semantic HTML: landmarks, one main heading per page, and a logical heading order, plus a “Skip to main content” link.
  • Everything works with a keyboard alone, with visible focus indicators. The cookie notice does not take focus or block the page.
  • Body text meets the 4.5:1 contrast ratio against its background, and links within text are underlined so they do not rely on colour alone.
  • Data tables have captions and header cells, and scrollable tables can be reached and scrolled with the keyboard.
  • Layouts reflow on narrow screens and when text is enlarged, without horizontal page scrolling.
  • Smooth scrolling, the cookie notice and the landing page animations respect your device’s reduced-motion setting.
  • Links that open a new tab say so to screen reader users.
  • The legal pages have a print stylesheet that uses black text on white.

4.Known limitations

We know about the following issues and are working through them:

  • Floor plan editor. Placing tables, walls, and other items on the canvas is mostly done by dragging. Table details can be changed with form controls, but moving items with the keyboard is limited.
  • Analytics charts. Charts give limited text alternatives, so some trends may be hard to read with a screen reader.
  • Voice ordering. Recording an order depends on a microphone and on speaking. Items can also be added by hand on the Orders screen.
  • Automatic screen lock. The dashboard locks after 10 minutes of inactivity as a security measure. The timeout cannot be adjusted yet, and you reopen the screen with your PIN.
  • Colour contrast. The site uses one light theme and its text colours are chosen to meet the 4.5:1 ratio. The main colours were measured, but not every screen has been, so some secondary text may still fall below it.
  • Illustrations and motion. The sample order ticket and ticket rail on the landing page are illustrations of the product. Their text is real text in the page, but they are decorative and use made-up sample data. Their animation stops when your device asks for reduced motion.
  • Third-party screens. The Google sign-in screen is run by Google, and we cannot change its accessibility.

5.Feedback and help

If you find a barrier, or you need information from this site in another format, email hello@dummywaiter.com with the subject “Accessibility”. Please include the page address, what you were trying to do, and, if you are happy to share it, the browser and assistive technology you used.

We aim to reply within 5 business days. This is a one-person project, so please treat that as a best effort. If you are not happy with the reply, tell us and we will look again. You can also raise accessibility concerns with the relevant authority in your country.

6.Technical specifications

Accessibility of Dummy Waiter relies on HTML, CSS, JavaScript, and WAI-ARIA. The site is built with Next.js and React and is designed for current versions of Chrome, Firefox, Safari, and Edge. Source code is available at github.com/luke3321/DummyWaiter (opens in a new tab).

7.About this statement

This statement was prepared on October 5, 2026. It will be reviewed whenever a significant change ships. See also the Privacy Policy, the Terms of Service, and the Cookie Policy.