A Squarespace designer recently shared an experience that caught my attention.
She'd just finished building a website for a client's new brick-and-mortar boutique.
The client's lawyer recommended running an accessibility scan, so she did. The scan identified several issues, and the designer went back and fixed what she could.
Then the client ran another scan through AudioEye.
After a consultation, the company reportedly warned that her website was at high risk of a lawsuit and quoted several thousand dollars to make it compliant.
Here's where things got confusing.
Some of the issues being flagged appeared to come from Squarespace itself, rather than anything the designer had built or customized.
So what was she supposed to do?
Should her client spend thousands of dollars? Were these actual accessibility problems? And how could she fix something Squarespace controlled?
I decided to look into it.
An accessibility scan isn't a compliance verdict
This is the first thing I'd want the client to understand.
Automated accessibility scanners are useful. They can identify problems with image descriptions, color contrast, form labels, heading structure, and other elements that affect how people use a website.
But they can't tell you definitively whether your website is accessible or legally compliant.
The World Wide Web Consortium (W3C), which develops the Web Content Accessibility Guidelines (WCAG), explains this in its guidance on accessibility evaluation tools.
Some accessibility issues can't be detected automatically. Others require human judgment to determine whether something is actually a problem.
Interestingly, AudioEye acknowledges this limitation, too.
The company explains that accessibility scores aren't standardized across the industry and cannot establish whether a website conforms to WCAG or meets a particular legal standard.
In other words, a low score doesn't automatically mean your website violates the law.
And a high score doesn't guarantee that someone with a disability can actually use it.
An accessibility scan is a starting point for investigating potential problems, not a final verdict.
But accessibility lawsuits are a real concern
Now, none of this means website accessibility should be taken lightly.
Under Title III of the Americans with Disabilities Act (ADA), businesses open to the public have obligations to provide people with disabilities equal access to their goods and services.
And according to the U.S. Department of Justice, those obligations extend to the goods and services businesses offer online.
That includes retail stores like the boutique in this story.
Think about someone who relies on a screen reader visiting the website.
Can they find the store's location and hours? Browse products? Contact the business?
If the store sells online, can they complete a purchase?
These aren't hypothetical technicalities. They're real experiences that determine whether someone can use a business's website.
For private businesses covered by Title III, there isn't currently one detailed federal website regulation that defines compliance solely through a particular accessibility score or checklist.
WCAG is widely used as a technical reference, but applicable legal requirements can depend on the business, jurisdiction, and circumstances.
So when an accessibility company tells a client their website is at high risk of a lawsuit, I'd want to understand what that assessment is based on.
A scanner report alone can't establish the likelihood of a lawsuit.
That doesn't make the reported issues unimportant. It means they need to be evaluated properly.
What if the accessibility problems come from Squarespace?
This was the most interesting part of the original designer's experience.
Squarespace provides several built-in accessibility features, including keyboard focus indicators, skip-to-content links, image descriptions, and accessible checkout features.
But having those features doesn't guarantee that every Squarespace website is accessible.
There are several places where problems can originate.
The website's design and content. Poor color contrast, missing image descriptions, confusing headings, and inaccessible custom code can all create problems. Many of these are things designers can address directly.
Third-party integrations. Booking systems, pop-ups, embedded forms, and other tools can introduce their own accessibility barriers.
Squarespace-controlled components. Navigation, checkout functionality, and other platform features may contain code or behaviors that designers cannot directly change.
That last category deserves particular attention.
If a scanner flags a default Squarespace component, don't automatically assume the scanner is wrong.
But don't assume it's something you can fix, either.
First, determine whether the reported issue creates an actual accessibility barrier.
If it does, document the problem and contact Squarespace support. You may also need to investigate a workaround or get help from an accessibility specialist.
And if the problem genuinely requires a change to Squarespace's underlying platform, there's a limit to what an individual designer can accomplish.
The important thing is knowing which problems you can address and which ones require help.
Does accessibility remediation really cost thousands of dollars?
It can.
A comprehensive accessibility audit involves considerably more than running a website through a scanner.
An experienced specialist may manually test pages, evaluate keyboard and screen-reader interactions, identify barriers automated tools miss, and provide detailed recommendations for fixing them.
Depending on the engagement, the work might also include implementing those fixes, retesting the website, documenting the results, and providing ongoing monitoring.
That work takes time and expertise.
So I wouldn't automatically dismiss a quote for several thousand dollars.
But I'd want to know exactly what the client was paying for.
Is the company performing a comprehensive manual audit? Making the necessary changes? Testing those changes afterward?
Or is the quote primarily for installing software and monitoring automated findings?
Those are very different services.
And without seeing the actual report or proposed scope of work, there's no way to determine whether the quote in the original story was reasonable.
Five things I'd do before agreeing to an accessibility quote
If I were the designer in this situation, here's how I'd approach it.
1. Get the complete accessibility report
I'd start by asking for the specific issues the scanner identified.
Not just an overall score or a warning about potential lawsuits.
I'd want to know which pages were affected, what the reported problems were, which WCAG criteria applied, and whether the findings had been manually verified.
That gives us something concrete to work with.
2. Run another test
I'd use WAVE, a free accessibility evaluation tool developed by WebAIM at Utah State University.
It can help identify issues involving color contrast, missing image descriptions, page structure, and more.
But I wouldn't treat WAVE as a final authority, either.
The point isn't to keep running scans until you get a passing score.
It's to gather enough information to understand what's actually happening.
3. Test the website yourself
I'd also spend some time navigating the website without a mouse.
Can you move through the navigation using your keyboard? Open menus? Access the contact form? Tell which element has focus?
If the website has an online store, try going from a product page all the way through checkout.
I'd also want screen-reader testing, ideally performed by someone experienced with assistive technology.
The goal is to understand whether visitors can actually accomplish what they came to the website to do.
4. Separate the issues by what can be fixed
Once I had a clearer picture of the problems, I'd sort them into three categories:
Issues I can correct directly in Squarespace.
Issues involving custom code or third-party integrations.
Issues involving Squarespace-controlled functionality that require further investigation.
That would help me determine what I could handle myself and what might require outside help.
It would also prevent me from spending hours trying to fix something I don't have access to change.
5. Get a second opinion before making a major investment
If significant issues remain, I'd consider having an independent accessibility specialist review the findings.
I'd want someone who could explain which barriers matter, how they affect users, and what it would take to address them.
Before agreeing to a remediation package, I'd ask whether the price includes actual fixes, manual testing, verification, documentation, and ongoing support.
By that point, we should have a much better understanding of whether the investment is justified.
Getting help with Squarespace accessibility
Of course, not every designer wants to become an accessibility specialist.
And there's nothing wrong with getting help.
One service worth looking into is Kat ADA, which is built specifically for Squarespace websites.
Unlike accessibility overlays that make adjustments in a visitor's browser, Kat ADA's team works directly inside Squarespace to address issues with things like image descriptions, headings, links, and other elements they can modify.
The service also includes monthly monitoring and documentation of the changes made.
Plans currently start at $29 per month when billed annually for websites with 1–10 pages.
That's a different kind of service from a comprehensive independent accessibility audit, and it won't necessarily resolve every issue.
For example, some third-party integrations and platform-controlled functionality may require additional attention.
But if you're looking for help with ongoing accessibility maintenance on a Squarespace website, it's an option worth exploring.
You can run a free accessibility scan with Kat ADA to get started.
We've also previously written about why accessibility needs to be part of every Squarespace designer's practice.
Disclosure: SQSPThemes may earn a commission if you subscribe to Kat ADA through our link.
What responsibility does the website designer have?
There's another part of this situation worth discussing.
What happens when a client discovers accessibility problems after their website has already launched?
I think designers should be thinking about accessibility throughout a project, not just when a scanner raises concerns afterward.
That includes making thoughtful decisions about color contrast, image descriptions, headings, keyboard navigation, and the tools being added to a website.
But there's a difference between building with accessibility in mind and promising that a website meets every applicable legal or technical requirement.
Designers should be clear about what their services include, what testing they've performed, and where their expertise ends.
A comprehensive accessibility audit may need to be a separate engagement, particularly for websites with complex functionality.
And after launch, clients need to understand that adding new content, changing layouts, or installing integrations can introduce new accessibility issues.
That's one reason ongoing monitoring and maintenance can be valuable.
None of this automatically determines who's legally responsible for a particular issue. That depends on the circumstances and contractual obligations.
But setting expectations early can help prevent a difficult conversation later.
The bottom line
If a client came to me with an accessibility report and a quote for several thousand dollars, I wouldn't immediately tell them to pay it.
But I wouldn't tell them to ignore it, either.
I'd want to understand the actual issues, what we could fix ourselves, and what genuinely required specialized expertise.
And if their attorney was concerned about legal exposure, I'd encourage them to continue that conversation.
Because making a website accessible isn't about getting a green score from a scanner.
It's about making sure people can actually use it.
An accessibility scan can tell you where to start looking. It shouldn't be the only thing telling you what to spend.
This article provides general information about website accessibility and is not legal advice. Accessibility requirements vary by business and jurisdiction.