Accessibility testing for restaurant websites

What we check

• Your menu: we test the menu page. When the menu is only a PDF or a picture, the report points it out: a screen reader or zoom often can't read it well, and a menu on the page itself works better for every guest.
• Table booking: we find your booking page. A booking service embedded from another company, such as OpenTable, is third party: the keyboard form path stops at it. Automated checks still list issues inside its frame, apart from yours, as third-party content: only that company can fix them, and they don't count in your score.
• Contact and booking forms: we reach every field with the keyboard alone, type test text and check that a wrong email shows an error people can perceive. We never send the form, so no test booking or message reaches you.
• The rest of your site: the home page and pages such as about and services, with images, headings, links, contrast and focus.

Automated testing finds many common issues; some criteria need human review. An audit adds that review. Our method page explains what we test and how the score works.

Any platform

We test your site whatever it is built with: WordPress, Wix, Squarespace or Webflow, or your own code. The report says where fixes are made on your platform.

Fixes

We fix what your audit finds where your platform allows: in a child theme on WordPress, in your content on Wix, Squarespace or Webflow, or in the code of a hand-built site. Issues inside a booking service from another company are listed apart for you to pass on. Book a call to talk about your site.

Get started

Start with a free scan of three pages, see the plans and prices, or book a call.

Get a free scanBook a call