Accessibility is an ongoing design, content and development practice. We aim for essential functions to work with keyboards, screen readers, text enlargement and different device sizes.
We use web accessibility guidance as a working reference, but do not present the site as a finished certification: we review and remove barriers as they appear.
Perceive
Clear hierarchy, contrast, alternative text and notices that do not rely on colour alone.
Operate
Identifiable controls, visible focus and journeys that can be followed with a keyboard.
Understand
Direct language, ordered instructions and messages that explain what happened and what comes next.
How we build the interface
We use semantic structure so headings, lists, forms and navigation retain their meaning outside the visual design. Controls have accessible names and important changes are communicated visibly.
We also check that content can be enlarged and touch targets have enough space. Recipes include a simplified print view for ingredients and method.
- Keyboard-operable navigation and forms.
- Visible focus on links, buttons and fields.
- Identifiable page language and heading hierarchy.
- Reduced-motion preferences respected where relevant.
- Layouts that adapt to mobile, tablet and desktop.
JavaScript and interactive tools
Recipes, ingredients, articles and main navigation should remain readable without JavaScript. Some personal tools—saved recipes, shopping, pantry and planner—need JavaScript because they work in the browser.
That information is stored locally on the device. If local storage is blocked, pages remain readable, but those tools cannot retain changes between visits.
- Buttons expose their state through text and accessible attributes.
- Save notifications are announced without forcing a page change.
- Cooking mode provides large steps and sequential controls.
- The print view removes navigation and unnecessary images.
Limitations and help
A growing site can introduce undetected barriers, especially in specific combinations of browser, assistive technology or translated content. We prioritise problems that prevent someone from completing a task.
When reporting an issue, it helps to include the page, device, browser, assistive technology and exact step where the problem occurs. You do not need to share sensitive information.
- Choose “Technical issue” in the contact form.
- We also welcome feedback about legibility, translation or navigation.
- Corrections follow the same editorial workflow as the rest of the site.