I build custom apps and tools.
If you need a program to do something and can't find one that does it, tell me about it and I'll see if I can build it. Most of what I've made so far is Mac apps. Some of it is for getting around software that doesn't work with a screen reader.
Things I've built
Most of it started because I needed it. I've made more than a dozen Mac apps for my own use. These three have their own pages.
- A Pro Tools accessibility layer that makes hidden controls reachable with VoiceOver.
- A Komplete Kontrol accessibility layer for Native Instruments' music software.
- ScreenRecognition, which finds buttons and text in apps VoiceOver can't see at all and puts something navigable on top.
How a project goes
- You tell me what you need and what you're trying to get done. That's enough to start.
- I look into whether it can be done. If it can't, or not in a way I'd trust, I'll say so before you pay anything.
- I build it, test it, and you use it for a while before we call it done.
If it touches patient, client, or financial records, tell me up front. It changes what I can build and where that data is allowed to go.
Pricing
Every one of these is different, so I quote a flat price after we talk. You'll know the number before I start.
Companies update their software, and when they do, a tool built on top of it can stop working. I offer a monthly fee to keep it working. If you'd rather skip that and pay for fixes when they come up, that's fine as well.
If it's an accessibility problem at work
If software you need for your job doesn't work with your screen reader or other assistive technology, your employer may be responsible for paying for a fix as a workplace accommodation. Vocational rehabilitation agencies sometimes pay for this kind of thing too. I can write the quote in whatever form they ask for.
Tell me what you need.
I mostly build for the Mac. If you're on Windows or a phone, ask anyway, since a lot of things can be built as a web page that works anywhere.