Legal

Accessibility Beta

A guest ordering dinner should not need good eyesight, a steady hand, or a mouse. This page says what we are building toward, what we know is not right yet, and how to tell us when we get it wrong.

RobinRun is in beta. We have not yet completed an independent accessibility audit, so nothing on this page is a claim of conformance. It describes the standard we design to and the gaps we know about. If something blocks you, tell us and we will fix it.

Last updated: 31 August 2026

What we are working toward

We design to WCAG 2.2 Level AA across the guest ordering pages and the restaurant dashboard. We treat accessibility defects as ordinary bugs with ordinary priority, not as a separate project that happens later. We have not had the product independently audited, so we are not claiming conformance to that standard yet.

What we have built for

• Keyboard navigation with visible focus indicators throughout the ordering flow.
• Text contrast of at least 4.5:1 for body copy and 3:1 for large text and interface elements.
• Semantic headings, landmarks, labelled form fields, and error messages tied to their inputs.
• Touch targets of at least 44 by 44 pixels on mobile.
• Text reflows to 320 pixels wide without horizontal scrolling, and scales to 200% without loss of content.
• Animation is suppressed for visitors who set prefers-reduced-motion.
• No information conveyed by colour alone.

Known gaps

• Some analytics charts in the dashboard do not yet expose their data as an accessible table.
• A few dashboard components have incomplete screen-reader announcements when content updates live.
• Menu photos uploaded by restaurants may lack alternative text. We prompt for it but do not currently require it.
• The kitchen display is built for a wall-mounted screen and is not optimised for screen-reader use.

We are working through these and will update this page as they close.

Assistive technology we test with

VoiceOver on iOS and macOS, TalkBack on Android, NVDA with Firefox on Windows, keyboard-only navigation, and browser zoom to 200%. This testing is internal, not a substitute for a formal audit.

If you hit a barrier

Email accessibility@robinrun.com with the page or screen, what you were trying to do, and the device, browser, and assistive technology you were using. We aim to acknowledge within two business days and to tell you a fix timeline within ten.

If you cannot complete an order because of an accessibility barrier, contact the restaurant directly by phone — every RobinRun ordering page lists its number — and tell us as well so we can fix the cause.

We want to hear about barriers, and we would rather hear about them early. Email accessibility@robinrun.com and it reaches a person, not a queue.

For restaurants using RobinRun

Two things in your control make the largest difference: write alternative text for menu photos when you upload them, and keep dish names and descriptions in plain text rather than baking them into an image. If you have an accessibility obligation of your own — for example under the Accessibility for Ontarians with Disabilities Act — email us and we will help you document how your ordering page meets it.