Accessibility

Ordering food should not require good eyesight, a steady hand or a mouse. Here is what we have done, what we have not, and how to tell us when we have got it wrong.

Last reviewed 26 August 2026 · Target: WCAG 2.2 Level AA

Where we stand

We aim to meet WCAG 2.2 Level AA. We believe the site substantially meets it, with the known gaps listed further down. We have not yet had an independent audit; when we do, we will publish what it finds, including the parts that fail.

What we have built in

Using it without a mouse

Every control is reachable with Tab and operated with Enter or Space. Nothing needs a hover, a drag or a long press to work.
The ingredient picker scrolls, but it does not have to be dragged: it has up and down buttons, it responds to the arrow keys, and every ingredient in it is an ordinary button you can tab to and press.
A visible focus outline follows you. We have not removed it anywhere.
A Skip to link is the first thing on every page, so a keyboard user does not tab through the navigation on every visit.
The box builder opens in a dialog that can be closed with Escape as well as its close button.

Using it with a screen reader

Pages are built from real headings in order, real lists, real buttons and real form labels, rather than styled divs.
Every form field has a label that is permanently visible, not a placeholder that disappears the moment you type.
Buttons that toggle something report their state with aria-pressed, so you are told whether lunch is on or off rather than having to guess from a colour.
Images that carry meaning have descriptions. Images that are decoration are marked so they are skipped rather than read out.
The rotating macro graphic has a written description that says the same thing — the calories and the grams of each macro — and every number in it is also printed as text underneath.
Errors are written in words next to the thing that is wrong, never signalled by a red border alone.

Seeing it

Body text is 17px with a 1.6 line height, and every combination of text and background on the site meets or exceeds the 4.5:1 contrast minimum.
The page reflows to a single column and stays usable at 400 percent zoom, and on a 320px screen, without anything scrolling sideways.
Nothing is communicated by colour alone. A selected card also carries a tick and a border; a discount line also says what it is.
Text can be resized by your browser without anything overlapping, because the layout is built in relative units.

Motion

If your device is set to Reduce Motion, we honour it. The macro graphic stops turning, transitions between steps become instant, counters jump to their value, and the animation libraries are not even downloaded.
Nothing on the site flashes. There is no content that moves for longer than five seconds without stopping, and nothing auto-plays with sound.
No animation is required to understand anything. Every animated thing is also readable when it is still.

Touch and motor

Every tap target is at least 44 by 44 pixels, and the day and meal choosers are considerably larger than that.
Nothing depends on a precise gesture. Dragging the macro platter or the day dial is a convenience; buttons do the same job.
There is no time limit anywhere. A part-built week is saved as you go, so you can leave and come back tomorrow.

Reading it

We write in plain English and avoid jargon. Where a term is unavoidable — macros, TDEE — it is explained the first time it appears.
Prices are given as whole numbers with the currency spelled out.
Nutrition is given as both a figure and a plain sentence.

Known gaps

Listing these is more useful than claiming we have none.

The ingredient picker is unusual. It is a scrolling reel rather than a plain list. It is fully keyboard operable and announces the chosen item, but it is a novel pattern and may take a moment to learn with a screen reader. If you would prefer a plain list, tell us and we will add it as an option.
The week calendar is dense. On a small screen with large text it becomes a long column. It is readable, but it is a lot of scrolling. We are looking at a summary view.
No independent audit yet. Everything above is our own testing with keyboard, VoiceOver, and browser zoom. We have not had an external expert go through it.
Arabic. The site is English only. A right-to-left Arabic version is planned and not yet built.
PDF invoices are not yet tagged for screen readers. Ask us and we will send the same information as plain text or in an email.

If you cannot use part of the site

Two things are true at once: we want to fix it, and you should not have to wait for us to fix it before you can eat.

Order by phone. Call between 06:00 and 21:00 and we will build the week with you and read the price back. There is no surcharge and no difference in the plan.
Order by email. Write to and we will send back a plain text summary to confirm.
WhatsApp. The same number takes messages and voice notes.

Telling us about a problem

Email with "accessibility" in the subject. It helps if you can say what page, what you were trying to do, and what you are using — a screen reader and its version, a magnifier, voice control, a keyboard only.

We reply within five working days with either a fix, a date for one, or an honest explanation of why we cannot. If a barrier stops you ordering, we will take the order over the phone in the same reply.

How this was tested

Keyboard only, through the whole ordering flow, on Chrome, Safari and Firefox.
VoiceOver on macOS and iOS through the ordering flow and the tracker.
Browser zoom to 400 percent, and a 320px viewport, checking for sideways scroll.
Contrast checked against WCAG 2.2 AA for every text and background pair.
Reduced Motion turned on, confirming nothing is lost and nothing keeps moving.