Editor’s note: This article is a fictionalized composite case study created to illustrate the type of technical accessibility work ADA Access Group can perform in coordination with a business and its legal counsel. It does not describe a specific client, plaintiff, settlement, or court matter. Any litigation outcome depends on the facts, jurisdiction, claims, counsel, and many other factors. This is not legal advice.
When a business receives an ADA website accessibility lawsuit, one of the first questions leadership asks is usually simple: “What can we do now that actually helps?”
The answer is not a quick widget, a screenshot from an automated scanner, or a promise that one technical fix will make the case disappear. A stronger response separates legal strategy from technical accessibility work and gives counsel better evidence to work with.
This composite case study follows a large multi-location retail chain facing a website accessibility lawsuit in a federal district court in Florida. The company operated a substantial e-commerce website and was accused of creating barriers for blind and low-vision shoppers using assistive technology.
What changed the company’s position was not one magic fix. It was the combination of a targeted manual accessibility audit, fast remediation of confirmed barriers, retesting, and a recorded session with a real blind screen-reader user performing the same shopping tasks at issue in the claim.
The situation: a retail chain receives a Florida website accessibility lawsuit
The retailer had dozens of physical locations and a growing online business. Customers used its website to search products, filter results, review product information, select variants, add products to a cart, create accounts, and complete checkout.
The complaint alleged that parts of the digital shopping experience created barriers for people who use screen readers. The allegations focused on real transaction paths rather than cosmetic defects: navigation, product discovery, interactive controls, forms, and checkout.
Internally, the first reaction was predictable. Executives wanted to know how serious the problem was. Marketing believed the website was generally usable. Developers wanted exact reproduction steps. Legal counsel needed facts that could be separated from broad allegations.
That is where a targeted technical accessibility response became valuable.
The first mistake the company avoided
The company did not treat a generic automated scan as the final answer.
Automated accessibility tools can find many detectable problems quickly, including missing labels, certain semantic errors, some contrast failures, and other code-level issues. But a lawsuit involving a real shopping journey usually requires more than a scanner result.
The technical team needed to know whether a blind customer could actually perform the tasks alleged in the complaint.
That required manual testing.
Step 1: building a targeted manual accessibility audit
The audit began with the allegations in the complaint and then expanded into the templates and components that affected the same customer journeys across the website.
The review included:
- global navigation and mobile navigation;
- site search;
- category and search-result pages;
- filters and sorting controls;
- product detail pages;
- variant selectors;
- add-to-cart interactions;
- cart controls;
- account creation and login;
- checkout forms;
- error messages and validation;
- promotional dialogs and popups;
- keyboard focus behavior; and
- selected third-party components.
Instead of producing a long list of abstract WCAG failures, the audit connected every confirmed issue to a real user impact and a specific remediation path.
The audit changed the internal conversation
A developer-ready audit turns accessibility findings into a trackable remediation backlog.Before the audit, the company had two extremes inside the organization.
One group believed the website was probably fine because most customers used it successfully. Another group feared that the entire website would have to be rebuilt.
The audit replaced both assumptions with evidence.
Each confirmed issue was documented with the affected page or component, reproduction steps, user impact, relevant accessibility requirement, severity or priority, screenshots or other evidence, and recommended remediation.
The issues were then organized into a simple workflow:
identified → assigned → remediated → retested → verified
That structure gave developers a usable backlog and gave counsel a much clearer picture of what the company was actually dealing with.
Step 2: recording a real blind user navigating the retail website
Recorded real-user testing can show where a shopping journey becomes difficult to navigate with assistive technology.The most powerful part of the technical review was a recorded usability session with a real blind tester who regularly uses a screen reader.
The tester was asked to perform realistic retail tasks rather than artificial accessibility-test exercises:
- open the main navigation;
- find a product category;
- search for a specific product;
- filter the results;
- open a product page;
- understand product options;
- add an item to the cart; and
- move through the checkout process.
The recording was valuable because it made technical barriers visible to people who did not normally use assistive technology.
An executive can read a finding such as “button has no accessible name” and still not fully understand the consequence. Watching a screen-reader user encounter several unlabeled controls in a row creates a very different level of understanding.
The session also helped distinguish high-impact problems from lower-priority defects. Some issues created genuine transaction blockers. Others created friction but did not prevent task completion.
Why video evidence can be more persuasive than a scanner score
A scanner score is useful for triage, but it is an abstraction. A real-user video shows whether a person can actually complete the task.
For this composite retailer, the video created several practical benefits:
- developers could see exactly where interaction failed;
- leadership understood why the work mattered;
- the accessibility team could prioritize the most disruptive barriers;
- counsel received a more concrete technical record; and
- the company could later record or document the same workflow after remediation.
That before-and-after evidence created a much stronger story than “we installed an accessibility tool.”
Step 3: fixing the highest-impact barriers first
The company did not attempt to fix every minor issue simultaneously. It prioritized the barriers most closely tied to the allegations and to revenue-generating customer journeys.
The first remediation sprint focused on navigation, filters, product selectors, form labels, validation, focus management, and checkout controls.
Template-level issues were especially important. A single inaccessible component could appear across hundreds or thousands of pages, so fixing the underlying component often produced a larger improvement than manually editing individual URLs.
After developers completed a fix, the accessibility team retested it. Tickets were not considered complete merely because the code had changed.
Step 4: giving counsel a cleaner factual record
Technical evidence, remediation status, and retesting results can give counsel a clearer factual record.The purpose of the audit was not to tell the attorneys how to litigate or settle the case. That is legal work.
The purpose was to give counsel better technical facts.
By the time settlement discussions became more serious, the company could document:
- which alleged barriers were reproduced;
- which allegations were not reproduced during testing;
- which issues had already been fixed;
- which changes had been independently retested;
- which remaining items were in active remediation;
- how key user journeys performed after fixes; and
- what ongoing accessibility process the company intended to maintain.
This is materially different from entering negotiations without having investigated the website.
Did the audit reduce the settlement amount?
In this fictionalized scenario, the retailer ultimately resolved the matter for a substantially lower amount than the opening settlement position discussed early in the dispute.
It would be misleading to say that the accessibility audit alone “caused” that reduction. Settlement amounts can be affected by the jurisdiction, claims, plaintiff, counsel, attorney’s fees, procedural posture, insurance, litigation risk, evidentiary issues, business priorities, and many other factors.
What the technical work did was strengthen the company’s factual position.
Counsel was no longer negotiating around an unknown website condition. The company had investigated the allegations, fixed confirmed barriers, verified substantial remediation, documented its work, and demonstrated actual user testing.
That kind of evidence can support more informed settlement discussions and may improve negotiating leverage in some matters. It does not guarantee a lower settlement, dismissal, or any particular legal result.
Why remediation can matter in a Florida federal case
Florida federal courts sit within the Eleventh Circuit, and businesses should not assume that simply changing a website automatically ends an ADA case.
For example, in Kennedy v. Omegagas & Oil, LLC, the Eleventh Circuit concluded that evidence of continuing website-related barriers prevented dismissal on mootness grounds at that stage. The lesson is straightforward: remediation needs to be real and complete enough to address the barriers at issue; merely claiming that a site was updated is not the same thing as proving the problem is gone.
The U.S. Department of Justice also states that Title III applies to businesses open to the public and identifies retail stores among covered public accommodations. DOJ’s Guidance on Web Accessibility and the ADA explains the Department’s position that inaccessible web content can create barriers to the goods and services offered by businesses open to the public.
For an actual lawsuit, businesses should rely on qualified counsel for legal strategy. Accessibility consultants should stay focused on testing, documentation, remediation, and verification.
What the retailer did after the immediate dispute
One of the biggest mistakes a company can make is treating accessibility as finished when a settlement is signed or a remediation sprint ends.
The retail chain moved from an emergency project into a maintenance process.
That process included recurring automated scans, manual review of major releases, accessibility checks for new shared components, periodic screen-reader and keyboard testing, and an annual deeper review of high-value customer journeys.
This reduced the chance that a new promotion, plugin, checkout update, theme change, or third-party tool would silently reintroduce the same categories of barriers.
The commercial lesson for other retailers
Retail websites are unusually complex. They combine design systems, search, product catalogs, filters, dynamic content, accounts, promotions, payment providers, customer-support tools, and third-party scripts.
That complexity means a retail accessibility program should focus on complete user journeys rather than a few isolated pages.
A useful audit asks:
- Can a customer independently find a product?
- Can they understand the product information?
- Can they operate product options?
- Can they add and remove items from the cart?
- Can they identify and correct checkout errors?
- Can they complete the transaction with a keyboard and assistive technology?
If the answer is no, the business has both an accessibility problem and a broken customer journey.
What businesses should do after receiving a website accessibility claim
- Contact qualified legal counsel. Do not rely on an accessibility vendor for legal advice.
- Preserve the relevant website state. Coordinate with counsel before major emergency changes.
- Audit the allegations and related user journeys. Do not rely on a homepage scan.
- Use real manual testing. Include keyboard and screen-reader review.
- Document every confirmed barrier. Give developers reproduction steps and remediation guidance.
- Fix high-impact issues quickly. Prioritize barriers tied to the allegations and important transactions.
- Retest the fixes. Verification matters.
- Consider real-user testing. A recorded session can make barriers and improvements much easier to understand.
- Give technical evidence to counsel. Counsel decides how to use it.
- Create an ongoing monitoring process. Avoid returning to the same problem after the immediate case ends.
How ADA Access Group supports businesses and counsel
ADA Access Group is not a law firm and does not provide legal advice. Our role is the technical side of digital accessibility.
We can support a business and its legal counsel with targeted manual accessibility audits, screen-reader and keyboard testing, developer-ready reports, remediation guidance, retesting, real-user testing, and ongoing monitoring.
If your organization has received a website accessibility demand letter or lawsuit, request an urgent Website Accessibility Review. If you have the complaint or demand letter, the technical review can be scoped around the specific allegations and the customer journeys that matter most.
Sources and legal context
- U.S. Department of Justice — Guidance on Web Accessibility and the ADA
- U.S. Court of Appeals for the Eleventh Circuit — Kennedy v. Omegagas & Oil, LLC
- U.S. Department of Justice — ADA Title III Regulations
This fictionalized composite case study is for educational and marketing purposes. It does not describe an actual ADA Access Group client, lawsuit, plaintiff, settlement, or court outcome. Nothing in this article is legal advice or a guarantee that an accessibility audit, remediation project, or real-user test will reduce a settlement or produce any particular legal result.
Related reading
- What to Do If You Receive an ADA Website Accessibility Lawsuit or Demand Letter
- What Does a Website Accessibility Audit Include?
- Accessibility Widgets Don’t Prevent ADA Website Lawsuits: 2026 Data
- Florida ADA Website Accessibility Update: What Recent 2026 Filings Signal
- Ana Luisa Website Accessibility Lawsuit: What the 2026 Filing Signals for E-Commerce