Accessibility

Accessibility at Food Says Hi

This site should be usable with a keyboard, a screen reader, zoom or reduced motion — and honest about where it falls short.

Every table.
Every reader.

Our commitment

Food Says Hi aims to meet WCAG 2.2 AA across the site. This is a working commitment, not a formal audit or certification — we keep checking the pages described below and fix what we find.

Last reviewed:

What the site does today

  • Every control is a real link, button or native form element, so the whole site can be used with a keyboard. A skip link at the top of each page jumps to the main content.
  • Links, buttons, form fields and menu toggles show a visible focus outline.
  • Editorial photographs and guide artwork carry descriptive alt text, or an empty alt attribute where they are decorative; coded figures and status cards describe themselves in text.
  • Pages are built to reflow at narrow widths and high zoom — checked at 320 px wide and 200% zoom.
  • Interface motion is optional: with “reduce motion” on, smooth scrolling, entrance and hover animations switch off.
  • Pages are server-rendered, so the text of every page is readable without JavaScript, with headings and landmarks in order.
  • The mobile menu is a native toggle that announces its label and opens by keyboard.

Known limitations

  • The live lookup on the scanner page needs JavaScript. Without it, a notice explains the limit and links to the guides.
  • Lookup readings are generated text. The wording of the same uncertainty can differ between lookups, and a screen reader hears the result as written.
  • Editorial photos and guide artwork are illustrative. They have alt text or are marked decorative, but they do not document a particular dish or serving.
  • The Food Passport uses this browser’s local storage. Where storage is unavailable the page says so, but saved notes cannot be kept there.

Report a barrier

Found something hard to use? Tell us and we will look at it.

hello@foodsayshi.com

Use the subject “Accessibility” — the link above starts that subject for you. When you can, include:

  • the page or feature you were using
  • your device, browser, and any assistive technology
  • what you expected, and what happened instead

We read every message and aim to reply within a few working days.