Accessibility
Accessibility statement
Everyone who cooks should be able to use Hedgehog Chef. Here's what we aim for, what we've done, what we haven't yet, and how to tell us when something gets in your way.
Last reviewed .
What we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, in the app at app.hedgehogchef.com and on this site. We haven't had that confirmed by an outside audit yet (see known limits).
What we've done
- Contrast. Every text color meets WCAG AA contrast (at least 4.5:1) at body sizes, in the light and the dark theme, including small labels. Focus rings and control borders are at least 3:1.
- Keyboard. The app is built to be used with a keyboard, with a visible focus ring on every control. When a dialog closes, focus goes back to where you were. Cook mode steps forward and back with the arrow keys and Space.
- Screen readers. Pages use real headings in order, buttons and fields have labels, images have text alternatives (or are marked decorative), and timers and status messages are announced as they change.
- Touch. Tap targets are at least 44 pixels, and text fields don't make phones zoom in.
- Your settings. The light or dark theme follows your device unless you pick one in Settings, and animations stop when you turn on reduced motion.
- Zoom. Layouts reflow as you zoom; at very short window heights, such as a phone on its side, the bars get out of the way while you type.
- Checked in tests. Our end-to-end tests find buttons and fields by their role and label, the way a screen reader does, so an unlabeled control fails them. Every page of this site is checked for one main heading, heading order, image text alternatives and labeled landmarks, and it scored 100 in Lighthouse's accessibility audit when we last measured.
Known limits
- No outside accessibility audit yet. What's above is our own work and our own checks.
- We haven't yet tested the app from start to finish with VoiceOver on iPhone and Mac or TalkBack on Android, and automated axe checks aren't in our tests yet. Both are planned.
- Signing in happens on our sign-in provider's pages (WorkOS), payments on Stripe's, and the status page is Better Stack's. Their accessibility is up to them, though we'll pass on anything you report.
Report a problem
If something in Hedgehog Chef is hard or impossible to use, email hello@hedgehogchef.com, or in the app go to Settings › Help & what's new › Send us a message. Tell us what you were trying to do, the device and browser, and any assistive technology you use (a screen reader, switch control, magnification). A person reads every message and replies within 1 business day.
If you need something from us in another format, ask the same way.