Summary. This toolkit collects the working papers a business and its counsel need to defend a website accessibility demand or Title III lawsuit and to keep the next one from succeeding. It includes four demand response letters for different postures, a three-party privileged audit engagement letter, a remediation plan and log, a litigation hold notice, an insurer tender letter, an accessibility statement, settlement agreement key terms, vendor contract clauses, an exposure and strategy memo outline, and a mootness declaration outline. Each template states its purpose, owner, and timing, and is followed by drafting commentary tied to the governing authority. A running example follows a regional outdoor retailer through a demand from a Florida firm. An index table at the top maps each template to the step it supports.


Website accessibility matters are won or lost on paperwork written in the first month. The response letter sets the tone and the number. The engagement letter decides whether the audit stays privileged. The remediation log decides whether a mootness argument is available. The settlement terms decide whether the next plaintiff finds the same defects. This toolkit is that paperwork.

The step-by-step sequence these templates support is in Responding to a Website Accessibility Demand Letter or Lawsuit: A Practical Guide. The doctrine and the code behind them are in Website Accessibility Lawsuits: What the ADA Requires, What Breaks in the Code, and What to Do When the Letter Arrives. The testing protocol that feeds Templates 6 and 13 is the Website Accessibility Self-Audit Checklist: A Practical Checklist.

How to use this toolkit

Each template states its Purpose, its Owner, and When to use it, then gives the template and drafting commentary. Bracketed text in capitals is to be filled in. Use one reference system across every paper: F- for audit findings (F-01, F-02), R- for remediation tickets, and V- for verification records, so that the log, the declaration, and the settlement exhibit can all point to "F-03 / R-03 / V-03."

Running example. Juniper Lane Outfitters, LLC sells outdoor apparel through five stores in Georgia and north Florida and an online store that produces 40 percent of revenue. On September 9, it receives an email demand from a Miami firm on behalf of a blind Miami-Dade resident. The letter alleges that on August 22 the plaintiff could not use Juniper Lane's "Shop" menu, could not tell whether items were added to his cart, and could not complete checkout because "form fields lack labels," citing WCAG 2.1 AA generally. It demands $15,000 and a remediation commitment within 21 days. Juniper Lane's general counsel engages outside counsel the next day. The Eleventh Circuit has no binding website precedent after Gil v. Winn-Dixie Stores, Inc., 993 F.3d 1266 (11th Cir. 2021), was vacated as moot, 21 F.4th 775 (11th Cir. 2021), but Juniper Lane's stores and in-store pickup supply the nexus that Rendon v. Valleycrest Productions, Ltd., 294 F.3d 1279 (11th Cir. 2002), and the unpublished Haynes v. Dunkin' Donuts LLC, 741 F. App'x 752 (11th Cir. 2018), treat as sufficient.

Template Owner Stage
1. Demand response: remediation and resolution Defense counsel Weeks 2 to 3
2. Demand response: factual rebuttal Defense counsel Weeks 1 to 3
3. Demand response: legal rebuttal Defense counsel Weeks 1 to 3
4. Demand response: information request Defense counsel Week 1
5. Privileged audit engagement letter (three-party) Defense counsel, client, consultant Week 1
6. Remediation plan and log Client's digital lead, supervised by counsel Weeks 2 onward
7. Litigation hold notice Defense counsel or in-house counsel Days 1 to 2
8. Insurer tender letter Client or coverage counsel Days 1 to 7
9. Accessibility statement Client, reviewed by counsel After transaction-path fixes
10. Settlement agreement key terms Defense counsel At resolution
11. Vendor accessibility contract clauses Client's procurement, reviewed by counsel Renewals and new purchases
12. Exposure and strategy memo outline Defense counsel (privileged) Weeks 1 to 2
13. Mootness declaration outline Defense counsel, with the remediation lead and an independent tester After verification

Template 1: Demand response, remediation and resolution posture

Purpose: acknowledge a largely accurate claim, show competence and seriousness, and open settlement on the business's terms. Owner: defense counsel. When to use: the audit confirms the alleged barriers are real, the business intends to remediate, and resolution is cheaper than a fight.

[FIRM LETTERHEAD]

[DATE]

VIA EMAIL ([EMAIL ADDRESS])

