This site is built to be usable with a keyboard, a screen reader, or a phone in one hand while
the other is holding a pan. Where it falls short, we would rather hear about it than guess.
What is in place
- Semantic structure. One
h1per page, headings in order, real
lists for ingredients and steps. A screen reader can navigate a recipe by heading. - Keyboard access. Every link, the search field, the menu toggle and the
newsletter form are reachable and operable by keyboard. - Contrast. Body text is checked against its background for at least the WCAG AA
ratio of 4.5:1, and large headings for 3:1. - Images. Every recipe photo carries alt text describing the dish, not the
filename. - Text scaling. The layout is set in relative units and holds together when text
is enlarged to 200%. - No motion traps. Nothing auto-plays, nothing flashes, and nothing moves except
a small hover transition on cards.
Known gaps
Two things are honest to name rather than hide:
- Wide comparison tables scroll sideways inside their own container on narrow screens. That is
better than a squeezed layout, but it is still a horizontal scroll. - The recipe card puts ingredients and method side by side on a wide screen. Read in source
order, ingredients come first and method second, which is the order you want, but the visual
pairing is lost in a linear reading.
Telling us
If something here blocks you, the contact page reaches a person who can change the template.
Say which page and what happened; a screenshot is welcome but not required.