← All posts

Is My Squarespace Site Accessible? How to Check (2026 Guide)

Kat ADA · 14 min read · Updated June 7, 2026

If you've ever wondered whether your Squarespace site actually works for people with disabilities, you're asking the right question, and you're ahead of a lot of owners. The honest answer is that most small business Squarespace sites have a handful of accessibility issues, and most are fixable once you can see them.

This guide is for owners, not engineers. We'll cover what web accessibility and WCAG 2.1 AA mean in plain language, the issues we see most often on Squarespace sites, the problems specific to restaurants (PDF menus and reservation embeds especially), and a simple checklist you can run this afternoon. At the end, we'll be honest about when it makes sense to hand the work to a done for you service.

One note up front. This article is general information for business owners, not legal advice, and no guide or tool can guarantee any accessibility outcome.

What "web accessibility" actually means

Web accessibility means people with disabilities can perceive, understand, navigate, and use your website. That includes people who are blind or have low vision and use a screen reader, people who navigate by keyboard instead of a mouse, and people who are deaf or hard of hearing.

Picture someone ordering from your restaurant using only their keyboard and a voice that reads the screen aloud. Can they find your menu? Can they hear what's on it? Can they fill out your reservation form? If yes, your site is doing its job. If no, that's an accessibility barrier, and it's exactly the kind of thing that gets sites flagged.

What WCAG 2.1 AA means in plain language

WCAG stands for the Web Content Accessibility Guidelines, the international standard for digital accessibility. The widely referenced version is 2.1, and "AA" is the middle conformance level that courts, settlements, and most organizations treat as the practical target. (A newer WCAG 2.2 adds a few criteria, but 2.1 AA remains the common reference point in 2026.)

You don't need to memorize the guidelines. They boil down to four plain ideas, sometimes remembered as POUR.

  • Perceivable. People can take in your content. Images described, video captioned, text readable.
  • Operable. Everything works by keyboard, not just by mouse, and nothing traps them.
  • Understandable. Content and forms behave predictably, with clear labels and instructions.
  • Robust. Your code works with assistive technology like screen readers.

WCAG 2.1 AA is the specific, testable version of those four ideas. When a free scanner or a service like ours checks your site, it's measuring your pages against those criteria.

The most common accessibility issues on Squarespace sites

Squarespace is a genuinely good platform, and a Squarespace site can absolutely be accessible. But like every website builder, it doesn't write your image descriptions or pick readable colors for you. Here are the issues we see again and again.

1. Missing alt text on images

Alt text is the short written description a screen reader reads aloud in place of an image. Without it, a blind visitor hears "image" or nothing at all, a real problem when that image is your menu or your logo. This is the single most common issue we find.

How to check. On your photo heavy pages, ask whether each meaningful image has a description. Purely decorative images can be left undescribed on purpose, but anything carrying information needs alt text.

2. Low color contrast, especially text over hero photos

That full width hero photo with white text laid over it is beautiful, and it's also where contrast problems love to hide. When light text sits over a light or busy part of a photo, people with low vision (and anyone in bright sunlight) can't read it. WCAG 2.1 AA asks for a contrast ratio of at least 4.5:1 for normal text.

How to check. Look at headlines and body text over photos and colored backgrounds. If you find yourself squinting, that's a signal. A scanner will measure the exact ratios for you.

3. Unlabeled form fields

Every field in your contact form, reservation form, or newsletter signup needs a real label, not just placeholder text that vanishes when you start typing. Without labels, a screen reader user hears an empty box with no idea whether to type their name, email, or party size.

How to check. Click into each field. If the only hint is gray placeholder text, the field likely needs a proper label.

4. Vague link and button names

"Click here," "Read more," and "Learn more" repeated across a page are a real barrier. Screen reader users often navigate from a list of all the links, and ten identical "Read more" links tell them nothing. Same goes for a button announced only as "button."

How to check. Read your links out of context. "Order Now" or "View our dinner menu" makes sense on its own. "Click here" doesn't.

5. Heading order that jumps around

Headings (H1, H2, H3) aren't just styling. They're the outline a screen reader user navigates by. When a page jumps from an H1 to an H4 because that size looked nicer, the outline breaks. Each page should have one clear H1 and a logical descending structure.

How to check. Look at how headings organize the page, not just the font sizes.

6. Missing skip links and keyboard traps

