Accessibility Statement
What we target, what we have verified, and what we know is not there yet.
EZ Orders · Last updated
1. What we aim for
We aim to meet WCAG 2.1 Level AA across the ordering pages, order status pages, and the restaurant dashboard.
2. What is in place
- Text contrast is checked automatically against the real stylesheet on every build, for every text colour against every background, in both light and dark themes. That check is why two contrast failures already live in dark mode were found and fixed.
- The ordering page works without JavaScript for reading a menu, and the dashboard's charts are server-rendered so their data is present in the page rather than drawn only after scripts run.
- Filters and views are plain links and forms with real URLs, so they work with keyboard navigation and can be bookmarked.
- Light and dark themes both honour the operating system setting by default.
3. What we know is not there yet
Stating these is more useful than claiming full conformance:
- The interactive chart crosshair on analytics pages is pointer-driven; the underlying figures are available in the accompanying tables and CSV export, which are the accessible path to the same data.
- We have not completed a full screen-reader audit of the dashboard.
- Menu photographs uploaded by restaurants may lack alternative text, because it is the restaurant that writes it.
4. Telling us about a problem
Email hello@ezorders.shop with the page and what went wrong. Accessibility reports go to the top of the queue, and if something blocks you from placing an order we will find another way to get it placed while we fix it.
Questions about this policy? Email hello@ezorders.shop or use the contact form. See all policies at /legal.