Statement
Accessibility
We aim at WCAG 2.2 Level AA. We have not had an independent audit, so this page describes what is built and tested rather than claiming a conformance level we cannot evidence.
What is in place
- A skip link to the main content as the first focusable element on every page.
- One
<h1>per page and a real heading order, with landmarks (header, main, nav, footer) on every route including the 404 page. - Full keyboard operation: search suggestions are reachable with the arrow keys, Home, End, Enter and Escape; the mood filter is a radio group you move through with the arrow keys; pagination is real links.
- Visible focus styles that are never removed, and descriptive names on icon-only controls such as the bookmark toggle.
- Meaningful alternative text on recipe photography, and empty
altonly on images that repeat adjacent text. - A live region announcing how many search suggestions are available as you type.
- Motion: hover-zoom and transitions are disabled under
prefers-reduced-motion. There is no autoplaying video, no carousel and no content that moves on its own. - A declared dark colour scheme, so native controls and scrollbars render in their dark variants rather than as light widgets on a dark page.
Known gaps
We are being specific here because a vague statement is not useful to anyone deciding whether they can use the site.
- No independent audit and no assistive-technology user testing has been carried out. Our checks are automated tooling plus keyboard testing.
- Some decorative text is set at small sizes with wide letter-spacing for the editorial look. It meets contrast requirements, but it is small.
- Recipes do not yet carry structured allergen or dietary metadata, which would help people filter by need rather than by reading every ingredient list.
Report a barrier
If something here is unusable with a screen reader, a keyboard, magnification, or at the text size you need, we treat that as a defect rather than a suggestion. Write to kevynsgrin@gmail.com and tell us the page, what you were using and what happened. See also our contact page.