Accessibility Statement

Our commitment

Breakfast Bake is committed to making our website usable by as many people as possible, including people who use screen readers, keyboard navigation, voice control, magnification or other assistive technologies.

Standard we aim for

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We consider the site partially conformant: most content meets the standard, with the known limitations listed below.

What we’ve done

• Semantic HTML with landmarks, one H1 per page, logical headings and a skip to content link
• Full keyboard access, visible focus outlines, and an Escape key that closes menus, dialogs and search
• Text and interface contrast that meets AA in both light and dark mode, and support for Windows high-contrast (forced colors)
• Touch targets of at least 44 × 44 pixels, larger than the WCAG 2.2 minimum
• Descriptive alternative text for every meaningful image, and decorative images hidden from screen readers
• Respect for reduced motion settings, with no auto-playing video or audio
• Recipe tools built for accessibility: the servings scaler and timers announce changes, steps can be marked done with a keyboard, and Cook Mode shows one large-print step at a time
• Clear form labels, error messages and status announcements, with no CAPTCHA puzzles by default
• A print stylesheet that produces a clean, high-contrast recipe card

Known limitations

• Some older illustrations have generic alternative text that we’re improving.
• Embedded third-party content, such as videos, may not fully meet our standards. We provide text alternatives where we can.
• Pinterest and other external share destinations are outside our control.

How we test

We test with keyboard-only navigation, VoiceOver on macOS and iOS, NVDA on Windows, browser zoom up to 400%, and automated checks (Lighthouse and axe) on every release.

Report a problem or request an alternative format

If something doesn’t work for you, or you need a recipe in a different format, please tell us. We’ll try to respond within 5 business days.

• Email: {{CONTACT_EMAIL}}
• Contact form, choosing “Accessibility”

Please include the page address and what happened. If you’re not satisfied with our response, you can contact the relevant enforcement body where you live.

Last review

This statement was last reviewed on October 31, 2026.