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

Your accessibility person, on the projects that need one.

For web, product, and marketing agencies that ship client sites and get asked about accessibility after the fact. Manual testing, fixes in your codebase, your name on the deliverable if you want it.

Talk about this Email directly
Fit

Who this is for, and who it is not for

For

  • Agencies with 3 to 40 people and no in-house accessibility specialist
  • Clients in Ontario, US public sector, higher education, healthcare, or finance
  • Any client that has received a letter about their website

Not for

  • Agencies looking for a widget or overlay to resell
Triggers

What starts this work

A client received a demand letter or AODA noticeThe site you shipped is named in it, and the client is asking you what to do.
An RFP requires WCAG conformance or a VPATThe client cannot bid without a document, and nobody on your team can produce one.
A redesign is in QA and nobody has keyboard-tested itLaunch is close, the templates are done, and accessibility was a line item nobody owned.
You want to sell an accessible buildYou need someone to define what that means and stand behind it on delivery.
Deliverables

What I do

One person covers the review, the fixes, and the document. Scope is written per project.

  • Pre-launch review of templates and components, with findings written for your developers
  • Remediation in your stack: HTML, CSS, JavaScript, PHP, Laravel, WordPress, and Drupal
  • Re-test and a written conformance summary your client can keep
  • Accessibility statement drafting for the client site
  • White-label or co-branded delivery, your choice, agreed per engagement
  • Design-stage review of Figma files or prototypes before build
How it works

You keep the client. I do the accessibility work.

The arrangement is simple and written down before work starts.

  1. The agency owns the client relationship

    You decide whether I appear by name, under your brand, or not at all. The client hears from me only if you want them to.

  2. I invoice the agency

    One invoice to you, on the terms we agree. You bill the client however you normally do.

  3. Scope is written per project

    Each project gets a short written scope: templates, flows, standard, deliverables, and dates. No retainer required to start.

  4. NDA is standard

    Your paper or mine, signed before I see the repository or the client name.

Ontario clients

Redesigns shipping in 2026 land inside the AODA filing window.

Any Ontario client with 50 or more employees has a WCAG 2.0 AA website obligation under the AODA, and a compliance report due December 31, 2026. A redesign delivered this year is what they will be certifying. Read the AODA 2026 thresholds before you scope the build.

If a client has already received a letter, the response is a different engagement. See what counsel will need from a technical reviewer.

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

Placeholder: Agencies I have worked with

This block is reserved for the practitioner to fill. No names are listed until they are confirmed.

FAQ

Questions asked before scoping

Can you work under our brand?

Yes. Reports, statements, and re-test summaries can carry your name, both names, or mine. We agree it per engagement and it is written into the scope.

Do you need access to our repo, or can you work from a staging URL?

Either. Reviews can run against a staging URL with test accounts. Remediation works best as pull requests in your repository, but I can also deliver patches or written changes for your developers to apply.

What happens if the client wants to talk to you directly?

You decide. I will join a call with you present, take questions through you, or talk to the client directly if you prefer. The relationship stays yours either way.

Do you do overlays or widgets?

No. Overlay widgets do not fix the underlying code, and sites running them have been named in hundreds of lawsuits, so they add exposure rather than remove it.

Can you review designs before we build?

Yes. A design-stage review of Figma files or prototypes covers contrast, focus order, component states, form patterns, and content structure. It is the cheapest point to fix most of what an audit would find later.

Related engagements

AODA 2026Thresholds and the December 31, 2026 filing for Ontario clients Demand letter supportWhen a client site has already been named in a letter
Next step

Send the project and the deadline.

A short call covers the stack, the client context, whether the work is branded, and what the first deliverable should be.

Talk about this Email directly