Accessibility

Last updated:

I think a website that some people can't use isn't finished. This page sets out what I aim for and how to tell me when I fall short. This is a sensible placeholder statement, not a legal guarantee.

What I aim for

I aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at AA level across this site. In practice that means readable text and sensible contrast, content that works with a keyboard and a screen reader, clear focus states, meaningful alt text on images, and pages that make sense when you increase the text size or turn off styling.

How I build with access in mind

I use plain, semantic markup, test with a keyboard as well as a mouse, and check that the site holds up on a phone and at larger text sizes. Accessibility isn't a box I tick at the end — it's part of how the thing gets built.

I know it won't be perfect

No site is flawless, and standards move on. If something here is hard to use, that's a bug I want to hear about — not a bother.

Reporting a problem

If you hit an accessibility barrier on this site, please email hello@breakfastdept.com. Tell me the page and what went wrong — as much or as little detail as you can. I'll come back to you, and I'll fix genuine issues as quickly as I reasonably can.