Last updated September 1, 2026
Accessibility
A hungry person should be able to order with one hand, in sunlight, with a screen reader, or with a keyboard. Here's what we've done and how to reach us when it falls short.
What's built in
- Every interactive element is reachable and operable by keyboard, with a visible green focus ring.
- Text meets WCAG 2.2 AA contrast on every surface, including green-on-cream links, which use a darker green than the buttons for that reason.
- Body text is at least 16px on phones and the layout reflows at 200% zoom without horizontal scrolling.
- Tap targets on the ordering flow, the kitchen board and the Eats Delivery Driver board are at least 44px, and the primary action on each screen is 48px or taller.
- Live regions announce cart quantity changes and order-status changes. The tracking page's progress is a real ordered list with the current step marked.
- Form fields have visible labels, correct input types (telephone, email, numeric) and clear error text next to the field.
- Images that carry meaning have descriptive alt text; decorative glyphs are hidden from assistive technology.
- Animation is minimal and is switched off entirely when your device asks for reduced motion.
- Nothing depends on color alone: paid vs cash, open vs closed, and alcohol warnings all carry a word as well as a color.
Known gaps
- The Stripe payment form is provided by Stripe and follows their accessibility support; we can't change its internals.
- Push notifications on iPhone require adding the board to the Home Screen first, which is an Apple constraint.
If the site isn't working for you
Call the kitchen directly; every kitchen's number is on its menu page and on the tracking page. Or email hello@frostburgeats.com and we'll take the order by hand and fix whatever got in the way. Accessibility problems get treated as bugs, not feedback.
