A restaurant site is first used to check what is offered, when to come and how to book. The menu, practical information and booking route should tell the same situation, including closing days and seasonal changes.
These files describe preparation methods. They do not present customer achievements and do not replace the validation of information by the organization concerned.
All sectoral files
Publish a textual version of the menu in addition to a possible downloadable document. Organize dishes, drinks and formulas with explicit titles. Assign price validation and dish information to the person who knows them. An archived menu should be identified as old; A photo of slate alone becomes difficult to read and keep up to date.
Explain whether the request reserves a table immediately or awaits confirmation. Distinguish opening days, service hours and bookable slots. For groups, specify the appropriate channel rather than letting an individual form accept any number of people. When the slots are complete, offer a concrete sequence without displaying false availability.
Describe the address, entry and practical information that the institution has confirmed. For the accessibility of the premises, give precise characteristics instead of a vague formula. A card completes an access text but does not replace it. The menu and booking languages must remain consistent until confirmation.
Simulate a booking, change, and cancellation on a test environment. Check the recipients and the displayed time zone. Check that the constraints are announced before validation and that a message sent several times does not create confusion. Test the journey on a phone with long text and keyboard.
When the menu or schedules change, update the page, documents and platforms used by the establishment. Name a replacement person during the holidays. Give a date or period to seasonal offers and remove calls to book as soon as the event is over.
For each item, keep the source, the person validating it and the language versions concerned. Missing information must become a question to solve, never a value invented to fill the page.
Planning exercise: a visitor opens the website on a day when the restaurant is exceptionally closed, reads the food menu on their phone and tries to book a table. Use opening hours and a food menu created for the exercise. Make the dates of validity and the source of the information visible. If booking uses an external provider, explain the move to that website and the next steps. A request submitted through a form must remain a pending request until the restaurant has accepted it; it must not be shown as a confirmed reservation.
These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.
Designate a person who updates the menu and schedules, then test the route after each change of provider. A translation should be read for food names and food information; It does not replace their validation. Remove old documents from main links or archive them clearly. Keep a short procedure to publish an unexpected closure in all affected languages.
The website should help people choose a meal and plan a visit. Decide whether bookings need staff confirmation or can be confirmed by the system used at the restaurant.
A photographed menu can be unreadable on a small screen. Publish the main information as text, with a date or validity period when the menu changes.
Try finding lunch for today, then planning a group visit. Both workflows should explain the offer and next action without conflicting information.
A text page is easier to view and translate. The PDF can remain a supplement for downloading or printing.
Show only those that the institution or its tool can actually confirm, with a clear state when the request remains pending.
Put the information near the schedules and the booking button, then remove it when its period is over.
Identify the main editorial source and the pages that reuse it. Replace the menu, check translations and remove links to outdated documents. Explain any day-specific or availability-dependent limits alongside the menu.
Additional reference: W3C Wai: Structure an accessible page. The sectoral recommendations of this sheet are an editorial method; This reference does not certify the information specific to an establishment.
