What We Keep Finding
A telehealth visit is a chain of small gates. The appointment email, the intake form, the camera prompt, the waiting room, the join button. A sighted patient clears all five in about a minute. A patient using a screen reader can lose the appointment at any one of them. The waiting room is the gate that fails most quietly, because a queue position that redraws on screen without being announced leaves the patient no way to tell whether anything is happening at all.
Then there are the captions, and the trap is not the missing ones. It is the automatic ones. W3C is direct about this. Auto-generated captions do not meet accessibility requirements unless somebody has confirmed they are accurate, and usually they need real editing first. The example W3C uses is a dropped negation, where a spoken "You should not preheat the oven" comes out written as "You should know to preheat the oven." Move that same error onto a call about a dose and you can see why we check the captions against what was actually said, rather than checking that captions ran.
The law reaches most of this audience already, through the practice rather than through you. A provider billing Medicare or Medicaid owes WCAG 2.1 Level A and AA under the HHS Section 504 web rule by May 11, 2027, or May 10, 2028 if it has fewer than 15 employees. A platform selling into those practices inherits that duty through its contract rather than through the statute. In plain terms, your customers will start asking you for evidence a good while before their own date arrives.
What We Check
- Join a visit end to end by keyboard alone, from the appointment email to the video
- Fill in the intake and consent forms with a screen reader before the visit starts
- Check the waiting room announces its own updates instead of only redrawing them
- Compare the live captions against what was actually said, word by word
- Test the reschedule and cancel paths, the ones patients reach for when plans change
What You Get
Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.
The format is not a mystery either. Read the sample report before you spend anything.
The Honest Limit
One honest limit and one finding we will not write up. The limit is that our testing is desktop-based, so we cover browser-based visits and not your native mobile app, and the report says plainly which findings carry across and which stop at the browser. The finding we will not write up is the camera permission prompt. That dialog belongs to the browser rather than to your code, and the criteria it touches except what the browser draws, so billing it to you as a defect would be dishonest. It is still a real gate for the patient, so we record where it stalled a journey and leave it out of your fix list.
What It Costs
Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.
Worth Reading Next
Related on this site
Guides, checklists, tools, and terms that go with this service.