Η προσβασιμότητα στη Angie Eats

• Everything is reachable by keyboard

  Every screen starts with a skip link to the content, and focus is drawn with a 3px outline that is never removed for aesthetics. Dialogs take focus when they open and hand it back to the control that opened them.

• Targets sized for a real finger

  Interactive controls are at least 44px, and most are 48px. On the restaurant tablet they are 56px — that screen is used by someone wearing kitchen gloves.

• Text can be enlarged

  Zoom is not locked, up to 500%. Base body text is 18px rather than the usual 16px, and layouts reflow to a single column rather than requiring sideways scrolling.

• Colour is never the only signal

  Order states carry a label and a position as well as a colour, so the kitchen rail is readable by someone who is colour-blind. Errors are text, not a red border on its own.

• Motion respects your settings

  With “reduce motion” enabled at the operating system level, animations and transitions stop — including the pulse on a new order, which somebody stands in front of for eight hours.

• Dark mode follows your device

  The whole platform switches with the system preference, and an explicit choice overrides it in either direction.

• Screen readers are told what changed

  Search announces how many restaurants came back and under which filters. Errors are announced when they appear rather than sitting silently on the page.

• Nothing moves under your finger

  The scrollbar gutter is reserved permanently so that opening a dialog cannot shift the page sideways, and elements that load late are given their space in advance.

Angie Eats has not been audited by an independent accessibility specialist, and this page does not claim conformance with WCAG 2.2 at any level. WCAG 2.2 AA is the standard the work is aimed at, and we will say so properly when somebody qualified has tested it and we can publish what they found.

Known gaps, so you do not have to discover them: the maps used for delivery zones are visual tools without an equivalent text interface; the platform has not been tested against every screen reader and browser combination; and some staff-facing reporting screens are dense tables built for scanning rather than for narration.

If something on Angie Eats stopped you doing what you came to do, tell us what you were trying to do, what happened, and what you were using — browser, device, and any assistive technology. That is enough for us to reproduce it, which is what turns a report into a fix.

◻Accessibility contact address — not published yet

If it is blocking a live order, use the report-a-problem route on the order itself — that reaches an operator immediately, and the accessibility fix can follow afterwards.

Last reviewed 30 July 2026.