Accessible
Everyone can use it.
What we mean
Anyone who arrives can use the thing, whatever device, connection or ability they bring. Someone on a five-year-old phone on a weak signal. Someone who cannot see the screen and hears it instead. Someone who cannot hold a mouse and moves through it with a keyboard. Someone who gets dizzy when things move.
Accessible means the product was built for all of them from the first screen, not patched for them at the end.
How we do it
We hold every build to WCAG 2.2 AA and write that into the proposal, so it is a promise rather than a hope. Before a client sees a preview, we go through every page with a keyboard alone and with a screen reader. We turn reduced motion on and check that every animation has a gentler version. We measure how fast the first screen appears on a phone, because a slow page is a page some people cannot use.
Automated checkers run too, but they catch under half of what matters, so the manual pass is the real one. On a site that serves the public, we also pay someone who uses assistive technology every day to use it and tell us what broke.
Why it matters
For the person using it, this is the difference between being included and being turned away by a door that looks open. For a practice or a business, it is the difference between a patient who books and one who gives up, and an inaccessible website is a legal risk no practice needs.
A note from Gina
I want to be honest about where this stands. I have built accessibly for years in the ways a checklist can catch: contrast, labels, focus, structure. I have not yet sat beside someone who uses a screen reader and watched them use something I made. That is the next thing I am doing, and I will write up what I learn, including what I got wrong. A value you cannot test is a slogan. This one I intend to test.