Lorixen.
EN

Got an ADA Website Demand Letter? A Calm First-Week Plan

Short answer: Receiving a demand letter about your website's accessibility is stressful, but the first week has a clear order. Speak to a qualified attorney before you reply, save a copy of the site as it stands, arrange an independent accessibility audit and start fixing the most serious barriers while keeping a dated record of every change. Do not sign anything or agree to a deadline until counsel has reviewed it. Avoid quick fixes that promise full compliance, because a rushed overlay or a claim you cannot support can make the position harder. The aim is to show a serious, documented plan.

Day one: stop, read and call a lawyer

The letter will usually ask you to respond within a short period and may describe specific pages and features. Do not ignore it. Do not reply with an admission or a promise either. Forward the letter to a lawyer who handles accessibility or commercial disputes, and ask them how to respond and by when.

A bakery in Chicago, Second Street Bakery in this example, gets a letter about its online ordering page, which a screen reader user could not complete. The owner's first instinct is to fix the page that day and reply with a short apology. Her lawyer asks her to keep the page as it is for the moment, capture evidence of its current state and hold any reply until the review is complete. That pause protects the business.

Day two: preserve the current state

Before you change anything, record how the site looks and behaves now. Take dated screenshots of the affected pages, save copies of the page source if your developer can do it, and export the hosting logs and any analytics for the period mentioned. If you use a website builder, export the site or take a full backup. These records show what existed when the letter arrived and help your lawyer assess the claim.

Keep the list of people who edit the site. Ask your developer or agency to confirm in writing what they changed in the last few months, because a recent redesign can affect the timeline.

Day three: get an independent audit

An audit should test the site against the Web Content Accessibility Guidelines, which the W3C publishes. The current standard most often referenced is WCAG 2.1 or 2.2 at level AA. An audit combines automated checks with manual testing using a keyboard and a screen reader. Ask the auditor to produce a list of issues, each with the page, the criterion, the effect on a user and a suggested fix. Ask whether the report shows which pages were fully tested and which were sampled. An audit that tests five representative pages from a site of two hundred is a different document from one that tests every template, and your lawyer will want to know which one you have. Ask also whether the auditor will check the pages that take payment, sign-in and booking, because those are the pages a claimant is most likely to describe in a letter. Keep the auditor's scope letter with the report, and file both with your other records from the first week.

Ask whether the auditor will work under your lawyer's direction. Counsel often prefers that certain reports are prepared for legal advice, and that arrangement should be agreed before the work starts.

Days four and five: fix the top issues

Start with barriers that stop someone completing a task. Examples include a checkout button that cannot be reached by keyboard, a form without labels, a menu that traps focus, or a video without captions. Fix these first, because they affect the most people and are the issues a claimant is most likely to describe.

Record each fix with the date, the page, the change made and the person who did it. Retest after each fix, and keep the retest results. A simple change log is more persuasive than a general statement that the site was improved.

Days six and seven: plan, document and communicate

Write a plan that lists the remaining issues, the owner of each fix and a realistic date. Share the plan with your lawyer before sending it to anyone else. If counsel approves a response to the letter, keep it factual, describe the steps taken and the timetable, and avoid admissions about fault.

Also check your public accessibility statement, if you have one. It should describe the standard you aim for, the known gaps and how to report a problem. An inaccurate statement can create its own difficulty.

Be cautious with overlays and promises

Some vendors sell overlay products that claim to make a site compliant with a single script. Accessibility regulators and advocates have criticised these claims, and overlays do not fix the underlying code. Do not promise full compliance in writing unless an independent audit confirms it. A promise that proves false can damage your position more than the original barrier.

What to keep for the long run

Keep the audit report, the change log, the retest results, the correspondence and the final version of the plan. Store them somewhere safe, and note the review date. When the site changes in a major way, such as a new checkout or a new booking system, add the new components to the testing list.

Build accessibility into your routine. Test new pages with a keyboard before publishing, and include an accessibility check in any contract with a developer.

FAQ

Do I have to respond to the letter myself?

Your lawyer can respond on your behalf. Speak to counsel before replying to the sender, and do not make statements about your site until you have advice.

Can I fix the site quickly and close the matter?

Some issues can be fixed quickly, but the claim may still need a formal response. Fixing the site and documenting the steps is a sensible part of the plan, not a substitute for legal advice.

How long does a typical response take?

It varies with the number of pages, the complexity of the site and the speed of the audit. Ask your advisers for a realistic timeline once they have read the letter.

An audit scope is easier to agree once someone has read the letter with you. If you need that help, start with our enquiry form.

Sources

WhatsAppBook a call