Accessibility isn’t a feature I added to this site. It’s the reason the site exists, and it’s the standard I hold my own work to. This page is my honest account of how this site is built, where it stands today, and what I’m still working on — because a statement that only lists what’s already perfect isn’t worth the pixels it’s printed on.
My commitment
I believe access is a right, not an accommodation. That belief comes out of the Disability Justice tradition, which starts from the understanding that disability is produced by environments and systems — not by people — and that the work of removing a barrier belongs to whoever built it. I build to that standard here, and I hold my clients’ work to it too. When something on this site excludes you, that’s mine to fix, not your burden to work around.
What I’m aiming for
My conformance target is WCAG 2.2, Level AA — the Web Content Accessibility Guidelines published by the W3C. I aim for AA across the whole site: sufficient color contrast, full keyboard operability, meaningful headings and landmarks, text that resizes and reflows, form fields with real labels, and content that works with a screen reader from the top of the page to the bottom.
I want to be precise about the word target. I am working toward full 2.2 AA conformance, and I’m not going to claim I’m fully there on every page, every day. Anyone who tells you their site is “100% compliant” is either not testing it or not being straight with you. I’d rather tell you the truth and show you the work.
How this site is built and tested
I don’t audit accessibility from the outside and hope for the best. I use this site the same way many of my visitors do — by keyboard and with a screen reader — so the barriers you would hit are barriers I hit first. That’s the whole difference between building accessibility in and bolting it on afterward: I live inside the thing I’m shipping.
I also build with AI as a working partner, and I’m open about that, because using AI responsibly is part of what I do professionally. AI helps me draft, structure, and move faster. But nothing reaches this site on the strength of an AI’s say-so about accessibility. Every structural and interactive piece is verified by me, in the environment my visitors actually use. The AI proposes; I test, and I decide.
What I know isn’t perfect yet
This is the part most statements leave out, so it’s the part I’ll spend the most words on.
- Third-party embeds. Some tools I rely on — like my scheduling widget — are built and controlled by other companies, and I can’t reach inside them to fix everything. I choose them carefully and I test them, but where one creates a barrier I can’t resolve, I’ll always give you another way to reach me or book time. If a third-party piece blocks you, that absolutely counts as a barrier worth reporting.
- Ongoing content. I write and publish regularly. New posts and pages get the same standard as everything else, but I review on a rolling basis — so if something recent slipped past me, telling me is the fastest way to get it caught.
- The honest unknown. I test thoroughly, but I use a particular set of tools in a particular way. If your setup surfaces something mine doesn’t, I want to hear it — you’ll have found something I genuinely couldn’t have caught on my own.
Found a barrier? Tell me.
If any part of this site keeps you from doing what you came to do, I want to know — and I will personally respond. There’s a form built for exactly this, kept separate from my general contact form so your report goes straight into the right stream: report an accessibility barrier.
You don’t need to diagnose it, name a guideline, or soften it. Tell me what you were trying to do and what got in your way, in your own words, and I’ll take it from there.
Last reviewed: July 4, 2026.