Start With The Guest Tasks
Review the paths a guest actually uses: read the menu, find hours, choose a location, reserve a table, order takeout, buy a gift card, request catering, ask about allergens, and contact the restaurant.
A beautiful homepage matters less than whether someone can complete the ordering or reservation flow with keyboard navigation, meaningful labels, clear errors, and readable content.
Menu And PDF Risk
Do not rely only on an image of the menu or a hard-to-read PDF. Keep critical menu information in accessible HTML where possible, and treat downloadable menus as documents that need structure, reading order, text, links, and table handling.
If prices, allergen notes, specials, or private-event menus change often, build an update habit so the accessible version does not drift behind the visual or PDF version.
Ordering, Reservations, And Third-Party Widgets
Restaurant websites often depend on reservation widgets, delivery apps, online ordering platforms, maps, chat, loyalty tools, review widgets, and payment handoffs. List each third-party tool, who owns it, and what can be fixed internally versus escalated to the vendor.
For forms, W3C guidance supports clear labels, grouped controls, instructions, and accessible validation. That matters for reservations, catering requests, event inquiries, gift cards, and checkout.
Evidence To Keep
Keep a simple evidence folder with the public-page snapshot, menu inventory, PDF or HTML menu status, ordering and reservation notes, third-party widget list, remediation tickets, retest dates, and accessibility statement updates.
If there is a demand letter or lawsuit pressure, speak with counsel first and avoid public claims that the site is fully compliant or that a provider has ended legal risk.
Decision path
Use these links to move from research to evidence, then from evidence to a responsible remediation option.
Downloadable assets
Optional follow-up
Want help using these asset?
Direct downloads stay available above. Share a work email only if you want a tailored note on how to use the asset for your site, client, or article.
Frequently asked questions
Should a restaurant menu be HTML or PDF?
Accessible HTML is often easier to keep usable and current. PDFs may still be needed, but they should not be the only way to read critical menu, allergen, pricing, or ordering information.
Do restaurant ordering and reservation widgets need review?
Yes. Even when a third party owns the widget, guests experience it as part of the restaurant website. Track the owner, limitations, and escalation path.
Does this checklist guarantee ADA compliance?
No. It is technical planning guidance for public website review. It does not replace counsel, manual testing, or a full WCAG audit.