Menus for
every diner.
What we build
against.
DineSights aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, across its public surfaces — the diner menu, the help center, and these policy pages — and its owner dashboard.
We consider ourselves partially conformant today: most content works well with assistive technology, and some parts are still being improved. In practice, our approach means:
- Semantic HTML and labeled controls, so screen readers announce what things are — not just what they look like.
- Menus render as real text, not images of text, so they can be enlarged, read aloud, and translated.
- Color contrast and touch-target sizes chosen for legibility first.
- No time limits on reading a menu, and no content that flashes.
- The experience runs in your phone’s own browser, so your device accessibility settings — text size, zoom, screen reader, display preferences — apply.
Where the edges
are.
Honesty beats a badge. These are the limitations we know about.
- Restaurant-provided content. Dish photos, names, and descriptions come from each restaurant. We encourage owners to write descriptive dish names and text, but we can’t guarantee the quality of photo-only information a restaurant uploads.
- QR codes require a camera. If you can’t scan, any DineSights menu can be opened directly by URL — ask staff for the link, or ask us and we’ll provide it.
- Signing in requires receiving an SMS code. If SMS doesn’t work for you, contact us and we’ll help another way.
- Ongoing audits. Not every screen has been through a full assistive-technology audit yet; we fix issues in the order they’re found, and reports go to the front of the line.
We welcome accessibility feedback and aim to respond within five business days. This statement applies to surfaces DineSights operates; each restaurant remains responsible for the accessibility of its own premises and any non-DineSights materials.
Hit a barrier?
Tell us what you were trying to do, what device and assistive technology you were using, and where it broke. We'll fix it and follow up with you.
Report an accessibility issue