Web development
I'm a blind developer, so I build websites with a screen reader. If something doesn't work, I'm the first to know.
I navigate the web with VoiceOver every day. When I build a site, I run into the same problems your users would -- except I catch them while I’m writing the code.
Why this is different
Most people audit the site, write a report, and leave you to find a developer. I just do both.
I use the thing I'm building
I use a screen reader for everything. Unlabeled buttons, image-only controls, missing form context — I hit all of that firsthand.
One person, the whole way
I find the problems and write the code to fix them.
Compliance that holds up
ADA, EAA, WCAG. I can help you meet them.
Services and pricing
I don't love putting prices on a page, but it's more honest than making you ask.
Site rebuild and remediation
Fix what's there
Starting at $2,000
I go through your site, find what's broken, and rebuild the parts that need it.
- Full accessibility audit
- Rebuild of the pages and components that need it
- Tested with a screen reader and keyboard throughout
- Clean markup that makes sense
- Notes on what I changed and why
For sites that need accessibility fixes.
New accessible site
Start fresh
Starting at $1,500
A new site, accessible from the start.
- Responsive -- works on whatever device
- Semantic HTML, proper headings, landmarks
- Forms and interactive stuff that actually works
- Tested before you ever see it
- Lightweight, no framework bloat
New projects, restarts, or redesigns.
Ongoing retainer
Keep things working
Custom monthly
Sites change over time. I'll keep checking in so things don't break between launches.
- Monthly review of anything new or changed
- Quick fixes when something breaks
- Help for your team on keeping things accessible
- Bigger check-in every quarter
Good fit for teams that ship often and don't want accessibility to slip.
Why me
VoiceOver isn't a testing tool for me. It's just how I use my computer.
Not for testing -- for everything. I'm not simulating anything. That changes how I build things in ways a certification can't.
What you end up with
- HTML that makes sense to navigate
- Focus and keyboard interaction that works the way you'd expect
- Forms with real labels and error handling
- Fast pages, nothing heavy
- Code someone else can maintain later
How it works
The process stays pretty straightforward.
We talk.
You tell me what's going on. If it's a rebuild, I'll look through your site first.
I build, and you see it as I go.
I don't disappear for weeks. You see progress as I go.
You get something that works.
A finished site, plus notes on what I changed and why.
Good fit
You probably already know something's not right.
Maybe you got a letter, or a deadline's coming up, or someone finally said it out loud. Whatever it is, it's a good time to reach out.
Things I hear a lot
- We got an ADA demand letter and need to respond
- There's an EAA or WCAG deadline coming up
- A client or vendor flagged accessibility issues
- We're launching something new and want to do it right
- We tried fixing accessibility before, but it didn't really stick
Interested?