- Navigate without a mouse
- Correct an incomplete order
- Understand the confirmation
A customer should be able to complete the task without guessing what a control or message means.
Illustrative decision process, not a product screenshot or customer result.A customized restaurant website needs to work for customers who read enlarged text, use a keyboard, rely on assistive technology or have difficulty with small touch controls. Accessibility is part of the ordering task: choosing food, supplying necessary details and understanding whether the order was accepted.
This owner-led review helps you find practical problems and ask better questions. It is not a formal accessibility certification or a substitute for specialist testing with people who use assistive technology.
Begin with the menu rather than the homepage
Open the menu at a narrow width and increase text size. Check whether item names, prices and descriptions remain readable without overlapping controls. Long names and multiple modifiers are useful test cases because they reveal limitations that a short sample menu can hide.
Food pictures should support written information. A guest should not have to identify a dish from its photograph alone. Where an image conveys relevant information, ask how that meaning is made available to someone who cannot see it.
Make every choice understandable
A size selector needs a clear purpose. A plus button needs to identify which quantity it changes. A required choice should be explained before the customer encounters an error. Visible text, programmatic labels and predictable grouping help different users understand the same task.
W3C’s guidance on labelling controls describes associating a control with its purpose. Ask your supplier to demonstrate that relationship for menu options, quantities and checkout fields, rather than checking only whether labels look attractive.
Try a keyboard journey
Use Tab to move through the page and observe whether the current focus is visible. Check that the order of controls follows a sensible reading sequence. Open and close a menu dialog and verify that keyboard access continues in an understandable place.
| Task | What to observe | Problem worth recording |
|---|---|---|
| Select an item | Focus and item identity remain clear | Focus disappears behind a popup |
| Choose modifiers | Required and optional groups make sense | Choices have no understandable labels |
| Change quantity | The affected item is identified | Several identical unnamed buttons appear |
| Correct a field | Error and field remain connected | A generic warning gives no next step |
| Finish submission | The outcome is communicated | Visual success appears without useful feedback |
Record the exact step and control. “Accessibility is bad” is difficult to fix; “after closing the item dialog, focus cannot be located” gives the developer a reproducible problem.
Test an incomplete checkout
Leave a required field blank in an authorised test and submit once. The resulting message should explain what needs correction without deleting the rest of the basket. Do not rely solely on a red border to identify the problem.
W3C’s notification guidance recommends clear feedback about success or failure and understandable correction instructions. Ask how a screen-reader user learns about the error and how the customer returns to the relevant field. This is a useful supplier demonstration, not something a screenshot can prove.
Inspect changes that happen after an action
When a guest changes fulfilment method, the relevant fields and total may change. Verify that the new state is understandable and that hidden fields do not remain unexpectedly required. Similarly, an unavailable option should not leave the guest with a basket that appears valid but cannot be submitted.
If a timer or service cutoff affects the order, ask how the customer is informed. Avoid designing a process in which someone must read a long message and act instantly to avoid losing the basket. Assess the actual workflow with the supplier.
Include the final order state
Confirmation should identify the order and explain the next step. Distinguish received from accepted where the restaurant’s process makes that distinction. A decorative success animation cannot replace a readable status and a usable support route.
Ask the restaurant team to compare the customer’s confirmation with its own order record. Accessibility and operational accuracy meet here: the same items, choices and destination should remain understandable to both sides.
Use this review when evaluating Restrova
Review Restrova’s ordering website offering and bring these tasks to a demonstration. The related live-order video gives operating context; it is not evidence that every accessibility requirement has been independently certified.
Combine this review with the mobile checkout audit and a written acceptance record. Ask for identified issues to be resolved and retested on the delivered configuration.
Accessibility questions
Does a high automated score prove the website is accessible?
No. Automated tools detect some issues. Keyboard, screen-reader and real-task testing can reveal problems those tools do not capture.
Can I check everything from a screenshot?
No. A screenshot can reveal some visual problems, but not focus behaviour, control names or how dynamic messages are announced.
Should this wait until after launch?
Include the main ordering journey in acceptance testing. Fixing fundamental menu and checkout interaction problems earlier avoids carrying them into customer service.
Related Restrova demonstration
Use this introductory order-management walkthrough as context for the customer-to-restaurant handoff. It does not establish the app, website or exception-handling requirements in this guide; request those specific tests in your demonstration.
Restrova Live Order Demo | Online Ordering System for Restaurants
Restrova’s live-order demonstration introduces receiving and managing online customer orders. It covers the ordering side of the delivery workflow.
Watch this demonstration on YouTube · Published
Written overview, not a transcript. Use a live demonstration to verify the specific requirements in this guide.


