How to Respond to an Accessibility Complaint (Without Panicking)

You open your inbox and find an email with legal language you were not expecting. Someone is telling you your website is not accessible. Maybe it is a formal demand letter from a law firm. Maybe it is a complaint filed with a regulatory body. Maybe it is a strongly worded email from a customer who could not complete a purchase because your checkout form did not work with their screen reader.

Your first instinct might be to panic, ignore it, or immediately call your web developer and demand they “fix everything by Friday.” All three of those reactions are understandable, and all three will make things worse.

This guide walks you through exactly what to do when you receive an accessibility complaint, step by step. No legal jargon, no technical deep-dives — just practical advice for business owners who need to respond quickly and correctly.

First: Understand What You Are Dealing With

Not all accessibility complaints are the same. Before you respond, figure out which category yours falls into:

Customer feedback or informal complaint. A real user telling you something on your site does not work for them. This is actually the best-case scenario because they are giving you free, specific information about a real barrier. Many users just leave and never come back.

Demand letter from a law firm. In the United States, this is the most common form of ADA website accessibility action. A law firm sends a letter alleging your website violates Title III of the Americans with Disabilities Act. These letters typically demand you remediate your website and pay the plaintiff’s legal fees.

Regulatory complaint. Under the European Accessibility Act (EAA), national market surveillance authorities can investigate complaints from consumers. Some EU member states allow consumers to file complaints directly with a designated authority.

Formal lawsuit. An actual legal complaint filed in court. This requires an immediate legal response — you have specific deadlines to answer the complaint.

The response strategy differs for each, but the first steps are the same.

The First 48 Hours: What to Do

1. Do not ignore it

This is the single most important piece of advice. Ignoring a demand letter does not make it go away. In the US, ignoring a lawsuit means the plaintiff can get a default judgment against you. In the EU, ignoring a regulatory complaint can escalate enforcement actions.

Even informal complaints deserve a response. The person who emailed you had a real problem. Acknowledging it costs nothing and can prevent escalation.

2. Do not admit fault in writing

Respond promptly, but carefully. A simple acknowledgment works:

“Thank you for bringing this to our attention. We take accessibility seriously and are reviewing the issues you have raised. We will follow up with more details within [timeframe].”

Do not write “we know our site is not accessible” or “we have been meaning to fix that.” Do not promise specific fixes or timelines you cannot guarantee. Do not argue that your site is fine.

3. Document everything

Save the complaint, any correspondence, and screenshots of your website as it exists today. If someone filed a formal complaint, note the date you received it, the specific claims made, and any deadlines mentioned.

4. Get a professional assessment

Before you can respond meaningfully, you need to understand the actual state of your website. Run an automated scan using a free tool like WAVE or axe DevTools to get a baseline picture.

Automated tools catch roughly 30-40% of accessibility issues. For a complete picture, you may need a manual audit by an accessibility professional. But the automated scan gives you immediate, concrete data about what is broken.

5. Consult a lawyer (for demand letters and lawsuits)

If you received a demand letter or lawsuit, consult an attorney who has experience with ADA or EAA accessibility cases. This is not optional. Many demand letters follow a pattern, and an experienced attorney can advise you on whether to negotiate, settle, or fight.

Do not use your general business attorney for this unless they have specific accessibility litigation experience. This is a specialized area of law.

Common Mistakes That Make Things Worse

Installing an accessibility overlay

When business owners panic, they often search for a quick fix and find accessibility overlay companies promising “one line of code” that makes your site compliant. This is the worst thing you can do after receiving a complaint.

Overlays do not fix the underlying code problems. They can actually introduce new accessibility barriers. Multiple courts have rejected overlay use as evidence of good faith compliance efforts. And the plaintiff’s attorney will use the overlay installation as evidence that you knew about problems but chose a superficial fix instead of genuine remediation.

Rushing a redesign

Your instinct might be to rebuild everything from scratch. Resist it. A rushed redesign often introduces new accessibility problems while failing to address the specific issues in the complaint. Instead, focus on systematic remediation of specific, documented barriers.

Ignoring the specific issues raised

If the complaint mentions specific barriers — “I could not complete checkout with a keyboard” or “your images have no alt text” — address those specific issues first. They represent real barriers experienced by real people. Fixing them demonstrates good faith and directly reduces the harm.

Going silent after the initial response

If you acknowledged the complaint and promised to follow up, follow up. Silence after a promise looks worse than the original problem. Even if progress is slow, send updates: “We have fixed 12 of the 24 issues identified and expect to complete the remaining fixes by [date].”

Building Your Remediation Plan

Once you understand the scope of the problems, create a structured plan. This serves two purposes: it guides your actual remediation work, and it documents your good faith efforts if the complaint escalates.

Prioritize by impact

Not all accessibility issues are equally urgent. Focus first on:

  1. Barriers that completely block access. Things like forms that cannot be submitted with a keyboard, content hidden from screen readers, or videos without any captions. These prevent entire groups of users from using your site at all.

  2. Issues specifically mentioned in the complaint. If someone told you exactly what is broken, fix those things first.

  3. High-traffic pages. Your homepage, product pages, checkout flow, and contact page affect the most users.

  4. Issues with known legal risk. Missing alt text, insufficient color contrast, missing form labels, and inaccessible navigation are the issues most commonly cited in lawsuits.

Set realistic timelines

Full WCAG 2.2 AA compliance is not a weekend project. A typical small business website takes 2-6 months to remediate depending on its size and complexity. An e-commerce site with thousands of product pages takes longer.

Set milestones: “Critical barriers fixed within 30 days. All high-priority issues resolved within 90 days. Ongoing monitoring and maintenance plan in place within 6 months.”

Document your progress

Keep records of every fix you make, when you made it, and what issue it addressed. Take before-and-after screenshots. Save your audit reports. This documentation is valuable evidence of good faith compliance efforts if the matter goes to court.

After the Immediate Crisis

Publish an accessibility statement

An accessibility statement on your website shows that you take accessibility seriously. It should include your commitment to accessibility, the standard you are working toward (typically WCAG 2.2 Level AA), known limitations, and a way for users to report problems.

Having a clear feedback mechanism can prevent future complaints from escalating. When users know they can report a problem and expect a response, they are less likely to go straight to a lawyer.

Establish ongoing monitoring

Accessibility is not a one-time fix. New content, new features, and platform updates can introduce new barriers. Set up regular automated scanning and periodic manual reviews. Many accessibility testing tools can run on a schedule and alert you to new issues.

Train your team

Everyone who creates content for your website needs basic accessibility training. Content editors need to know how to add alt text, create proper heading structures, and write descriptive link text. Developers need to understand keyboard navigation, ARIA attributes, and semantic HTML.

This does not require expensive courses. A two-hour internal workshop covering the most common issues can dramatically reduce the number of new accessibility barriers your team creates.

The Silver Lining

An accessibility complaint feels terrible in the moment, but it can be the catalyst for genuine improvement. Many businesses that receive complaints and respond well end up with better websites — not just more accessible, but more usable for everyone.

Accessible websites tend to load faster, work better on mobile devices, rank higher in search results, and convert more visitors into customers. The remediation work you do in response to a complaint pays dividends far beyond compliance.

The businesses that handle accessibility complaints badly are the ones that treat accessibility as a legal threat to be minimized. The ones that handle it well are the ones that treat it as a quality issue to be solved.

We’re building a simple accessibility checker for non-developers — no DevTools, no jargon. Join our waitlist to get early access.