A skip link lets a keyboard user jump past your navigation menu straight to the main content, instead of tabbing through every menu item on every page. Many themes handle this, but custom code can break it. And if you tab through your site and get stuck somewhere you can't tab out of, that's a keyboard trap, a serious barrier.

How to check. Put your mouse aside and press Tab from the top of a page. You should be able to reach everything and move past the menu efficiently.

Problems specific to restaurants (and what to do about them)

Restaurants and food service are among the most targeted industries for web accessibility complaints. EcomBack's 2025 dataset ranks "Restaurant/Food/Drinks" as its single most sued category, with 1,368 lawsuits (34.65% of its dataset), while UsableNet's tracker puts food service lower, around 21% and second to e-commerce. Either way, it's a real pattern, and two restaurant issues drive a lot of it. Most generic guides skip these, so we'll spend real time here.

The PDF menu problem

This is the big one. So many restaurants upload their menu as a PDF, often a beautifully designed one. The trouble is that most of those PDFs are effectively a flat image of text, and a screen reader can't read them. A blind customer finds the "Menu" button, opens it, and hears silence. They can't learn what you serve or what it costs, which is the whole reason they visited.

What to do about it. Put your menu on an actual web page as real text, with proper headings for each section (Appetizers, Mains, Desserts) and readable prices. A web page menu is easier for everyone, loads faster on phones, and is far better for SEO than a buried PDF. If you keep a PDF for download, treat it as a secondary copy behind the screen reader friendly web menu. (Properly "tagging" a PDF for accessibility is possible but fiddly and easy to get wrong, so a real web menu is almost always the better path.)

Third party ordering and reservation embeds

The other snag is the embedded widget. OpenTable, Tock, or Resy for reservations, and ordering or delivery widgets for takeout. These embeds are controlled by the third party, not by you and not by Squarespace. If the widget has unlabeled fields or poor contrast, you usually can't fix that from your own editor, because the code belongs to someone else.

What to do about it. Honesty beats a quick fix here. (1) Recognize these embeds are a known limitation you don't fully control. (2) Provide an accessible alternative right beside the widget, such as a clearly labeled phone number and email for reservations or orders, so no customer is locked out. (3) Keep a dated record noting the third party constraint and the alternative you offer. The goal is that every customer has a working way to reach you, even when one widget falls short.

A simple DIY accessibility checklist for Squarespace owners

Here's a checklist you can run today. No special software needed, just your keyboard and a careful eye. Start with your most important pages (home, menu, contact, reservations).

  1. Images. Does every meaningful image have a written description? Are purely decorative images left undescribed on purpose?
  2. Menu. Is your menu real web page text, not just a PDF or an image? Can you select the menu text with your cursor? (If you can't select it, a screen reader probably can't read it.)
  3. Color contrast. Can you comfortably read all text over photos and colored backgrounds, including in bright light?
  4. Forms. Does every form field have a visible label that stays put, not just disappearing placeholder text?
  5. Links and buttons. Do your link and button names make sense on their own, with no generic "click here"? Does every button have a name?
  6. Headings. Does each page have one clear H1 and a logical heading order, used for structure and not just font size?
  7. Keyboard. Put your mouse aside. Can you reach and use everything (menus, forms, buttons, the ordering widget) with only the Tab and Enter keys, without getting stuck?
  8. Embeds. For every third party widget (reservations, ordering), is there an accessible backup, like a labeled phone number, right beside it?
  9. Video. Does any video have captions? Captions on video hosted on outside platforms are a known limitation to flag.

If you breeze through, wonderful. If you got stuck on a few items, that's normal, and it's useful information rather than a verdict.

When to let a done for you service handle it

The DIY checklist will catch a lot, and for some owners that's enough to start. But there are honest limits. Manual checking is slow, it's easy to miss issues you can't perceive (most sighted owners have not once heard their own site through a screen reader), and accessibility isn't a one time task. Every photo you add, seasonal menu you swap in, or promotion you run can introduce new issues. A site that was accessible in January can drift by March, and catching that drift means checking again and again, which most busy owners won't keep up with.

That gap is the model we built Kat ADA around, and we'll be transparent about exactly what it is. Kat ADA is done for you accessibility for Squarespace sites. You grant our team Administrator access once, and a specialist makes the real fixes inside your own Squarespace editor. Image descriptions, button and link names, form labels, heading order, skip links, ARIA, and color contrast handled through reversible Custom CSS and Site Styles. These are real fixes to your actual content at the source, not an overlay widget that vanishes the moment its script is removed.

