What we have built for, and what we have not tested.

What is built in

• Colour never carries meaning on its own. Every state that uses colour also uses words. A line that needs a decision says so; it is not merely a different shade.
• Touch targets are large. Every control is at least 44px tall, because the design target was a thumb with oil on it.
• Controls are labelled. A tick box says “Tick tomatoes” rather than “button”. Icons that sit beside text are hidden from screen readers rather than read twice.
• Text scales. Type uses relative units and reflows; nothing depends on a fixed pixel height.
• Nothing scrolls sideways. Wide content — tables, long ingredient lines — scrolls inside its own box rather than dragging the page with it.
• Steps can be read aloud using your device’s own voice, so a step can be heard rather than read while your hands are busy.
• The screen stays awake while you cook, so a guide does not go dark mid-step.

What has not been done

RecipeMirror has had no formal accessibility audit and has not been tested with a screen reader by somebody who uses one. We are not claiming a WCAG conformance level, because claiming one without testing is exactly the kind of unverified statement this product exists to avoid.

Specific things we know we have not checked: keyboard-only navigation through the whole cooking flow, focus order inside dialogs, and how the guide reads aloud when the source language differs from the interface language.

If something is unusable

Tell us what you were trying to do and what got in the way — email hello@recipemirror.com or use the contact form. A person reads it. We do not publish a response-time commitment yet because we will not state one we cannot keep.