Every visitor gets the full site

This site is built to WCAG 2.2 AA, the Web Content Accessibility Guidelines, on every page and in both the light and dark themes. Accessibility is a build gate in this studio, not a cleanup pass: pages ship when they meet the bar, and the same bar applies to the sites we build for clients.

• Body text is set at 18px on a measured palette. Body text pairs are engineered past a 7:1 contrast ratio, above the 4.5:1 minimum the guidelines require, and nothing ships below the minimum. Contrast is never caveated by text size and never faked with opacity.
• Every page works by keyboard alone: a skip link at the top, a visible focus ring on every interactive element, and no traps.
• Headings, landmarks, and labels are semantic, so screen readers get the same structure sighted visitors see.
• If your system asks for reduced motion, the site treats that as a designed variant: nothing disappears, and no content requires animation to be understood.
• Text scales to 200% without breaking the layout, and controls are sized for touch.

Every page runs automated checks with axe, an industry-standard accessibility engine, in both themes before it ships. The current result is zero violations across every route, in both themes, re-run after each release.

Automated tools catch only part of what matters, so each release also gets hands-on passes: full keyboard runs, reduced-motion runs, and small-screen checks at phone widths. We would rather tell you what was tested and what it found than call a site fully accessible, which is not a claim any tool can support.

We build to WCAG 2.2 AA and state conformance to WCAG 2.1 Level AA. That is not hedging. No United States federal rule references version 2.2 yet, and content that conforms to 2.2 also conforms to 2.1, so building to the newer version and claiming the referenced one is the honest way around.

We do not describe this site, or any site we build, as certified. There is no accessibility certification a body can grant on a regulator’s behalf. What exists is a standard, a test, a scope, and a date, and those are the four things we publish.

A practice is answerable for the things bolted onto its site, not only the pages we write: the scheduler, the chat widget, the map, the patient forms. We test those too, and when one fails we say so before launch rather than after, because replacing it is a procurement conversation with time in it.

We do not install accessibility overlay widgets. They sit on top of the markup instead of fixing it, and the fixes they claim are not the fixes an audit looks for.

Website accessibility is a legal question for medical practices as well as a design one, through Section 1557 of the Affordable Care Act and the Americans with Disabilities Act. The federal deadlines attached to those rules moved in 2026 and are being litigated, so we do not quote a date as settled and we would be careful of anyone who does.

We are not attorneys and this is not legal advice. Your counsel advises you on timing and obligation. What we control is the build, and the standard those rules point at is the one we already work to, which is the practical answer whichever way the dates land. The wider posture is on the compliance page.

Nothing is currently listed. When a barrier is found or reported, it appears here with its status until a release fixes it. An empty list is a claim, and we expect you to test it.

If something on this site is in your way, tell us and we will fix it. It helps to know the page, what happened, and the browser or assistive technology you were using. We reply within two business days.

• Email contact@tallbunny.com
• Call 864-606-2712