Accessibility

The standard we work to

We target WCAG 2.1 level AA, which is the standard behind Israeli Standard 5568 and the European EN 301 549. Accessibility is checked as part of building the site, not as a one-off audit.

What has been done

• Every control is a real button or link, reachable and operable by keyboard, with a visible focus indicator. A "skip to content" link is the first stop on every page.
• Pages have a single main landmark, headings in order, and labels on every control and form field. Moving between pages moves focus to the new page and announces it.
• Text meets the AA contrast ratio in both the light and dark themes, and this is verified automatically on every change.
• The page can be zoomed and reflows down to narrow screens. Nothing blocks pinch-zoom on a phone.
• The page declares its language and reading direction before it is drawn, including right-to-left for Hebrew and Arabic. Menu text in another language is marked with that language, so a screen reader pronounces it correctly.
• Animation is reduced automatically when your system asks for less motion.

The map

The map markers are deliberately not in the keyboard tab order: there can be hundreds of them, and tabbing through every dot would be a trap rather than a feature. Every restaurant shown on the map also appears in the list beside it, which is fully keyboard accessible and carries the same information — name, distance, cuisine and certifications. The list, not the map, is the accessible path.

Known limitations

Menu content is supplied by restaurants and by community contributors, so descriptions and photo alternatives vary in quality and are not under our direct control. Some parts of the restaurant dashboard have had less testing with assistive technology than the public pages. We are working on both.

Found a problem?

If anything on this site blocked you, please tell us — describe the page and what happened, and we will fix it. This is the fastest way to get something changed.

accessibility@openfood.edeny.dev