We audit other people's products against WCAG 2.1 AA. It's only fair that this site holds itself to the same bar. This page reports where we stand, what we've tested, and what we know is still imperfect. Real audits don't end at a single pass.
All non-deferred surfaces pass WCAG 2.1 AA. Two items are explicitly out-of-scope for this iteration's audit (see "known issues" below) because they are downloadable artifacts or copy still in production.
me stubs or pending content that will be rebuilt before launch.WCAG 2.1 Level AA · the W3C recommendation, global baseline.
Section 508 (revised 2018) · the US federal standard.
EN 301 549 · the European harmonized standard tied to the June 2026 EAA deadline.
Updated whenever an audited surface changes.
Tracks site iteration. v1.0 lands at launch.
15+ years of accessibility specialty — the same lead who audits our clients.
If our own statement hid behind perfect-conformance language, we'd be doing the thing we tell clients not to do. Here's what's still imperfect and why.
What's there: two PDF download cards on the home page (general and healthcare-specific). The PDF files themselves are in production.
The plan: PDFs tagged for screen-reader navigation (logical heading order, reading order, table semantics), pass automated PDF/UA scan, hand-verified with VoiceOver before the links go live.
What's there: page structure, regulatory framework, six surface tiles — all in production-fidelity chrome.
The plan: client-experience copy follows once seed material lands.
Everything else on the site passes WCAG 2.1 AA. Deferred items above are explicitly out-of-scope for this iteration and will be re-audited as they ship.
Identical to what we run for clients. Same order, same tooling, same honesty about the gap between automated and lived-experience findings.
axe-core via Lighthouse + WAVE + manual color-contrast measurement. Clears the technical baseline; the harder failures don't surface here.
Every page walked against the AA criteria. Keyboard navigation, focus visibility, heading hierarchy, landmark structure, semantic tagging, ARIA usage, text alternatives.
VoiceOver (macOS), NVDA (Windows), TalkBack (Android). Keyboard-only navigation. 200% zoom and 400% reflow. Deferred for v1: formal disabled-user testing of the conversion flow with assistive-tech users on the calendar embed.
nce wired.Status per principle. Criterion-level conformance available on request — this summary is the right grain for most readers.
Content presented in ways users can perceive — including via assistive technology.
aria-hidden; content images have explicit alt.Interface usable by anyone — not just mouse users.
<header>/<main>/<nav>/<footer> landmarks; descriptive page titles.Information and operation must be understandable.
lang="en" declared; reading level kept below Grade 12 on all marketing pages.aria-current="page" on active nav link.Compatible with current and future assistive technology.
Accessibility findings are how a real audit works. We want yours. Tell us what broke, on which page, with which tool or assistive technology — and we'll respond within 5 working days.
email · [email protected]
response time · 5 working days
what to include · page URL, browser + AT, what you expected, what happened