Accessibility
Last updated: July 31, 2026
This site should work for you—with a keyboard, with a screen reader, at whatever text size you need, on whatever device you have. This page says what we've built toward, what we've actually tested, and what we already know isn't perfect. If something here doesn't work for you, that's a bug and we want to hear about it.
What we're aiming for
We build toward WCAG 2.2 Level AA, the standard most accessibility law and policy points at. We're not claiming a certification—nobody has audited this site from outside, and we'd rather tell you what we know than imply more.
What's actually been done
Checked across every page on the site, most recently on July 31, 2026:
- Keyboard. Everything you can do with a mouse, you can do with a keyboard. There's a "skip to main content" link, focus is always visible—including on the dark sections, where a default focus ring would disappear—and focus never gets trapped anywhere.
- Structure. Real headings in order, without skipped levels; landmarks so you can jump between regions; images carry alternative text; every link says where it goes rather than "click here."
- The contact form. Every field has a real label. If something's wrong, the error is announced, attached to the specific field, and focus moves to the first one that needs fixing—so you're not hunting for what went wrong.
- Text size and zoom. The layout reflows down to a 320-pixel-wide window without a horizontal scrollbar, which is what zooming to 400% amounts to.
- Motion. If your system asks for reduced motion, we honor it.
- Color. Contrast meets AA, and color is never the only thing carrying meaning.
- Automated testing. Every page passes an automated accessibility audit with no failures, and an independent third-party scan run on July 31, 2026 returned nothing outstanding. We treat that as a floor, not a finish line—automated tools catch only a fraction of real problems, which is why the next section exists.
What we know isn't finished
The honest list. We'd rather you know these up front than discover them:
- We haven't tested with a real screen reader yet. The markup is built correctly and reads correctly in testing tools, but that isn't the same as sitting down with NVDA, JAWS, or VoiceOver and using the site. That testing is planned. Until it's done, we won't claim it.
- Embedded third-party content. The booking calendar and the maps come from Calendly and Google. We deliberately don't load either until you press a button, and there's always a plain link to the same thing—but once loaded, their accessibility is theirs, not ours. If one of them is the barrier, email works and reaches the same place.
- The free tools. They're built to the same standard as the rest of the site, but they're the most interactive thing here, and interactive things are where accessibility problems hide. Extra scrutiny welcome.
Tell us when something doesn't work
This is the part that matters most. If any part of this site is hard or impossible to use, email bill@withregardco.com. Tell us what page, what you were trying to do, and what happened—and what you're using, if you know it (screen reader, browser, phone or computer). Any detail helps; none is required.
We'll reply within one business day, the same as any other message. If it's something we can fix, we'll fix it and tell you when it's done. If it's going to take a while, we'll say so and give you a straight answer about when. And if you needed something from this site and couldn't get it, tell us that too—we'll just get it to you another way.
Why we bother
Because a site that only works for some people isn't finished. Most of what's on this page is ordinary good practice that costs nothing when you do it from the start—which is the same argument we'd make to you about your own site.