I read your site the way a screen reader does.
You're probably here because you got an email about a specific problem on your own site. This page explains who sends that email, how the findings are produced, and what happens if you reply.
jump to a real finding ↓What a finding looks like
Every email includes screenshots like this, taken from your own site, with the specific element and the specific rule it fails, so you can hand it straight to whoever maintains the site.
How this is produced
- Scans run on axe-core, the open source engine also inside Chrome DevTools and Microsoft's and Google's own tooling, against the pages that matter: your booking and contact forms, not just the homepage.
- Findings are weighted by how often that failure class shows up in real complaints and by which page it's on. A contrast issue in a footer is a footnote. The same issue on an appointment form is the transaction the business exists to complete.
- Only the findings clear enough to describe in two sentences make it into a first email. Everything else goes in the full report, if you want one.
What this isn't
- Not a lawsuit prediction. I'm an engineer describing defects on your site, not a compliance authority, and you won't get a message telling you that you're about to be sued.
- Not an overlay pitch. If your site already runs a widget like accessiBe or UserWay, the findings above are what still fails with it installed, screenshots included.
- Not a compliance guarantee. Nobody can promise legal immunity, automated or not. Passing an automated scan is not the same as a blind visitor being able to book an appointment on your site, and I won't tell you it is.
Worked out ahead of time
Hours times an hourly rate, with a per-rule cap so a few hundred repeated contrast errors don't produce a number that doesn't match reality, plus a fixed block for the manual work a scanner can't do: a keyboard-only pass, a screen reader spot check, the written report, and a retest once fixes ship. No retainer, no subscription, nothing added that you didn't ask for.
If you reply
The first email doesn't ask you for anything. If you want the full audit, I'll scan every page that matters, not just the ones in the first email, and send back a prioritized list with a quote. If you'd rather have your own developer fix it, the findings are specific enough to act on without hiring me at all.
Who's behind this
I'm Manh Do, a web accessibility engineer. I run these audits myself, one practice at a time. Not an agency, not a call center: every email you get from mdtlabs was read by the person who sent it.