Accessibility statement

Where we stand

Our goal is level AA of the WCAG 2.2 guidelines. Today we meet it only in part: we reviewed it ourselves, nobody outside has audited it, and it still has to be tested with screen readers.

What we tested

On November 1, 2026 we reviewed these screens, on sample menus, at phone and computer sizes:

• The public menu.
• Ordering: from choosing how you want it to the form with your details. We did not send any orders.
• Booking: from choosing how many people to the form with your details. We did not send any bookings.

We reviewed them in three ways:

• With an automatic tool (axe) that looks for known problems.
• With the keyboard only: that everything can be reached and you can see where you are.
• On screens 320 pixels wide and with zoom, to see that nothing gets cut off.

What we found, we fixed, except for what we list below.

What we know is missing

• We did not test with screen readers (VoiceOver, TalkBack or NVDA) or with people with disabilities.
• Each restaurant chooses its colors, fonts and photos, and we respect its design. Text over a photo can be hard to read: no tool measures that on its own.
• The virtual waiter chat uses white letters on the restaurant's color. If that color is light, it is hard to read.
• Each restaurant writes its dishes and uploads its photos. Those texts are its own, and photos are described only by the dish's name.
• If you pay by card or Mercado Pago, you end up on the payment provider's page. That page is not ours.
• We have not yet reviewed order tracking, paying the bill from the table, the waitlist, reviews, the menu's PDF or the restaurants' dashboard.

If something does not work for you

Write to us at support@menunode.com. Tell us which page you were on, what you wanted to do and what you use to browse (for example, a keyboard or a screen reader). If it happened on a restaurant's menu, tell us which one.

Changes

When we review again, we update this page and the date above.