Legal consulting · Web accessibility
A technical read on website accessibility claims
For attorneys and the businesses they represent in ADA website matters. I’ve spent my career building production web frontends and user experience, so I can tell you what a site actually does for someone using a keyboard, a screen reader, or a magnifier, and what it would take to fix it.
Direct invoice · $150/hr
Engagements
-
Consulting
Calls with counsel, a read of the complaint or demand letter, and a plain-language explanation of the technical issues it alleges.
$150/hr
Usually 2–4 hours
- Working calls with counsel
- Complaint read against the live site
- Plain-language notes on each alleged barrier
-
Deep dive
A hands-on review of the site, measured against WCAG 2.1 and 2.2 Level AA, with a written list of issues and fixes. Billed hourly at the same rate. I check with you before going past 20 hours.
$2,250–$3,000
About 15–20 hours
- Dated, reproducible findings with screenshots
- Each issue tied to a WCAG success criterion
- Severity ranked by impact on real tasks
- Fix list a developer can work from
A deep dive for a site with many problems usually lands at 15–20 hours, below most agency audits. Smaller sites take less.
What I check
The tasks a real patient or customer tries to finish
An automated scan is the first ten minutes. The findings that matter come from working through the site the way a person with a disability would.
-
Keyboard only
Can someone who can’t use a mouse reach every link, open every menu, and finish the form? Is focus visible the whole way?
-
Screen readers
Do images, buttons, and form fields have names that make sense out loud? Do errors get announced?
-
Low vision
Color contrast, text resizing, and whether the page still works when zoomed to 400% on a narrow screen.
-
Forms and booking
Labels, required fields, error messages, time limits, and CAPTCHAs on the flows that matter: booking, contact, intake, payment.
-
Media and documents
Captions on video, pause controls on carousels, and whether downloadable PDFs are tagged and readable.
-
Third-party widgets
Scheduling tools, chat, reviews, and overlay plugins, which often introduce barriers of their own.
Forms are where I go deepest. I built and run TendForm, a form builder with a HIPAA tier, so intake and booking flows in healthcare are familiar ground.
Inquiry
Start with a conflict check
Tell me about the site, where the matter stands, and who the parties are. Leave out anything privileged. If the timing and rate work, my direct line appears at the end.
Open in a new tab ↗Do you give legal advice?
No. I’m a technical consultant, not a lawyer. I explain what a site does and doesn’t do for people with disabilities, and why. Legal conclusions stay with counsel.
Do you work for plaintiffs or defendants?
Either. The work is the same: find out what the site actually does, and write it down accurately. I run a conflict check before taking a matter.
Is expert testimony included?
No. These engagements cover consulting and written findings. Anything beyond that needs a separate agreement.
How do you keep the work confidential?
When counsel engages me, I work at their direction and label findings accordingly. Case materials stay off shared drives and out of anything public, and they’re returned or destroyed when the matter closes.
Isn’t an automated scan enough?
No. Automated tools catch roughly a third of accessibility issues. They’re a starting point. The rest takes a person with a keyboard, a screen reader, and a zoomed browser working through the tasks a real user would try.
How do I pay?
I invoice directly, net 15. ACH bank transfer is preferred and card is accepted. Consulting hours are billed when they’re done, not at the end of the matter.