An ADA demand letter or filed complaint needs two coordinated responses: legal counsel manages the legal strategy; an accessibility team establishes the technical facts and fixes the barriers. Do not let a developer, scanner vendor, or accessibility agency present technical work as legal advice.
This guide covers the technical response. If you need immediate help, review our emergency accessibility remediation service or request an urgent assessment.
Important: eLan Technology provides website accessibility testing and remediation, not legal advice. Your attorney should interpret the claim, deadlines, jurisdiction, and response obligations.
First 24 Hours: Stabilise the Situation
1. Send the document to qualified legal counsel
Counsel should determine whether the document is a demand letter, complaint, summons, or another type of notice. They should also direct preservation requirements and communications with the claimant.
Do not rely on a generic online timeline. Deadlines and response obligations vary by document, court, jurisdiction, and procedural posture.
2. Preserve the current technical evidence
Before changing the website, create a dated record of:
- URLs and user journeys named in the claim
- Current templates, components, themes, plugins, and third-party widgets
- Screenshots or recordings of reproducible barriers
- Automated scan exports and tool versions
- Recent releases that may have introduced the issue
- Analytics showing which pages and journeys are actively used
This gives counsel and the remediation team a reliable baseline. It also prevents later confusion about what existed before a fix was deployed.
3. Do not confuse an overlay with remediation
An accessibility widget may change some presentation or input behaviour, but it cannot establish conformance across the underlying content, semantics, forms, focus order, custom components, documents, and task flows.
In 2025, the US Federal Trade Commission required accessiBe to pay $1 million to settle allegations that it misrepresented the ability of its automated product to make any website WCAG compliant. The practical response is to fix barriers in the source and verify the resulting experience.
Read our detailed guide to accessibility overlays and source-level remediation.
Next 24–72 Hours: Establish the Technical Facts
Define the audit scope
Begin with the journeys named in the claim, then identify shared templates and components that may reproduce the same barrier elsewhere.
A focused emergency scope often includes:
- Homepage and global navigation
- Search, product, cart, checkout, or booking journey
- Registration, login, and account management
- Contact, payment, and validation flows
- PDFs or documents identified in the claim
- Cookie, chat, consent, and other third-party interfaces
Use hybrid testing
Automated checks are useful, but they are only one part of the evaluation. The audit should include:
- Automated rules with reproducible selectors and URLs
- Keyboard-only operation and visible focus review
- Screen-reader testing of important journeys
- Browser zoom, reflow, and text-spacing checks
- Form labels, instructions, errors, and status announcements
- Contrast and non-text contrast evaluation
- Captions, transcripts, and other media alternatives
- Accessible names, roles, states, and values for custom controls
The report should map each finding to the relevant WCAG success criterion, describe user impact, and provide enough evidence for a developer to reproduce the problem.
Prioritise Remediation by User Impact
A scanner can produce thousands of repeated instances. That does not mean thousands of independent engineering problems.
Prioritise:
- Blockers in the journey named in the claim
- Keyboard traps and controls without accessible names
- Form and checkout failures
- Shared navigation, dialog, and template defects
- Severe contrast, reflow, and content-alternative barriers
- Repeated content-authoring issues
Fix shared components first. One corrected navigation component can resolve the same barrier across hundreds of pages.
Retest Before Calling a Finding Resolved
A code change is not the same as a verified fix. Retest using the same method that reproduced the original barrier and record:
| Field | What to document |
|---|---|
| Finding | Plain-language description and affected user |
| WCAG reference | Applicable success criterion and level |
| Original evidence | URL, component, steps, and test environment |
| Remediation | Source-level change that was made |
| Retest result | Pass, partial, fail, or not tested |
| Remaining limitation | Known exception, dependency, or follow-up |
| Regression control | Automated test, review step, or ownership |
Your attorney can decide how this technical record should be used in the legal response.
ACR and VPAT: Use the Terms Correctly
A VPAT is a template maintained by the Information Technology Industry Council. A completed disclosure is commonly called an Accessibility Conformance Report (ACR).
An ACR can support procurement and stakeholder review when it accurately describes how the evaluated product supports each applicable criterion, including known gaps. It is not a universal certification, a legal guarantee, or a substitute for the underlying audit evidence.
Current DOJ Title II Timeline
The DOJ Title II web rule applies to covered US state and local government web content and mobile apps and names WCAG 2.1 Level AA.
Following an April 2026 interim final rule, the general compliance dates are:
- April 26, 2027: public entities serving 50,000 or more people
- April 26, 2028: smaller public entities and special district governments
Those dates concern Title II public entities. They should not be presented as a universal private-business deadline.
What eLan Technology Delivers
Our emergency process can include:
- Initial response to an emergency assessment request within 24 hours
- Scoped automated and manual WCAG testing
- Criterion-level findings with reproducible evidence
- Code-level remediation across shared templates and components
- Retesting and status documentation
- ACR preparation using the appropriate VPAT template when separately scoped
- Ongoing regression testing after the urgent work
A rapid audit and remediation plan starts at $1,500 USD. Full remediation is quoted after the affected surface and issue types are understood.
Review the 30-day emergency remediation process or request an urgent assessment.