Ontario businesses & non-profits: the AODA reporting deadline is December 31, 2026. Check what applies to you
Legal response support

You received a demand letter about your website. Here is what counsel will need from a technical reviewer.

Claim-by-claim validation, evidence, and a remediation plan your lawyer can attach to the response. Then the fixes themselves.

Fit

Who this is for, and who it is not for

For

  • Businesses and their counsel responding to an ADA Title III, Unruh, or AODA-related letter or complaint
  • Law firms that want a standing technical reviewer for accessibility matters

Not for

  • Anyone looking for a legal opinion. This is technical support to counsel, not legal advice.
Triggers

What starts this work

A demand letter or complaint arrivedIt names a plaintiff, lists alleged barriers, and asks for a consultant, a fix within 60 to 90 days, a statement, and monitoring.
A settlement requires an independent consultantThe agreement calls for third-party verification and periodic reporting, and you need someone to do it.
Counsel needs a declaration on current site stateWhat was fixed between the plaintiff's test date and today has to be documented by someone who tested it.
The insurance carrier asked for an assessmentThe carrier wants an independent view of the allegations before deciding how to respond.
Deliverables

What I do

The validation report comes first. Everything after it waits for counsel's decision on the response.

  • Claim-by-claim validation against the actual site, with severity (blocks a task, degrades a task, cosmetic), evidence, and test method for each
  • Written findings letter counsel can reference. It is a technical document, not a legal opinion.
  • Remediation plan with sequencing and effort ranges
  • Remediation in code, then re-test
  • Accessibility statement and feedback mechanism set up on the site
  • Post-settlement verification and periodic reporting if the agreement requires it
Process

Validation first, then whatever counsel decides.

Response deadlines are short, so the first deliverable is the one counsel needs to decide anything.

  1. Intake call with counsel within two business days

    The letter, the site, the plaintiff's test date, and the response deadline. NDA or engagement through counsel as needed.

  2. Validation report

    Each alleged barrier is tested on the live site with keyboard and screen reader, rated by whether it blocks a task, and documented with evidence and test method. Anything already fixed since the plaintiff's test date is recorded as such.

  3. Counsel decides on the response

    The remediation plan, the statement, and the fixes follow only after counsel has chosen how to respond.

What the letter usually contains

A scan is not a finding.

Most letters follow one shape: a named plaintiff, a list of alleged barriers, and requested relief. The list is often generated by an automated scanner, which detects roughly a third of real failures and reports some things that are not failures at all. Validation separates the allegations that block a task from the ones that are cosmetic or wrong, and that distinction is what counsel argues from.

Counsel also needs to show good faith: what has already been fixed, what is planned, and that a statement and feedback route are in place. Those are deliverables here, not promises. If the site was built by an agency, the agency can bring me in directly. If it was built with an AI site builder, the failure profile is predictable and fixable.

Why a named practitioner

One person scopes it, tests it, and fixes it.

  • Named practitionerThe person who scopes it does the work
  • Manual + assistive techKeyboard and screen-reader testing
  • Fixes, not just findingsRemediation from the same person
FAQ

Questions asked before scoping

Is this legal advice?

No. Accessibility consulting is not legal advice, and no consultant can guarantee that an organization will avoid a complaint, claim, or enforcement action. Everything here is technical support to your counsel, who decides how to respond.

How fast can you validate the claims?

The intake call is within two business days. A validation report for a typical letter, meaning ten to thirty alleged barriers on one site, follows within five business days of access. Larger claim lists are scoped on the call.

Will you sign a declaration?

Placeholder (VERIFY with practitioner): state whether a signed declaration or affidavit on the tested state of the site is offered, and on what terms.

The letter cites an automated scan. Does that matter?

Yes. Scanner output includes false positives and misses most interaction failures, so a list built from one is both over-inclusive and incomplete. Validation tests each item manually and rates it by user impact, which is what a response can rely on.

Can you handle the monitoring period after settlement?

Yes. Agreements commonly require third-party verification and quarterly reporting for one to three years. That is a standing engagement with re-tests on a fixed schedule and a dated report each time.

Next step

Send the letter and the URL.

The intake call is with counsel within two business days. The validation report is the first thing delivered.

If your counsel prefers to make first contact, that is fine.