After the fixes, we scan every page monthly using the axe-core engine against WCAG 2.1 AA, itemize what we fix, and honestly flag what we can't, such as PDF menus, third party reservation and ordering embeds, and captions on video hosted elsewhere. Each month you get a dated PDF record of the work, documentation of your diligence and ongoing effort.

To be clear, because this honesty is the whole point of how we work, that report is documentation you can keep and share, including with your attorney. It isn't an accessibility certificate and it isn't lawsuit protection, and no tool or report, ours included, can guarantee accessibility outcomes or prevent a lawsuit. We believe in an open, accessible web. We don't believe in selling false promises.

The easiest first step is seeing your real results

You don't have to decide any of this today. The simplest thing you can do now is find out where your site actually stands.

Run a free, instant accessibility scan of your Squarespace site at katadaapp.com/scan. No credit card, no obligation. Enter your URL and you'll see your real violations on up to 10 pages, the same kinds of issues we covered above. From there, if you'd rather a human make the fixes for you and keep a monthly record, you know where to find us.

Whatever you choose, asking "is my Squarespace site accessible?" is the right first move, and you've already made it.

This article is general information for business owners, not legal advice. Kat ADA is not a law firm. For guidance on your specific situation, consult a qualified attorney. No tool or report can guarantee accessibility outcomes or prevent a lawsuit.

Frequently Asked Questions

How do I know if my Squarespace site is accessible? Start with the basics. Every meaningful image has a written description, your menu is real web page text rather than a PDF or image, text over photos has readable contrast, form fields have visible labels, links and buttons have meaningful names, headings follow a logical order, and you can navigate the whole site with only your keyboard. The fastest way to see your specific issues is a free scan at katadaapp.com/scan, which checks your pages against WCAG 2.1 AA and shows the real violations on up to 10 pages.

What is WCAG 2.1 AA in simple terms? WCAG 2.1 AA is the practical accessibility standard most organizations and courts reference. It boils down to four ideas. Your content should be perceivable (images described, text readable), operable (works by keyboard), understandable (clear labels and predictable behavior), and robust (works with screen readers). AA is the middle conformance level and the common real world target. There is a newer WCAG 2.2, but 2.1 AA remains the widely used reference point in 2026.

Is a PDF menu a problem for accessibility? Often, yes. Most restaurant PDF menus are essentially a flat image of text, and a screen reader can't read them, so a blind customer can't find out what you serve. The most durable fix is a real web page menu with proper section headings and readable prices. It's better for screen reader users, loads faster on phones, and helps your SEO. If you keep a PDF for download, treat it as a secondary copy alongside the accessible web menu.

How do I make my restaurant menu accessible on Squarespace? Build your menu as a regular Squarespace page using real text, not an uploaded image or PDF. Use clear headings for each section (Appetizers, Mains, Desserts), keep prices as text, and make sure the color contrast is readable. Test it by trying to select the menu text with your cursor. If you can select it, a screen reader can generally read it. For reservation or ordering widgets you embed from third parties, add an accessible backup such as a clearly labeled phone number right beside the widget.

Can I make my Squarespace site accessible myself, or do I need help? You can handle a lot yourself with a checklist. Image descriptions, readable contrast, labeled forms, meaningful link and button names, logical headings, and keyboard navigation. The honest limits are that manual checking is slow, it's easy to miss issues you can't perceive yourself, and accessibility drifts as you update photos, menus, and promotions. A done for you service like Kat ADA makes the real fixes inside your own editor and rescans monthly so issues don't pile up. Either way, a free scan at katadaapp.com/scan is a good place to start.

Does Kat ADA fix my Squarespace site for me? Yes. Kat ADA is done for you accessibility for Squarespace sites. You grant our team Administrator access once and a specialist makes the real fixes inside your own editor, including image descriptions, button and link names, form labels, heading order, skip links, ARIA, and color contrast through reversible styles. Real fixes at the source, not an overlay. We then scan every page monthly with the axe-core engine against WCAG 2.1 AA, itemize what we fix, honestly flag what we can't, and deliver a dated PDF record you can keep and share, including with your attorney. It isn't an accessibility certificate or lawsuit protection, and no tool can guarantee accessibility outcomes or prevent a lawsuit. Start with a free scan at katadaapp.com/scan.

Further reading: the complete Squarespace accessibility guide covers every fix in one place. Run a cafe or coffee shop? See accessibility for Squarespace cafe sites.