Web compliance, done at the code level.

Alexander Danielsson — independent web compliance engineer. One person, not an agency.

What I do

Enforcement reaches websites in a handful of ways — an ADA lawsuit, an FDA warning letter, a regulatory deadline, a demand letter about texts or trackers. Different statutes, same ending: the website has to change, the change has to be real code and copy, and someone has to document it well enough to close the file. That's the work I do.

How I find the work

I monitor public enforcement data with software — federal court dockets, FDA's published warning letters, regulatory deadlines — as they post. When I write to a business, it's usually because its name appeared in a public record hours earlier, and the homework is already attached. Everything I reference is verifiable at the source: pacer.gov, CourtListener, fda.gov.

How every engagement runs

  1. The homework arrives first — free. An audit or claims inventory specific to your site, each finding mapped to the standard at issue. Yours to use however you'd like: me, your developer, any agency.
  2. Implementation. Real code and copy in your theme or CMS. You'll know the exact cost before anything starts — one number, no hourly meter, and it doesn't move if something turns out stubborn.
  3. Validation and the letter. The work is validated, then documented in a dated letter — what changed, where, and against which criterion. The document your attorney uses, or your records office keeps.

Who you'd be dealing with

An independent freelancer — one person, not an agency. I'm connected to no plaintiff, court, law firm, or agency, on any side. Your lawyer handles the case or the response; I handle the website. The obligation these matters end with exists either way — someone has to actually build it.

Contact

Email [email protected]. You'll get a reply from me — usually the same day, always from a person.