Accessibility Statement

1. Our commitment

Deally wants everyone to be able to browse a menu, build an order and pay, whatever device or assistive technology they use. We are committed to making the ordering experience we provide to restaurants accessible to people with disabilities, and to improving it continuously. Accessibility is part of how we design and review new features, not an afterthought.

2. The standard we work to

Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the World Wide Web Consortium (W3C). WCAG explains how to make web content more accessible to people with visual, hearing, motor and cognitive disabilities. We treat WCAG 2.1 AA as the benchmark for every guest-facing page and for the ordering flow from menu to confirmation, and we consider WCAG 2.2 success criteria as we build new interfaces.

3. What we do

These are the standards we hold our guest-facing pages to. Where a page does not yet meet one of them, it is listed in section 4.

• Build with semantic HTML and accessible component primitives so that headings, lists, buttons, forms and dialogs are announced correctly by screen readers.
• Design mobile-first with responsive layouts that work on small screens and with browser zoom, without horizontal scrolling of body text.
• Aim for visible focus indicators and a logical keyboard order so the menu, item options, cart and checkout can be used without a mouse.
• Aim for text and colour contrast that meets the WCAG AA minimum for body text and controls, and avoid relying on colour alone to convey meaning (for example, order status is shown with words as well as colour).
• Aim to give every form field a label, clear error messages linked to the field, and sufficient target size on touch screens.
• Provide text alternatives for the images and icons we control; menu photos use the item name as their description when the restaurant supplies no other text.
• Respect the “reduce motion” preference of your operating system for our animations and transitions.
• Review new guest-facing features for accessibility before release, including keyboard-only navigation and screen-reader checks (VoiceOver on macOS and iOS), and treat reported barriers as bugs to fix.

4. Known limitations we are fixing

Despite our efforts, some parts of the ordering experience do not yet meet our target. We list them here so you know what to expect, and we are working on each one.

• Dialogs and side panels. On some ordering pages, the sign-in dialog, the item options dialog and the cart panel do not yet trap keyboard focus inside them, return focus to the control that opened them when they close, or announce a title to screen readers. We are moving these to accessible dialog components with proper names, focus management and Escape-to-close.
• Form labels. A small number of sign-in and account fields are identified only by placeholder text rather than a persistent label. We are adding visible or screen-reader-only labels to every field.
• Menu photos. Restaurants upload their own menu photos and do not always supply descriptive alternative text. Where none is supplied, the item name is used as the image description.
• Live status updates. Some order-status changes update on screen without an announcement to screen readers. We are adding live regions so changes are read out.

If one of these limitations stops you completing an order, please use one of the alternatives in section 6 or contact us (section 7) and we will help you place the order.

5. Third-party content

Some content and functionality on Deally-hosted pages is provided by others, and we cannot fully control its accessibility:

• Restaurant content. Menus, item descriptions, photos, logos, opening hours and announcements are written and uploaded by each restaurant. We give restaurants tools and guidance to add alternative text and clear descriptions, but the restaurant is responsible for the content it publishes.
• Payment fields. Card entry, saved-card selection and, where offered, Apple Pay or Google Pay buttons are provided by Stripe inside the checkout. Stripe designs these elements to meet WCAG standards and publishes its own accessibility information.
• Sign-in with Google or Apple. The sign-in windows are provided by Google and Apple under their own accessibility practices.
• Maps and links. Links to delivery partners, map providers or a restaurant's social media pages lead to sites we do not operate.

If you have difficulty with third-party content on a Deally-hosted page, tell us anyway; we will raise it with the restaurant or provider and help you complete your order.

6. Other ways to order

You never have to use the website to order from a restaurant on Deally. Every restaurant's phone number is shown on its ordering page and in order confirmation emails; staff can take your order over the phone or in person. Where a restaurant offers an AI phone assistant, you can ask to be transferred to staff where the restaurant provides that option.

If you need an order placed in another way, or need help with an order you have already placed, contact the restaurant directly or email us at support@deal-ly.com and we will coordinate with the restaurant.

7. Tell us about a barrier

We welcome feedback on the accessibility of Deally-hosted pages. If you encounter a barrier, cannot access content, or have a suggestion, email support@deal-ly.com with the subject line “Accessibility feedback.” It helps if you tell us:

• the web address (URL) of the page and the restaurant you were ordering from;
• what you were trying to do and what happened instead;
• the device, browser and any assistive technology you were using; and
• how you would like us to reply.

We aim to acknowledge every accessibility report within 2 business days, tell you how we plan to address it, and offer a way to complete your order in the meantime. Accessibility reports are reviewed by the people who build the ordering experience, not routed to an automated queue.

8. Assessment and date

This statement reflects a self-assessment of the guest ordering flow carried out by Deally in October 2026 using automated tooling, manual keyboard testing and screen-reader review. It has not yet been independently audited. We will update this page as the limitations above are resolved and after each significant change to the ordering experience, and we review it at least once a year.

Related documents: Guest Privacy Notice · Guest Terms of Sale · for restaurants using Deally, the Terms of Service and Privacy Policy.