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.
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.
Availability and booking limits
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.
Access and preparation for the visit
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.
Test with a real service situation
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.
A coordinated update
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.
Information to gather before writing
Text menu with date or period
Separate opening hours of opening
Conditions for groups and events
Booking confirmation method
Access and contact details validated
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.
A case for preparing the content
Match each menu to its service
Fictional case: DEMO-MIDI covers Tuesday to Friday lunches; DEMO-SOIR covers Saturday dinner. Sunday information is missing.
Fictional teaching exercise: these texts and values describe no real business, course or product.
Path to check
1Choose the date
2Identify the service
3Read the right menu
4Flag missing information
Compare the wording
Avoid in this example
The same menu is available every day.
More precise wording
DEMO-MIDI menu: Tuesday to Friday lunch. Saturday dinner: DEMO-SOIR menu. Sunday: information awaiting confirmation.
Scroll the table horizontally if needed. With a keyboard, focus the table and use the arrow keys.
Three checks based on the supplied information
Starting information
What it establishes
What still needs checking
DEMO-MIDI
Tuesday to Friday lunches
Are the period and menu still current?
DEMO-SOIR
Saturday dinner service
Does the link open the right menu on a phone?
Sunday unspecified
No menu confirmed for this service
Who provides the information before publication?
A photograph of dishes establishes neither the current menu nor availability.
Match six time slots to the right menu
This fictional selection examines Tuesday to Friday lunches, Saturday dinner and Sunday lunch. The four weekday lunches link to DEMO-MIDI; Saturday dinner links to DEMO-SOIR. The Sunday lunch menu remains unverified.
Five slots have an identified menu and one lacks confirmed information. This proves neither opening hours, dish availability nor bookability. Other slots are not examined; their absence does not mean closure.
This workshop uses its own fictional snapshot. Do not combine its figures with those of another example on the page.
Six selected slots for the exercise, not a complete opening schedule. Entirely fictional example.
Tuesday
Service
Lunch
Linked menu
DEMO-MIDI
Wednesday
Service
Lunch
Linked menu
DEMO-MIDI
Thursday
Service
Lunch
Linked menu
DEMO-MIDI
Friday
Service
Lunch
Linked menu
DEMO-MIDI
Saturday
Service
Dinner
Linked menu
DEMO-SOIR
Sunday
Service
Lunch
Linked menu
Unverified
The diagram values are listed below with their labels.
Fictional teaching example: these figures are neither market statistics nor measured client results. They illustrate a calculation and its limits.
A restaurant receives 50 distinct requests for one fictional service. At the reporting time, 35 have an explicit confirmation. The other 15 are declined, withdrawn or still pending.
The proportion in this example
70%35 / 50 × 100
Requests confirmed at the reporting time
35
Distinct booking requests
50
What this figure means
70% of requests are confirmed at that point. This describes neither room occupancy nor guests actually attending.
Define the count before comparing
Fix the service and reporting time. Distinguish requests, confirmations, cancellations and attendance; an amendment must not create a new request.
A fictional breakdown consistent with this snapshot is 35 confirmations, 8 refusals, 2 withdrawals and 5 pending requests. The four states add up to 50 requests. Keep status-change dates so an open period is not compared silently with a closed one.
A practical check on the website
Make clear whether submission is a request or a confirmation. Test the on-screen message, the email received and a fully booked time slot.
What the calculation cannot establish
Flag differences between an ordinary lunch and a special service. Review pending requests separately.
Try with your own counts
Use two counts from the same group and period, with the same unit. The selected cases must belong to the reference total. Leave unknown values blank.
Whole counts only, up to one billion. Formula: selected cases ÷ reference total × 100. The displayed percentage is rounded to one decimal place.
These values stay in this page without being sent or saved. The calculation provides no benchmark, prediction or quality score.
To document real data, keep its origin, scope and quality limitations clear. Method reference : W3C · Data on the Web Best Practices (in English) · Consulted on . This source does not supply the fictional figures above.
A content model to maintain
Associate each menu with a service and period without confusing venue opening with kitchen availability. A useful exercise combines an evening with a special menu and a nearby exceptional closure. Visitors should understand which offer applies to their visit even when arriving through an old page.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
A content model to maintain
Information
Content to retain
Consistency check
Service offer
Identify the menu, dishes or set meals, confirmed prices and applicable dates or services. Define the wording shown when an offer has ended.
Open an old menu link: validity should remain explicit and a current offer reachable where available, without retaining an ambiguous reservation action.
Opening and arrivals
Distinguish venue opening, service hours and latest accepted arrival. Associate exceptions with specific dates.
Compare a visit before service, a late arrival and an exceptional closure. The record and booking channel should state compatible conditions.
Reservation
Channel used, request state and group arrangements.
The button and email both explain whether the table is confirmed.
Access
Exact address, entrance and verified access information.
The map points to the restaurant rather than a delivery address.
Menu and service
Separate the regular menu, daily menu, service days and availability confirmed by the team.
Read the menu on a phone, then check that a removed dish is no longer advertised in another language.
A focused next step
Have the person managing service review a dated record, then replay the journey on a phone with a late arrival. Check information before and after transfer to the booking provider. Where uncertain, offer the appropriate contact rather than a confirmation the restaurant cannot fulfil.
Schema.org: Restaurant — a reference for describing information, not evidence of a particular business or a guarantee of search features. · Source consulted
The HTML page, PDF and photograph show different dishes or prices. Visitors cannot identify the current menu.
Proposed check
Compare one dish across all three formats and confirm the approved version with the restaurant. Date it, remove replaced documents and test downloads. Relevant food information must be validated by the competent person.
Evidence to retain
Keep the approved menu reference and corrected supports. Check from a phone that an old image is no longer presented as the current menu.
Fictional finding example
Approved demonstration menu: €18. The page and booking journey show €18, but a menu image still says €16.
Interpret this outcome
Correct or replace the outdated image. Consistent text pricing is insufficient when the photographed menu continues to show a different offer.
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.
Documents and information to prepare
dated menu and person responsible for its validation
Usual times and calendar of exceptional closures
Link and actual operation of the reservation system
Contact details and access information verified
Expected response when the service or slot is unavailable
Acceptance criteria
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.
The menu remains readable without necessarily downloading a PDF.
Prices and titles agree between page and dated document.
An exceptional closure is visible before booking.
A booking link indicates the external service used.
A pending request does not display a confirmed reservation.
The published food information is validated by the establishment.
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.
Booking request
When to choose it
Suitable when the team checks availability manually. Visitors provide the date, preferred time, party size and contact details.
What to plan for
The page and receipt message must explain that the table still needs confirmation. Organise how requests are handled outside opening hours.
Confirmed online booking
When to choose it
Consider this when a tool reliably manages time slots and capacity. Visitors receive a clear status and can find their booking instructions.
What to plan for
Test date changes, fully booked slots and interruptions. Check that phone and online bookings cannot allocate the same capacity twice.
A risk to anticipate
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.
How to decide
Try finding lunch for today, then planning a group visit. Both workflows should explain the offer and next action without conflicting information.
Compare readable menus, hours and booking within the same scope. An enquiry requiring staff confirmation differs from a table confirmed through a capacity system.
Recurring operation
Assign menu updates, closures and booking maintenance. Where per-booking charges exist, document the assumed volume instead of concealing them in a fixed subscription.
Exit and handover
Check recovery of menus, images and public information. Plan replacement booking links and ongoing enquiries without publishing guests’ personal details.
Publish dishes, prices, relevant services and validity period as page text. A menu photograph may illustrate presentation but should not be the only carrier of essential information. Have the venue approve details and give a clear contact route for questions requiring its answer.
How should group enquiries differ from ordinary table bookings?
Agree when the restaurant needs a separate review, considering party size, private use, menu or time. Route that case to a group enquiry with an explicit status. Its summary should retain the date, party size and pending confirmation rather than imply an already reserved table.
What should be corrected when an old menu keeps circulating?
Identify its period and the pages or links still distributing it. Give the current menu a clear address, correct links controlled by the restaurant and label archives. Also check sharing previews; an old image may remain visible after the page copy is corrected.
How can a menu be replaced without leaving conflicting versions?
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.