Accessibility statement

Chef is run by WAW Etc Ltd. We want everyone who cooks to be able to use Chef — including people who use a screen reader, a keyboard or switch instead of a mouse, magnification, voice control, or who need more time, less motion or stronger contrast. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and we treat an accessibility barrier as a bug.

This statement covers:

• the Chef website and web app at chefbywaw.com, including the public recipe and cookbook pages; and
• the Chef apps for iPhone, iPad and Android.

It does not cover websites we link to, such as the original source of an imported recipe.

Chef is partially conformant with WCAG 2.2 level AA. That means most of Chef meets the standard, but some parts do not yet. The parts we know about are listed under Known limitations, with what we are doing about them.

On the web you should be able to:

• move through every page with a keyboard, with a clearly visible focus ring, and skip straight past the navigation to the content;
• zoom up to 500% and pinch-zoom anywhere, including in cook mode;
• read text that meets the WCAG contrast minimum of 4.5:1 against its background;
• tell pages apart by their titles, and move around recipes by their headings (ingredients, method, and each stage);
• hear status messages — “Saved”, “Link copied”, an undo offer — announced by your screen reader, shown for at least five seconds and held on screen while you point at them or focus them;
• open and close sheets and dialogs from the keyboard, with focus kept inside while they are open and returned afterwards;
• use Chef with reduced motion: parallax and decorative animation stop when your device asks for less motion;
• hit controls that are at least 24 by 24 pixels.

We know about the following problems. We are working on them and aim to fix them by the next review of this statement.

• Conversation with Chef. Chef’s replies are announced once they finish rather than as they are written. Progress lines on some cards (importing or adapting a recipe) may not be announced when they first appear.
• Cook mode. The extra notes on an ingredient (“finely chopped”, “made in step 2”) open on tap or hover and cannot yet be reached with a keyboard alone; the ingredient itself and every step are fully readable.
• Calendar. Meals you have skipped or already cooked are shown faded, and some of their smaller text falls below the contrast minimum. Moving a meal by dragging has a keyboard alternative on the meal’s own page (its date and Move controls) rather than in the calendar grid itself.
• Text over photographs. A few labels that sit on top of dish photographs, such as the dish names on a meal’s picture, depend on the photograph for their contrast. Some photographs, especially ones Chef creates, have generic descriptions rather than a description of the dish.
• Form field edges. Some text fields and search boxes have a pale outline below the 3:1 contrast recommended for control boundaries. Each is labelled and shows a clear focus ring when you are in it.
• Focus after closing. After you undo a removal in the calendar, or step back inside the delete-account dialog, keyboard focus may return to the top of the page rather than to a nearby control.
• Mobile apps. The iPhone, iPad and Android apps are being brought to the same standard as the web. Work on screen-reader labels, text scaling and contrast in the apps is in progress; until it is finished, some controls in the apps may not be announced clearly, and very large text sizes may crop some labels.
• Content from elsewhere. Recipes you import keep the wording and pictures of their original source, which we cannot always make accessible.

If you find a problem that is not listed here, please tell us — see below.

Chef is designed to work with:

• the current and previous major versions of Safari, Chrome, Edge and Firefox;
• VoiceOver on macOS, iOS and iPadOS, TalkBack on Android, and NVDA with Chrome or Firefox on Windows;
• browser and system zoom, text-size settings, and “reduce motion” settings.

Chef needs JavaScript to run.

If something in Chef is hard or impossible for you to use, or you need information from Chef in another format — for example a recipe as plain text, large print or read aloud — email hello@chefbywaw.com with “Accessibility” in the subject line. Tell us what you were trying to do, which page or screen, and the device and assistive technology you use if you can.

We will reply within 5 working days. If we cannot fix the problem quickly, we will tell you when we expect to, and help you do what you were trying to do another way in the meantime.

Please tell us first, so we can put it right. If you are in the United Kingdom and you are not happy with how we respond, you can contact the Equality Advisory and Support Service (EASS). If you are in the European Union, you can contact the authority in your country responsible for enforcing the European Accessibility Act.

This statement was prepared on 28 September 2026, following a review of the web app against WCAG 2.2 level AA by our own team. We check our public pages with automated accessibility tests (axe), and new work by hand with a keyboard and a screen reader. We review this statement at least every six months; the next review is due by March 2027.

See also our Terms and Conditions and Privacy Policy.