How we build Chefsline to be usable by as many people as possible, what we still need to improve, and how to tell us when we fall short.
In short: Everyone should be able to order dinner. We aim to meet WCAG 2.2 AA across the whole product, and we test against real assistive tech — not just a Lighthouse score.
Chefsline is built to be usable by people with a wide range of abilities, assistive technologies, and connection speeds. This page is a working summary of what we've done, what we're still working on, and how to reach us if something doesn't work for you.
We target WCAG 2.2 level AA across the web and mobile apps. In practice that means:
Every release is manually tested with:
We also run automated scans (axe-core) on every pull request.
We're honest about what's still imperfect. As of 12 April 2026:
If you hit something that doesn't work for you, please tell us. You can:
Please include, if you can, the page or screen, the device and assistive tech you were using, and what you expected to happen. That gets us to a fix fastest.
Chefsline is committed to meeting the requirements of the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, and the Equality Act 2010, for all users of our service.
This statement was last reviewed on 12 April 2026 and will be reviewed at least annually. For the latest version, this page is always the source of truth.
Our team replies in under 4 hours, every day from 8am to midnight UK time.