Skip to content
MenuAsk policy

Accessibility statement

MenuAsk operates in Israel. Our website and the menus we host are built for everyone, including people with disabilities. This statement explains what we did and how to reach us.

Last updated: 10 November 2026

1

We build MenuAsk so that everyone gets the same information and the same actions. The adjustments are part of the website itself; there is no accessibility toolbar to turn on.

The website is adapted to Israeli Standard 5568 and to WCAG 2.2 at Level AA, under the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013.

2

This statement covers the MenuAsk website, the tools restaurant owners use to import, edit and publish a menu, and the public menus hosted by MenuAsk.

Every public menu shows an accessibility icon at the edge of the screen that links to this statement. A restaurant can also publish its own accessibility information at the bottom of its menu.

Dish names, descriptions and photos are provided by each restaurant, and some links lead to services run by other companies, such as Google Maps, WhatsApp and the payment page. If something there is hard to use, write to us and we will help you get the information or complete the action.

3

We check the website with automated WCAG 2.2 A and AA scans, with the keyboard alone, at 200% zoom and on a screen 320 CSS pixels wide, in English, Hebrew and Spanish.

The website works in the current versions of Chrome, Edge, Firefox and Safari, on computers and phones. It was checked with these screen readers: NVDA on Windows, VoiceOver on iPhone and TalkBack on Android.

4

These adjustments are part of the website in desktop and mobile browsers:

  • Keyboard: every action can be reached and used with a keyboard. The website, the owner workspace and public menus start with a link that skips to the content or to the menu.
  • Focus: a visible focus ring shows where you are. A dialog takes focus when it opens, closes with the Escape key, and returns focus to the control that opened it.
  • Screen readers: pages use headings, regions and one main content area. Buttons, links and form fields have text names. Icons that are only decoration are hidden from screen readers.
  • Language and direction: each page declares its language and writing direction. Hebrew and Arabic are shown right to left. Text in a different language from the page is marked with its own language.
  • Zoom and small screens: browser zoom is never blocked. Pages reflow at 200% zoom and on a screen 320 CSS pixels wide without sideways scrolling.
  • Contrast: text has a contrast of at least 4.5:1 against its background, in every built-in menu color palette too.
  • Touch: the main buttons and links on touch screens are at least 44 by 44 CSS pixels.
  • Motion: we respect the “reduce motion” setting of your device. Public menus are then shown without animations.
  • Forms and messages: fields have labels, errors are written in text, and status and error messages are announced to screen readers. The sign-in code can be pasted or filled in automatically.
  • Images: a dish photo on the dish page has a text alternative. Images that are only decoration are hidden from screen readers.
5

What we adjusted in each part:

  • Public menu: categories are headings; the search field and the language picker have a name and a state; a dish opens with the keyboard, and focus returns to it when you close the dish.
  • Dish page: every dish has its own page, with its name, description and price as text.
  • Restaurant accessibility information: shown at the bottom of the menu in the restaurant’s own words, with its own language and direction. It opens without JavaScript too.
  • AI menu help, when a restaurant turns it on: it is optional. The full menu is always available without it, and the answer is announced to screen readers.
  • Sign-in: with a one-time code sent by email, with no password to remember.
  • Owner tools: import, editing, review and publishing. Photo cropping and cover positioning have sliders next to dragging, and dishes and categories are reordered with “Move up” and “Move down” actions.
  • Marketing website and legal pages: keyboard navigation, a mobile navigation menu that opens and closes with the keyboard, and FAQ answers that use a built-in browser control.
6

If something is hard to use, or you need information in another way, contact MenuAsk by email at support@menuask.com or on WhatsApp. Please include the page address and what you were trying to do. If useful, tell us which browser, device or assistive technology you use.

You can contact us without creating an account. We will review your message and work with you on a suitable way to get the information or the service.

7

MenuAsk gives its service online. For information about access to a restaurant, its parking, seating, toilets or on-site assistance, contact the restaurant directly. Website accessibility does not establish the physical accessibility of a venue.