← All posts

Is a PDF Menu ADA Accessible? A Cafe Owner's Answer

5 min read

Usually not. Many PDF menus are just a picture of text, and even PDFs with real text are rarely tagged, so a screen reader either skips the menu or reads it out of order. The most accessible fix is a real menu on a regular web page. Restaurant and cafe sites also tend to share four other problems that plaintiffs look for, photos without descriptions, unlabeled reservation and order forms, text over photos, and icon buttons with no names.

Short answer: usually not. Many PDF menus are just a picture of text, and a screen reader cannot read a picture. Even when a PDF has real text in it, it is rarely set up so a screen reader can follow it. The most accessible fix is a real menu on a regular web page.

The part of the website nobody thinks about

If you run a cafe or a restaurant, your website is probably the least loved thing you own. You built it once, uploaded a menu, added a reservation or order button, and went back to the hundred other things that keep the doors open.

Then one day a letter shows up. Sometimes it is about the building: the counter is too high, the restroom door is too narrow. It is often the same plaintiff going up and down the street, business after business. And then the website claims start, and they can keep coming even after you fix what the first one named.

That is what happened to us at our cafe in Southern California. Between the physical ADA lawsuit and the website lawsuits that came after it, it set us back many years. Nobody had told us the pretty PDF menu we uploaded was one of the first things a plaintiff's lawyer would look at. So here is what we learned, in plain English.

What "accessible" actually means

An accessible website is one that a person using a screen reader, a keyboard instead of a mouse, or zoomed in text can still use. They can read your menu, find your hours, and order or book a table.

The checklist most people go by is called WCAG 2.1 AA. It sounds technical, but most of it is common sense: text you can read against its background, photos with descriptions, buttons that say what they do, and forms with labels. Our guide covers how this works on a Squarespace site.

The five problems on almost every restaurant and cafe site

1. The PDF menu. This is the big one. A guest who is blind opens your menu and their screen reader says nothing, or reads prices with no dishes next to them. The fix is putting the menu on a real page in Squarespace. Keep the PDF as a download for printing if you like, but the web page is the one that counts.

2. Photos with no descriptions. Food sites are full of photos, and that is a good thing. But every photo needs a short description, called alt text, so a screen reader can say "iced matcha latte with oat milk" instead of just "image."

3. Reservation and order forms with no labels. If a field only shows gray "Name" text inside the box, and nothing is actually attached to it, a screen reader may not tell the guest what to type.

4. Text over photos. White text over a photo of your pastry case looks great. It can also fail the contrast rule, which asks for a ratio of at least 4.5 to 1 for regular text. Your eyes may say it is fine. A contrast checker often will not.

5. Icon buttons with no names. The little Instagram icon, the menu icon, the shopping bag. If nothing tells the code what they are, a screen reader just says "button."

We cover the longer version of this list on our restaurant website accessibility page.

What about the widgets?

You have probably seen the little floating icon in the corner of some websites, promising to fix everything with one line of code. We looked at those too, back when we were trying to make the letters stop.

The problem is that widgets sit on top of your site. They do not change the site underneath. The PDF menu is still a picture. The unlabeled form is still unlabeled. Here is more on why overlays and real fixes are different.

If you already got a letter

Do not ignore it, and do not panic and pay it. Talk to an attorney who knows ADA website claims. We are not lawyers and this is not legal advice. Our page on what to do with an ADA website demand letter walks through the first steps.

What we can tell you from experience: a dated record showing you found and fixed real problems on your site is a much better place to stand than having nothing at all.

Where to start this week

You do not need to fix everything at once. If you have an hour:

  1. Put your menu on a real web page, and keep the PDF only as a download.
  2. Add a short description to your top ten photos.
  3. Make sure every form field has a visible label.
  4. Run a free scan so you know what else is hiding.

The scan takes about two minutes, with no card and no sales call. Run the free scan at katadaapp.com/scan to see what a screen reader would trip over on your site, in words you can follow.

If you would rather not do it yourself, that is what we built Kat ADA for. We fix the real problems inside your Squarespace site, then send you a dated report every month showing what was checked and fixed. You can see a sample report here. We wanted it to be affordable for owners like us, so plans start at $29 a month, billed annually.

If your scan comes back with a few things, that is normal. Most restaurant and cafe sites do. Better to know now than to find out from a stranger's letter.

Kat

No tool or report can guarantee you will not face a claim, and this is not legal advice.

Frequently asked questions

Is a PDF menu ADA accessible?

Usually not. Many PDF menus are a scanned image or an export from a design app, which a screen reader cannot read at all. Even PDFs with real text are rarely tagged, so the dishes and prices can be read out of order. A PDF can be made accessible with proper tagging, but for most restaurants the simpler fix is a real menu on a regular web page.

Do I have to remove my PDF menu?

Not necessarily. Many owners keep the PDF as an optional download for printing, as long as the same menu is also on a regular web page that everyone can read. The web page version is the one that matters for guests using a screen reader.

Why do restaurants and cafes get so many website ADA claims?

Restaurant sites tend to have the same problems, like PDF menus, lots of photos with no descriptions, reservation and ordering forms, and text placed over photos. That makes them easy to find and easy to cite. A few plaintiff firms send claims to many small businesses at once, often along the same street.

Will an accessibility widget fix my PDF menu?

No. A widget sits on top of your site and does not change the PDF or the page underneath it. The menu is still a picture of text to a screen reader. Real fixes to the site itself, plus a real menu page, are what change what a guest using assistive technology can actually read.

How do I find out what else is wrong with my restaurant website?

Run a free scan at katadaapp.com/scan. It takes about two minutes, needs no credit card, and shows what a screen reader would trip over on your site in plain English. This is general information, not legal advice, and no tool can guarantee you will not face a claim.