Chefsline
Trust · Accessibility

A dinner everyone can order.

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.

Last updated: 12 April 2026Effective: TodayPlain-English summary: at the top of every section

Our commitment

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.

Standards we aim for

We target WCAG 2.2 level AA across the web and mobile apps. In practice that means:

  • All interactive elements reachable by keyboard, with a visible focus ring.
  • Contrast ratios of 4.5:1 for body text and 3:1 for large text and UI chrome.
  • Every image, icon button, and form input has a meaningful label for screen readers.
  • No colour-only state (errors, warnings, and confirmations all use icon + text).
  • Text can be resized to 200% without breaking layout.

Assistive tech we test with

Every release is manually tested with:

  • VoiceOver on iOS and macOS (Safari)
  • TalkBack on Android (Chrome)
  • NVDA on Windows (Firefox and Chrome)
  • JAWS on Windows (Chrome)
  • Keyboard-only navigation (no mouse)
  • OS-level Reduce Motion and High Contrast modes

We also run automated scans (axe-core) on every pull request.

Known issues

We're honest about what's still imperfect. As of 12 April 2026:

  • The live order-tracking map doesn't yet announce rider movements to screen readers. We're shipping a text-based tracking panel in May 2026.
  • Some long-form restaurant menus can be slow to navigate with a screen reader on poor connections — we're rebuilding the menu renderer this quarter.
  • Our marketing site uses a handful of decorative illustrations that don't yet have alt text on very old cached pages. Flag any you spot.

Report a barrier

If you hit something that doesn't work for you, please tell us. You can:

  • Email accessibility@chefsline.co.uk — we read every message and reply within 2 working days.
  • Use the contact form and pick “Something else”.
  • Phone 020 4515 4000, 9am–11pm UK time — we can take orders over the phone if the app isn't working for you.

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.

Formal accessibility statement

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.

Still have questions?

Our team replies in under 4 hours, every day from 8am to midnight UK time.

Help centreContact us
Accessibility · Chefsline