A Second Demand Letter After You Fixed the First: Why It Happens and What It Means
Fixing the barriers in a first letter does not end the story if new pages, apps, or regressions appeared. How second letters happen and how a store should respond.
Few business moments feel as unfair as a second accessibility demand letter landing after the first one was settled and its fixes were made. Owners assume someone made a mistake, theirs, their developer's, or the sender's. Sometimes that is true. More often, the site genuinely changed, and the second letter is about the site as it exists now, not the site that was fixed then.
Understanding why second letters happen turns a demoralizing surprise into a manageable process. The response playbook is similar to the first time, with one advantage: a store that documented its first remediation starts the second round with evidence most businesses never have.
Sites change, and change reintroduces barriers
Since the first settlement, the store probably added products, pages, a popup tool, a reviews app, maybe a theme update. Each addition can ship a barrier the original remediation never covered, because it did not exist yet. Plaintiffs and their tools scan live sites, so a clean audit from eighteen months ago says little about the pages a second letter cites today.
Read what the second letter actually cites
Compare the cited barriers with the first letter and your fix log before concluding anything. Some citations will be genuinely new elements. Some may be items your records show were fixed and tested, which is where dated evidence changes the conversation. Occasionally a letter cites barriers on pages belonging to a former theme or a third party portal, and sorting real from mistaken citations is the first useful work, done with counsel.
Your remediation log is now the main asset
A store that logged fixes with dates, kept scan results, and maintained its accessibility statement can show a pattern: barriers found, barriers fixed, monitoring in place. That pattern does not make a valid new barrier disappear, but it strongly affects how a claim is negotiated and how the business is judged. A store that fixed and forgot has to reconstruct that story from email scraps, if it can.
Preventing the third letter is a system, not a project
The durable lesson of a second letter is that remediation is maintenance. Ongoing scanning of core pages, an accessibility check when apps are installed or the theme updates, and a statement contact route that is actually monitored catch most barriers while they are still cheap. Stores that adopt that rhythm rarely see a third letter about the same classes of problem.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: ADA Accessibility Due Diligence When Buying an Existing Shopify Store, Accessibility Clauses in Vendor and Agency Contracts: Shifting Risk Before It Lands, and Preparing an Accessibility Evidence Pack for Insurance and Counsel.
Frequently asked questions
Does settling a first demand letter protect a store from a second?
No. A settlement usually covers the claims and site state at that time, sometimes with specific terms. New barriers, new pages, or commitments that were not kept can support a new claim. The settlement is a chapter, not immunity.
What should a store do first when a second letter arrives?
Preserve the letter, do not ignore its deadlines, involve counsel, and compare its citations against your remediation log and current scans. Start fixing any clear new barriers promptly, as remediation helps in every scenario.
Can a second letter be mistaken?
Parts of one can be. Automated scans produce false positives, and letters sometimes cite fixed issues or third party pages. That is a reason to verify each citation carefully with evidence, not a reason to dismiss the letter without checking.
How do stores stop the cycle of letters?
By treating accessibility as maintenance: routine scans, checks on app installs and theme updates, a monitored contact route, and dated records. Most repeat letters trace back to change that nobody rechecked.