[PLAINTIFF'S COUNSEL NAME]
[FIRM]
[ADDRESS]

FOR SETTLEMENT PURPOSES ONLY. SUBJECT TO FED. R. EVID. 408 AND [STATE ANALOGUE].

Re: [CLIENT LEGAL NAME]; your letter dated [DATE] on behalf of [PLAINTIFF NAME]

Dear [COUNSEL]:

We represent [CLIENT] in connection with your letter of [DATE]. Please direct
all further communications on this matter to us.

[CLIENT] is committed to making its website usable by customers with
disabilities. On receiving your letter, it retained this firm and, through us,
an independent digital accessibility consultant. [CLIENT] has begun a
remediation program directed at WCAG 2.1 Level AA, beginning with the
navigation, cart, and checkout functions your letter describes, and expects to
complete that phase by [DATE].

[CLIENT] denies that it has violated Title III of the Americans with
Disabilities Act or any other law, and nothing in this letter is an admission.
In the interest of resolving this matter without litigation, [CLIENT] proposes:

  1. A payment of $[AMOUNT], inclusive of all attorney's fees and costs;
  2. A written commitment to substantially conform the website at
     [DOMAIN] to WCAG 2.1 Level AA by [DATE], with a [60]-day notice-and-cure
     process for any alleged nonconformance;
  3. A general release of all claims relating to the accessibility of
     [CLIENT]'s websites and mobile applications through the effective date,
     including claims under [STATE LAW], and a covenant not to sue during the
     remediation period; and
  4. No admission of liability, and mutual confidentiality of the payment
     amount.

This offer remains open until [DATE]. We are available to discuss it at your
convenience.

Sincerely,

[NAME]
[TITLE]

Drafting commentary. The letter does four things: it moves communications to counsel, it shows the business has a real program (which undercuts the plaintiff's leverage), it denies liability, and it frames the deal around remediation rather than the number. Rule 408 protects offers and statements made in compromise negotiations from being used to prove liability, Fed. R. Evid. 408, but it does not make volunteered facts undiscoverable; describe the program in general terms and never attach the audit. Title III gives a private plaintiff only injunctive relief and fees, 42 U.S.C. § 12188(a) and § 12205, so the number is functionally a fee payment unless state damages are in play. For Juniper Lane, the audit (Template 5) confirmed a hover-only menu, a silent "Add to Cart" confirmation, and placeholder-only checkout labels, so counsel used this posture and offered $5,500. The negotiation strategy behind the number is in the Settlement Negotiation Toolkit: Case Valuation Worksheets, Concession Plans, and Offer Letters.

Template 2: Demand response, factual rebuttal

Purpose: decline payment where the alleged barriers do not exist or did not exist on the date alleged. Owner: defense counsel. When to use: testing (preferably with preserved versions of the site) shows the allegations are wrong.

FOR SETTLEMENT PURPOSES ONLY. SUBJECT TO FED. R. EVID. 408.

Re: [CLIENT]; your letter dated [DATE]

Dear [COUNSEL]:

We represent [CLIENT]. We have reviewed your letter with [CLIENT]'s team and an
independent accessibility tester.

Your letter alleges that on [DATE] your client could not [ALLEGED BARRIER 1]
and [ALLEGED BARRIER 2]. We tested those functions on [DATES] using [SCREEN
READER AND VERSION] with [BROWSER AND VERSION], and using the keyboard alone,
on the current site and on the version of the site deployed on [DATE OF
ALLEGED VISIT], which [CLIENT] has preserved. In each case the function
operated as follows: [SHORT, SPECIFIC DESCRIPTION, e.g., "the 'Shop' button
receives keyboard focus, opens on Enter or Space, announces 'Shop, button,
collapsed' and 'expanded,' and its links are reachable in order"].

If your client encountered a different barrier, please identify the page URL,
the date and approximate time, the assistive technology and browser used, and
what happened, and we will review it promptly. [CLIENT] takes accessibility
seriously and maintains a feedback channel at [CONTACT].

On the present record, [CLIENT] declines to make any payment.

Sincerely,
[NAME]

Drafting commentary. Be specific and modest. Describe how the function actually works, with the tools and versions used, and invite specifics. Do not overclaim ("the site is fully compliant"); the next plaintiff's tester will find something somewhere. This letter is only as strong as your preservation: if you cannot show what the site looked like on the alleged visit date, you can rebut only the present state. That is why Template 7 goes out first and why loss of the evidence carries consequences under Fed. R. Civ. P. 37(e). A complaint built on barriers the plaintiff never encountered is also vulnerable on the pleadings; the Ninth Circuit requires the plaintiff to identify the barrier actually encountered, Whitaker v. Tesla Motors, Inc., 985 F.3d 1173 (9th Cir. 2021).

Template 3: Demand response, legal rebuttal

Purpose: decline payment on a dispositive legal ground, usually that an online-only business is not a place of public accommodation in the relevant circuit, or that the plaintiff plainly lacks standing. Owner: defense counsel. When to use: the defense is strong under controlling law and the business is prepared to file a motion if sued.

FOR SETTLEMENT PURPOSES ONLY. SUBJECT TO FED. R. EVID. 408.

Re: [CLIENT]; your letter dated [DATE]

Dear [COUNSEL]:

We represent [CLIENT], which sells exclusively through its website and has no
physical location open to the public.

[OPTION A: PLACE OF PUBLIC ACCOMMODATION]
Title III applies to discrimination in "any place of public accommodation,"
42 U.S.C. § 12182(a). In [CIRCUIT], a website is not itself a place of public
accommodation and is covered only where it has a nexus to a physical place.
See [CONTROLLING AUTHORITY]. [CLIENT] has none. [IF CALIFORNIA STATE LAW IS
CLAIMED: Without an ADA violation, an Unruh Act claim requires intentional
discrimination, which your letter does not allege. See Martinez v. Cot'n Wash,
Inc., 81 Cal. App. 5th 1026 (2022).]

[OPTION B: STANDING]
Your client resides in [LOCATION], has never purchased from [CLIENT], and has
filed [NUMBER] substantially similar claims in [PERIOD]. A plaintiff seeking
injunctive relief must plausibly allege a real and immediate threat of future
injury. See Calcano v. Swarovski N. Am. Ltd., 36 F.4th 68 (2d Cir. 2022).

[CLIENT] nonetheless values all of its customers and reviews accessibility
feedback received at [CONTACT]. It declines to make any payment, and if a
complaint is filed it intends to move to dismiss.

Sincerely,
[NAME]

Drafting commentary. Use this letter only when the law is genuinely on your side; a bluff that is called costs more than a settlement. The controlling authority depends on the circuit: Ford v. Schering-Plough Corp., 145 F.3d 601 (3d Cir. 1998); Parker v. Metropolitan Life Insurance Co., 121 F.3d 1006 (6th Cir. 1997) (en banc); Weyer v. Twentieth Century Fox Film Corp., 198 F.3d 1104 (9th Cir. 2000); and, in New York, district decisions such as Winegard v. Newsday LLC, 556 F. Supp. 3d 173 (E.D.N.Y. 2021), and Mejia v. High Brew Coffee, Inc., No. 1:22-cv-03667 (S.D.N.Y. Sept. 30, 2024), which must be weighed against contrary decisions such as Andrews v. Blick Art Materials, LLC, 268 F. Supp. 3d 381 (E.D.N.Y. 2017). In California state court, Martinez v. Cot'n Wash, Inc., 81 Cal. App. 5th 1026 (2022), held both that an online-only retail website is not a Title III place of public accommodation and that knowledge plus a failure to fix does not show Unruh intent. The standing option should be used sparingly and never against a plaintiff with a plausible reason to shop with you. Juniper Lane, with stores, could not use Option A; this template was not used in the running example.

Template 4: Demand response, information request

Purpose: buy time and information where the letter is too vague to evaluate. Owner: defense counsel. When to use: in the first week, before the audit is complete, or when the letter identifies no pages, dates, or barriers.

FOR SETTLEMENT PURPOSES ONLY. SUBJECT TO FED. R. EVID. 408.

Re: [CLIENT]; your letter dated [DATE]

Dear [COUNSEL]:

We represent [CLIENT] and have received your letter. [CLIENT] takes the
accessibility of its website seriously and is reviewing your client's concerns.

To allow a meaningful review, please provide:
  1. The URL of each page on which your client encountered a barrier;
  2. The date and approximate time of each visit;
  3. The assistive technology (with version), browser, and device used;
  4. A description of what your client was trying to do and what happened;
  5. Any recording, screenshot, or audit report on which the letter relies.

We will respond substantively within [14] days of receiving this information.
Please treat this letter as a request to extend the response date in your
letter to [DATE].

Sincerely,
[NAME]

Drafting commentary. This is the least confrontational opening and often the most revealing: a firm that cannot answer these questions did not test the site. Pair it with an actual review; do not use it as a stall and then go silent. Under Fed. R. Civ. P. 11(b), any complaint later filed certifies a reasonable prior inquiry, and a firm that could not identify a single page in response to this letter will have trouble meeting that standard.

Template 5: Privileged audit engagement letter (three-party)

Purpose: structure the accessibility audit so that the consultant's analysis has the best available chance of protection as work product and, where it supports legal advice, attorney-client privilege. Owner: outside counsel, countersigned by the client and the consultant. When to use: as soon as a claim is reasonably anticipated and before any audit work begins.

[OUTSIDE COUNSEL LETTERHEAD]
PRIVILEGED AND CONFIDENTIAL
ATTORNEY WORK PRODUCT PREPARED IN ANTICIPATION OF LITIGATION

[DATE]

[CONSULTANT NAME]
[ADDRESS]

Re: Engagement to assist counsel in connection with [CLIENT] / [MATTER]

1. Engagement. [FIRM] ("Counsel") represents [CLIENT] ("Client") in connection
   with a claim asserted by [CLAIMANT] on [DATE] concerning the accessibility of
   Client's website and related digital properties, and in anticipation of
   litigation arising from that claim and similar claims. Counsel retains
   [CONSULTANT] ("Consultant") to assist Counsel in understanding technical
   matters so that Counsel can provide legal advice to Client.

2. Direction and reporting. Consultant will work at Counsel's direction and will
   report only to Counsel. Consultant will not deliver findings, drafts, or
   reports to Client personnel or third parties except as Counsel directs in
   writing.

3. Scope. [SPECIFIC SCOPE, e.g., "testing of the functions identified in the
   claim, the purchase path from product page through order confirmation, and
   the [NUMBER] page templates listed in Schedule A, against WCAG 2.1 Level AA,
   using manual keyboard and screen reader testing and automated tools"].

4. Deliverable. Consultant's deliverable is a confidential memorandum to Counsel
   describing findings and recommended remediation priorities. It is not a
   certification of conformance or compliance and will not be described as one.

5. Confidentiality. All information received from Counsel or Client, all work
   papers, and all communications are confidential. Consultant will label them
   "Privileged and Confidential, Prepared at the Direction of Counsel." Consultant
   will notify Counsel promptly of any subpoena or request for them and will
   not produce them without Counsel's consent or a court order.

6. Separation from remediation. Remediation tickets for Client's developers will
   be prepared by Counsel or Client from Counsel's instructions, not by
   forwarding Consultant's memorandum.

7. Fees. Client will pay Consultant's invoices, addressed to Counsel, at [RATE OR
   FIXED FEE]. Payment by Client does not alter the reporting structure.

8. Conflicts and independence. Consultant confirms it has no relationship with
   [CLAIMANT] or its counsel and has not sold Client any accessibility product.

9. Return of materials. At the end of the engagement or on request, Consultant
   will return or destroy confidential materials, except as Counsel directs
   for litigation purposes.

[SIGNATURE BLOCKS: COUNSEL; CLIENT (ACKNOWLEDGED AND AGREED); CONSULTANT]

Schedule A: Pages and templates in scope

Drafting commentary. The work-product doctrine, which grew out of Hickman v. Taylor, 329 U.S. 495 (1947) and is codified in Fed. R. Civ. P. 26(b)(3), protects documents prepared in anticipation of litigation by or for a party or its representative, including a consultant. The attorney-client privilege can extend to a non-lawyer whose role is to help counsel understand technical information, under United States v. Kovel, 296 F.2d 918 (2d Cir. 1961), and the corporate privilege principles of Upjohn Co. v. United States, 449 U.S. 383 (1981). Courts ask whether the document would have been created in substantially similar form for ordinary business reasons. Paragraphs 2, 4, and 6 are what answer that question: a memo to counsel, not a compliance report to marketing, and a separate ticket stream for developers. If you will need to prove the fixes for mootness, plan for a second, non-privileged verification (Template 13) so you never have to put this memo at issue. If privileged material is produced by mistake, Fed. R. Evid. 502(b) limits waiver where reasonable precautions were taken. For the doctrine in depth, see Attorney-Client Privilege and Work Product for Businesses: Upjohn, In-House Counsel, and the Common Interest.

In the running example, Juniper Lane's consultant tested the homepage, navigation, three category templates, the product template, the cart drawer, and the four checkout steps, and delivered its memo to counsel on day 12: F-01 hover-only menu (2.1.1); F-02 "Add to Cart" confirmation not announced (4.1.3); F-03 placeholder-only labels in checkout (1.3.1, 3.3.2); F-04 card errors shown only in red (3.3.1, 1.4.1); F-05 a promotional pop-up that traps focus (2.1.2); F-06 low-contrast sale badges (1.4.3).

Template 6: Remediation plan and log

Purpose: plan the fixes in legal-priority order and record each one in a form that can support a mootness argument and a good-faith showing. Owner: the client's digital or e-commerce lead, supervised by counsel. When to use: from the moment counsel translates the audit findings into tickets, and permanently afterward.

Part A: Plan (priority order)

Priority Rule Example (Juniper Lane)
P1 Barriers alleged in the claim F-01 menu; F-02 cart announcement; F-03 checkout labels
P2 Other transaction-path barriers F-04 card error messages; F-05 pop-up focus trap
P3 Level A failures elsewhere on high-traffic templates Category filter controls
P4 Level AA failures on high-traffic templates F-06 sale badge contrast
P5 Everything else, scheduled Footer link contrast; blog image alt text

Part B: Log (one row per fix)

Ref WCAG SC and level Page or template Defect (plain English) Fix Owner Ticket / commit Deployed Verified by, how, date Status
R-01 / F-01 2.1.1 (A) Global header "Shop" menu opens on hover only Rebuilt as disclosure button with aria-expanded; Escape closes [DEV] [TICKET] / [HASH] [DATE] V-01: [TESTER], NVDA [VERSION] + Firefox, keyboard, [DATE] Closed
R-02 / F-02 4.1.3 (AA) Product template Add-to-cart result not announced Added role="status" region with item and count [DEV] [TICKET] / [HASH] [DATE] V-02: [TESTER], VoiceOver + Safari, [DATE] Closed
R-03 / F-03 1.3.1, 3.3.2 (A) Checkout steps 1 to 3 Placeholder-only labels Visible label for on all fields; autocomplete added [DEV] [TICKET] / [HASH] [DATE] V-03 Closed
R-04 / F-04 3.3.1, 1.4.1 (A) Checkout payment Errors shown in red only Error summary with role="alert"; aria-invalid and aria-describedby per field [DEV] [TICKET] / [HASH] [DATE] V-04 Closed
R-05 / F-05 2.1.2 (A) Global Promo pop-up traps focus Replaced with native dialog; close button; focus returns to trigger [DEV] [TICKET] / [HASH] [DATE] V-05 Closed
R-06 / F-06 1.4.3 (AA) Category, product Sale badge contrast 2.8:1 Darkened badge to 5.1:1 [DESIGN] [TICKET] / [HASH] [DATE] V-06 Closed

Part C: Program items

Item Owner Date adopted Evidence
Written accessibility policy [NAME] [DATE] [LINK TO POLICY]
Accessibility statement published (Template 9) [NAME] [DATE] [URL]
Automated checks in deployment pipeline [NAME] [DATE] [CONFIG FILE / BUILD LOG]
Content team training [NAME] [DATE] [ATTENDANCE RECORD]
Vendor clauses added (Template 11) [NAME] [DATE] [CONTRACTS]
Next manual retest scheduled [NAME] [DATE] [CALENDAR ENTRY]

Drafting commentary. This log is a business record, and you should assume you will produce it. Keep it factual: what was wrong, what was done, when, and how it was checked. Keep counsel's evaluation of exposure out of it (that belongs in Template 12). The log is the evidence a court will look for under the voluntary-cessation doctrine of Friends of the Earth, Inc. v. Laidlaw Environmental Services (TOC), Inc., 528 U.S. 167 (2000), and Already, LLC v. Nike, Inc., 568 U.S. 85 (2013): not just that the defects were fixed, but that the policy, the pipeline checks, and the training make recurrence implausible (Part C). A remediation plan without completed rows proves little; in Haynes v. Hooters of America, LLC, 893 F.3d 781 (11th Cir. 2018), a remediation commitment made to an earlier plaintiff did not moot a later claim because the record did not show the work had been done. For the full remediation program, see the Website Accessibility Remediation Checklist: A Practical Checklist.

Template 7: Litigation hold notice

Purpose: suspend deletion and preserve the evidence of what the website looked like and how it changed. Owner: in-house or outside counsel. When to use: within one or two days of receiving a demand or complaint.

PRIVILEGED AND CONFIDENTIAL: ATTORNEY-CLIENT COMMUNICATION
LEGAL HOLD NOTICE: DO NOT DELETE

To:   [E-COMMERCE LEAD]; [MARKETING DIRECTOR]; [IT LEAD]; [CMS ADMINISTRATOR];
      [AGENCY CONTACT]; [CUSTOMER SERVICE LEAD]
From: [COUNSEL]
Date: [DATE]
Re:   Preservation of website and accessibility records: [MATTER NAME]

[CLIENT] has received a legal claim concerning the accessibility of its website
and may be involved in litigation. You are required to preserve the materials
below, in whatever form they exist, effective immediately and until you are
told in writing that this notice has been lifted. Suspend any automatic
deletion that would affect them.

Materials to preserve (for [START DATE, at least six months before the alleged
visit] to the present):
  - Website theme and template versions, deployment and release logs, and
    content management system revision history;
  - Source code repositories, branches, commits, pull requests, and issue or
    ticket records, especially any mentioning accessibility, ADA, WCAG, screen
    readers, keyboard, alt text, or contrast;
  - Analytics and server logs for [PAGES AT ISSUE], including any records for
    [DATE OF ALLEGED VISIT];
  - Customer service tickets, chats, call notes, and emails mentioning
    accessibility or inability to complete a purchase;
  - Prior accessibility audits, scans, VPATs, and communications with
    accessibility vendors or overlay providers;
  - Contracts and communications with the e-commerce platform and with
    third-party widget, payment, review, and chat vendors.

Do not alter or "clean up" any of these materials. Do not begin accessibility
changes to the website until counsel confirms the current state has been
captured, unless a defect is preventing customers from completing purchases,
in which case notify [COUNSEL] before and after the change.

Outside agencies and vendors: please confirm in writing within three business
days that you have received this notice and taken steps to comply, and tell us
how long your systems retain prior versions.

Do not discuss this matter with anyone outside [CLIENT] other than counsel.
Questions: [COUNSEL CONTACT].

Acknowledgment: I have read this notice and will comply.
Name: ______________  Signature: ______________  Date: ________

Drafting commentary. The duty to preserve attaches when litigation is reasonably anticipated; a demand letter usually qualifies. Loss of electronically stored information that should have been preserved can lead to curative measures, or, on a finding of intent to deprive, adverse-inference instructions or dismissal, under Fed. R. Civ. P. 37(e). The carve-out for transaction-blocking defects matters: nobody should leave customers unable to buy to protect a litigation position, and a capture of the current state before the change preserves the evidence. Name outside agencies expressly; they often control the only version history. The task list is in the Litigation Hold and Evidence Preservation Checklist: A Practical Checklist.

Template 8: Insurer tender letter

Purpose: give timely notice and request defense and indemnity under every policy that might respond. Owner: the client, its broker, or coverage counsel. When to use: within days of the demand or complaint, and before any settlement.

VIA EMAIL AND CERTIFIED MAIL

[CARRIER CLAIMS DEPARTMENT]
[ADDRESS]

cc: [BROKER]

Re: Notice of claim and tender of defense
    Insured: [NAMED INSURED]
    Policy: [POLICY TYPE AND NUMBER]; Policy period: [DATES]
    Claimant: [CLAIMANT]; Date received: [DATE]

Dear Claims Professional:

[NAMED INSURED] gives notice of a claim and tenders its defense and indemnity
under the policy referenced above and any other policy issued by [CARRIER] or
its affiliates to [NAMED INSURED].

On [DATE], [NAMED INSURED] received [a written demand / a summons and complaint
in CASE CAPTION, COURT, NO.] from [CLAIMANT], alleging that [NAMED INSURED]'s
website is inaccessible to persons with visual disabilities in violation of
Title III of the Americans with Disabilities Act [and STATE LAWS], and seeking
[injunctive relief, damages, and attorney's fees / payment of $AMOUNT]. A copy
is enclosed.

[NAMED INSURED] requests that [CARRIER]:
  1. Acknowledge receipt and assign a claim number;
  2. Confirm whether it will defend, and whether it requires the use of panel
     counsel;
  3. Consent to [NAMED INSURED]'s retention of [FIRM] and of an accessibility
     consultant through counsel as a reasonable defense cost; and
  4. Advise of any information it needs to evaluate coverage.

[If a response deadline exists:] The response to the [demand / complaint] is
due on [DATE]. Please respond before [DATE].

[NAMED INSURED] reserves all rights under the policy and applicable law.
Nothing in this letter waives any right or privilege.

Sincerely,
[NAME, TITLE]
Enclosures: [DEMAND OR COMPLAINT]

Drafting commentary. Tender to every policy that might respond: general liability (rarely, because the claim is not bodily injury, property damage, or an enumerated personal and advertising injury), employment practices liability with third-party discrimination coverage (the most likely), cyber, and any technology errors and omissions or media policy. Many policies define "claim" to include a written demand for non-monetary relief, so the notice clock may already be running. Do not settle without the carrier's consent; most policies exclude voluntary payments. For coverage analysis, see Business Insurance and Coverage Disputes: CGL, E&O, Cyber, and D&O; for tender practice generally, see the Insurance Coverage Toolkit: Placing, Tendering, and Litigating Claims. Juniper Lane tendered to its EPL carrier, whose third-party discrimination endorsement responded subject to a $10,000 retention.

Template 9: Accessibility statement

Purpose: tell users how to get help and report barriers, describe the business's commitment honestly, and create a record of good faith. Owner: the client's digital lead, reviewed by counsel. When to use: after the transaction-path fixes are in place, linked from every page footer.

Accessibility at [BUSINESS NAME]

[BUSINESS NAME] wants everyone to be able to shop with us, including customers
who use screen readers, keyboard navigation, magnification, voice control, or
other assistive technology.

Our standard. We aim for our website at [DOMAIN] [and our mobile app] to
conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We
test new features with keyboard and screen reader checks before release,
run automated accessibility checks on every update, and have the site
reviewed by an independent accessibility specialist [at least annually].

Current status. [HONEST STATEMENT, e.g., "We believe the site substantially
conforms to WCAG 2.1 AA. We are aware of the following limitations and are
working on them: [LIST, e.g., some older blog images lack descriptions; our
store-locator map is supplemented by a text list of locations]."]

Third-party content. Some features are provided by other companies, including
[PAYMENT, REVIEWS, CHAT]. We require our vendors to meet accessibility
standards and work with them to fix problems we find.

Need help or found a barrier? Contact us at [EMAIL] or [PHONE], [HOURS]. Tell
us the page and what happened. We will respond within [two business days] and,
if needed, help you complete your order by phone at no extra charge.

This statement was last reviewed on [DATE].

Drafting commentary. Accuracy is everything. A statement that claims full conformance you do not have is evidence against you; a statement that describes a real program, names known limitations, and offers a working contact channel is evidence of good faith and gives users a way to report problems before they become lawsuits. A staffed phone line is a useful backstop, but it is not a substitute for an accessible site: the effective-communication duty in the DOJ's Title III regulations, 28 C.F.R. part 36, turns on whether the alternative actually provides equal access, and the Ninth Circuit in Robles v. Domino's Pizza, LLC, 913 F.3d 898 (9th Cir. 2019), declined to treat a phone number as resolving the claim at the pleading stage. Review the statement at least annually; an outdated date undercuts it.

Template 10: Settlement agreement key terms

Purpose: a term sheet for the website-specific provisions of a settlement agreement. Owner: defense counsel. When to use: when the parties reach agreement in principle, before drafting the full agreement.

Term Recommended position Fallback Note
Parties Plaintiff and [CLIENT] and affiliates Plaintiff and [CLIENT] only The release binds only the plaintiff, not other claimants
Release All claims relating to accessibility of all [CLIENT] websites and apps through the effective date, federal and state Claims relating to [DOMAIN] Include state law expressly (Cal. Civ. Code §§ 51, 52, N.Y. law)
Covenant not to sue Plaintiff will not sue over [DOMAIN] during the remediation period Covenant limited to barriers alleged Prevents repeat claims by the same plaintiff
Standard "Substantially conform to WCAG 2.1 Level AA" WCAG 2.1 AA with WCAG 2.2 AA as a target Avoid "fully accessible" or "100 percent"
Exclusions Third-party content not under [CLIENT]'s control; archived content; user-generated content Commercially reasonable efforts to require vendor conformance Vendor terms in Template 11 make this credible
Timeline [12 to 24] months for full scope; [90 to 180] days for transaction path Shorter for transaction path only Must be achievable
Notice and cure Written notice identifying the page and barrier; [60 to 90] days to cure; meet and confer before any action [30] days The single most valuable protective term
Payment $[AMOUNT], inclusive of all fees and costs; tax allocation stated Separate fee payment to counsel No admission; payment terms confidential
Monitoring Self-certification letter at end of term Independent review report shared once Avoid open-ended monitoring at client's cost
Dismissal Stipulated dismissal with prejudice, Fed. R. Civ. P. 41(a)(1)(A)(ii) Dismissal with court retaining jurisdiction See Kokkonen note below
Consent decree None Only if unavoidable; limited term and scope Makes plaintiff a prevailing party under Buckhannon
Confidentiality Amount confidential; program may be described Full confidentiality Do not bar yourself from citing your program to the next claimant

Drafting commentary. Three doctrines shape these terms. First, a release binds only the releasing party, so the agreement's real protection comes from the remediation it causes (see Haynes v. Hooters, above). Second, a court-ordered consent decree makes the plaintiff a prevailing party entitled to fees, while a private settlement followed by a voluntary dismissal does not, Buckhannon Board & Care Home, Inc. v. West Virginia Department of Health & Human Resources, 532 U.S. 598 (2001); this is why defendants prefer private agreements. Third, a federal court has no continuing jurisdiction to enforce a settlement after dismissal unless the dismissal order retains jurisdiction or incorporates the agreement, Kokkonen v. Guardian Life Insurance Co. of America, 511 U.S. 375 (1994); without that, enforcement is a state contract action. If you use an offer of judgment instead, Fed. R. Civ. P. 68 shifts post-offer costs, and under Marek v. Chesny, 473 U.S. 1 (1985), post-offer fees as well where the fee statute defines fees as costs, a point litigated under the ADA's wording. For full release drafting, see Drafting a Settlement Agreement and Release: A Practical Guide, the Settlement Agreement Checklist: A Practical Checklist, and the Settlement Toolkit: Term Sheets, Releases, Offers of Judgment, and Enforcement. Juniper Lane settled before suit at $8,000 inclusive, with a 12-month WCAG 2.1 AA substantial-conformance commitment, a 60-day cure clause, and no consent decree.

Template 11: Vendor accessibility contract clauses

Purpose: make third-party components that render on the client's site meet the client's accessibility standard, and give the client a remedy when they do not. Owner: procurement, reviewed by counsel. When to use: every new purchase and every renewal of a component that renders content to customers (payment, reviews, chat, scheduling, video, maps, cookie consent, loyalty).

[X]. Accessibility.

[X].1 Standard. Vendor represents and warrants that the [Service / Deliverables],
including all user interfaces presented to Customer's end users, conform and
will throughout the Term conform to WCAG 2.1 Level AA (the "Accessibility
Standard"), [and will conform to WCAG 2.2 Level AA within [12] months after
written request].

[X].2 Documentation. Before the Effective Date and on each anniversary, Vendor
will deliver a current Accessibility Conformance Report based on the VPAT
template, prepared or reviewed by a qualified independent tester, describing
conformance to the Accessibility Standard and any known exceptions.

[X].3 Testing. Vendor will test each release with automated tools and with
manual keyboard and screen reader testing before deployment.

[X].4 Remediation. Vendor will correct any nonconformance (a) that prevents an
end user from completing a transaction within [5] business days, and (b) any
other nonconformance within [30] days, after notice from Customer or discovery
by Vendor.

[X].5 Cooperation in claims. If Customer receives a claim alleging that
Customer's digital properties are inaccessible, Vendor will, at no charge,
promptly provide information, testing, and fixes relating to the Service and
make knowledgeable personnel available.

[X].6 Remedies. Failure to meet [X].4 is a material breach. Without limiting
other remedies, Customer may [suspend payment for the affected Service / receive
service credits of [AMOUNT] / terminate without penalty and receive a refund of
prepaid fees].

[X].7 Indemnity. Vendor will defend and indemnify Customer against third-party
claims to the extent arising from the Service's failure to meet the
Accessibility Standard. [This indemnity is excluded from the limitation of
liability / subject to a separate cap of [AMOUNT]].

[X].8 No overlays. Vendor will not satisfy this Section by means of an
accessibility overlay or automated remediation script.

Drafting commentary. Vendors will resist the indemnity and the uncapped liability; the warranty, the conformance report, the remediation clock, and the cooperation duty are the essential terms and usually obtainable. The business remains responsible to its customers under 42 U.S.C. § 12182 whoever wrote the code, so the contract is about allocating cost and getting fast fixes, not shifting the legal duty. For public entities, the DOJ's 2024 Title II rule in 28 C.F.R. part 35 applies the standard expressly to content provided through contractual, licensing, or other arrangements; for federal procurement, Section 508, 29 U.S.C. § 794d, and the Revised 508 Standards at 36 C.F.R. part 1194 supply the vocabulary vendors already know. For broader contracting, see Cloud and SaaS Agreements: Service Levels, Data Rights, Security, and Exit and Building a Vendor and Third-Party Risk Management Program.

Template 12: Exposure and strategy memo outline

Purpose: a privileged internal memo that records counsel's evaluation and recommendation, so that the decision to settle or fight is made deliberately. Owner: defense counsel. When to use: weeks one to two, updated as facts develop.

PRIVILEGED AND CONFIDENTIAL: ATTORNEY-CLIENT COMMUNICATION / ATTORNEY WORK PRODUCT

To: [CLIENT DECISION-MAKER]   From: [COUNSEL]   Date: [DATE]
Re: [CLAIMANT] accessibility claim: evaluation and recommendation

1. Claim summary: claimant, firm, forum, statutes, relief sought, deadlines.
2. Claimant profile: prior filings (number, forums, outcomes), any rulings on
   standing or coverage, judicial criticism, sector campaign.
3. Truth of allegations: audit findings (F-refs) mapped to each allegation;
   transaction-path impact; Level A vs. AA.
4. Coverage under Title III: physical locations and nexus; circuit law;
   online-only arguments.
5. Standing: residence, plausibility of intent to return, tester status,
   controlling circuit authority.
6. State-law exposure: Unruh (per-offense minimum; ADA-based vs. intent), New
   York SHRL/NYCHRL; other states.
7. Insurance: policies tendered, responses, retention, consent requirements.
8. Remediation: plan, timeline, cost estimate, mootness prospects.
9. Options and costs: (a) settle now; (b) remediate and negotiate; (c) Rule 12
   motion; (d) litigate to summary judgment. Estimated cost and likely outcome
   of each.
10. Recommendation and settlement authority requested.

Drafting commentary. Keep this memo strictly between counsel and the decision-makers. It is the place for candor about weaknesses, and it is what work-product protection is for. Section 5 should apply the controlling circuit's standing law candidly: in the Second Circuit, Calcano v. Swarovski North America Ltd., 36 F.4th 68 (2d Cir. 2022); in the Eleventh, the tester-friendly rule of Houston v. Marod Supermarkets, Inc., 733 F.3d 1323 (11th Cir. 2013); in the Ninth, Langer v. Kiser, 57 F.4th 1085 (9th Cir. 2023). The Supreme Court's dismissal of Acheson Hotels, LLC v. Laufer, 601 U.S. 1 (2023), as moot left the tester question open. For Juniper Lane, the memo concluded that the claim was largely true, coverage was clear because of the stores, the plaintiff's Miami residence and alleged purchase attempt made standing difficult to attack, no state damages statute comparable to Unruh applied, and option (b) was cheapest. Briefing structures for options (c) and (d) are in the Justiciability Toolkit: Standing Allegations, Rule 12(b)(1) Motions, and Mootness Briefing.

Template 13: Mootness declaration outline

Purpose: prove, through a witness with personal knowledge, that the alleged barriers have been fixed and that recurrence is not reasonably expected. Owner: defense counsel, with the remediation lead as declarant and an independent tester as a second declarant. When to use: after the fixes are verified, in support of a letter to plaintiff's counsel or a Rule 12(b)(1) or Rule 56 motion.

DECLARATION OF [NAME] IN SUPPORT OF [MOTION]

I, [NAME], declare:

1. I am [TITLE] at [CLIENT]. I am responsible for [CLIENT]'s website at
   [DOMAIN]. I have personal knowledge of the facts stated here.

2. Allegations. The complaint alleges that the website [ALLEGED BARRIERS].

3. Remediation. Between [DATE] and [DATE], [CLIENT] made the following changes,
   recorded in the remediation log attached as Exhibit A:
   (a) [R-01: description, date deployed];
   (b) [R-02: ...];
   (c) [R-03: ...].

4. Verification. Each change was tested by [INDEPENDENT TESTER], whose
   declaration is filed herewith, using [ASSISTIVE TECHNOLOGY AND VERSIONS] on
   [DATES].

5. Policy and controls. On [DATE], [CLIENT] adopted the written accessibility
   policy attached as Exhibit B. Since [DATE], every website deployment has run
   automated accessibility checks that block release on new violations
   (Exhibit C). [CLIENT] has trained [NUMBER] content staff (Exhibit D), has
   published an accessibility statement with a monitored contact channel
   (Exhibit E), and has scheduled independent manual reviews on [SCHEDULE].

6. Vendors. [CLIENT]'s contracts with [VENDORS] now require conformance to
   WCAG 2.1 Level AA and prompt remediation (Exhibit F).

7. [CLIENT] has no intention of reverting these changes, and the controls
   described above are designed to prevent it.

I declare under penalty of perjury that the foregoing is true and correct.
Executed on [DATE] at [CITY, STATE].
_____________________
[NAME]

Drafting commentary. Voluntary cessation moots a case only if it is "absolutely clear" the conduct "could not reasonably be expected to recur," a "formidable burden" on the defendant, Laidlaw, 528 U.S. 167, and Already, 568 U.S. 85. Websites are easy to change, so paragraph 5 does the heavy lifting: it shows structural controls, not just a one-time fix. Use an independent tester rather than the privileged consultant for paragraph 4, so the privileged memo never goes at issue. A factual mootness challenge is a Rule 12(b)(1) motion, Fed. R. Civ. P. 12(b)(1), on which the court may weigh evidence. The declaration does not touch state damages for past violations, which survive mootness of the injunctive claim. If the case proceeds, a mootness ruling also limits the plaintiff's fee claim, because voluntary change without a judicial order does not make the plaintiff a prevailing party under Buckhannon.

Common drafting mistakes

  • Attaching the audit to a response letter. It waives protection and hands the plaintiff a roadmap.
  • Calling the consultant's deliverable a "compliance report" or "certification." It reads as a business document and creates a promise the next plaintiff can test.
  • Mixing the remediation log with legal evaluation. The log will be produced; the evaluation should not be.
  • Promising "full compliance" in an accessibility statement or settlement. Promise a standard, a process, and a contact channel.
  • Forgetting state law in the release. A federal-only release leaves Unruh and New York claims alive.
  • Accepting a consent decree by default. It costs fees, time, and flexibility.
  • Letting vendor contracts renew without accessibility terms. The next defect may live in someone else's code.

This document is general information, not legal advice for any particular situation; adapt each template to the facts, the forum, and current law before use.

Related Documents

Related Articles

Related Guides

Related Checklists

Related Toolkits