Accessibility
A recipe is no use if you cannot read it. Here is where we stand.
Last updated
What we aim for
We target WCAG 2.1 level AA. That is a goal we work towards rather than a certified result, and this page is meant to be an honest account rather than a badge.
In place today
- Semantic headings in order, so screen readers and skim-readers get the same structure.
- A visible focus ring on every link, button and form field for keyboard users.
- The mobile menu is a real button with
aria-expanded, and closes with Escape. - Filter results announce their count to assistive technology as they change.
- Text alternatives on photography; decorative images are hidden from screen readers.
- Body text and controls stay readable down to a 320 px viewport, with no horizontal scrolling.
- Animation is disabled for visitors who ask for reduced motion.
- Difficulty and category are always words, never colour alone.
Known gaps
- Some recipe photography still uses generic alternative text rather than a full description.
- A few placeholder illustrations remain while final photography is produced.
- We have not yet completed a full audit with screen readers on every page.
Tell us what breaks
If something is hard or impossible to use, email hello@kavovo.uk with the page address and what went wrong. Access problems are treated as bugs, not feature requests, and we will tell you what we intend to do about it.