Is my Squarespace website accessible? How to check (2026)

Q: What is WCAG 2.1 AA in plain terms?

WCAG 2.1 AA is the practical accessibility standard courts and organizations reference. Your content should be perceivable (images described, text readable), operable (works by keyboard), understandable (clear labels), and robust (works with screen readers). AA is the common real-world target.

Most small business Squarespace sites have a handful of accessibility issues, and most are fixable once you can see them. Here is what accessibility actually means, the issues we see most often, a checklist you can run today, and the fastest way to find your specific problems.

What "accessible" 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, those are accessibility barriers, and they're exactly the kind of thing that gets sites flagged.

Does Squarespace make my site accessible automatically?

Squarespace handles some structural basics in its templates (skip-navigation links, ARIA landmark regions), but it does not write your image descriptions, pick readable colors, or label your forms for you. The issues that show up in audits and demand letters are all content-level:

Alt text on images (Squarespace does not write this for you)
Labels on form fields (placeholder text is not a label)
Color contrast on text over hero photos
Accessible names on icon buttons and social links
Logical heading order across pages

Squarespace gives you the tools. Making the content accessible is the site owner's responsibility.

Most common accessibility issues on Squarespace sites

1. Missing alt text on images

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

2. Low contrast on text over hero photos

That full-width hero with white text over a photo is beautiful, and it's where contrast problems love to hide. When light text sits over a light or busy part of a photo, people with low vision cannot read it. WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text.

3. Unlabeled form fields

Every field in your contact, reservation, or newsletter form 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.

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 by a list of all links on the page, and ten identical "Read more" links tell them nothing.

5. Heading order that jumps around

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

The restaurant-specific problems most guides skip

The PDF menu problem

Most restaurant PDF menus are a flat image of text that a screen reader cannot read them. A blind customer finds the "Menu" link, opens it, and hears silence. The fix: put your menu on a real Squarespace page as actual text, with headings for each section (Appetizers, Mains, Desserts) and readable prices. Keep a PDF as a secondary download if you like, but not as the primary option.

Third-party ordering and reservation embeds

OpenTable, Tock, Resy, and delivery widgets are controlled by the third party, not by you or Squarespace. If the widget has unlabeled fields, you usually cannot fix that from your own editor. The durable answer is an accessible alternative right beside the widget: a clearly labeled phone number or email, so no customer is locked out.

DIY accessibility checklist for Squarespace owners

Run this on your most important pages: home, menu, contact, reservations. No special software needed, just your keyboard and a careful eye.

Images. Does every meaningful image have a written description? Are purely decorative images left undescribed on purpose?
Menu. Is your menu real web page text, not a PDF or an image? Can you select the menu text with your cursor? (If you cannot select it, a screen reader cannot read it.)
Color contrast. Can you comfortably read all text over photos and colored backgrounds, including in bright light?
Forms. Does every form field have a visible label that stays put, not just disappearing placeholder text?
Links and buttons. Do your link and button names make sense on their own, with no generic "click here"?
Headings. Does each page have one clear H1 and a logical heading order used for structure, not just font size?
Keyboard. Can you reach and use everything: menus, forms, buttons, embeds, with only the Tab and Enter keys, without getting stuck?
Embeds. For every third-party widget, is there an accessible backup, like a labeled phone number, right beside it?

If you breeze through, great. If you get stuck on a few items, that is normal and useful information, not a verdict.

The fastest way to see your real results

The DIY checklist catches a lot, but manual checking is slow, it is easy to miss issues you cannot perceive yourself, and accessibility drifts every time you add photos, update a menu, or run a promotion. A site that was clean in January can have new issues by March.

Run your site through katadaapp.com/scan and you will see your real violations on up to 10 pages, the same types of issues audits and demand letters cite, in about 30 seconds. No credit card, no obligation.

This page is general information, not legal advice. No tool or report can guarantee accessibility outcomes or prevent a lawsuit.

Frequently asked questions

How do I know if my Squarespace website is accessible?

Check that every meaningful image has alt text, your menu is real web page text (not a PDF), text has readable contrast, forms have visible labels, links have meaningful names, headings follow a logical order, and you can navigate by keyboard. The fastest way to see your specific issues is a free scan at katadaapp.com/scan.

Does Squarespace make my website accessible automatically?

Squarespace handles some structural basics but does not make your content accessible for you. Alt text, form labels, color contrast, and heading order all depend on how you configure your content. Those are exactly the issues audits and demand letters flag.

Is a PDF menu a problem for accessibility?

Often yes. Most PDF menus are a flat image of text that screen readers cannot read. The fix is a real web page menu with section headings and text prices. Keep a PDF as a secondary download if you like.

What is WCAG 2.1 AA in plain terms?

WCAG 2.1 AA is the practical standard courts reference. Your content should be perceivable (images described, text readable), operable (works by keyboard), understandable (clear labels), and robust (works with screen readers). AA is the common real-world target.

Can I make my Squarespace site accessible myself?

You can handle a lot with a checklist. The honest limits are that manual checking is slow, it is easy to miss issues you cannot perceive, and accessibility drifts as you update content. Monthly automated scanning catches what manual checks miss.