Why portal walkthroughs leave patients behind
Most patient portal tutorial videos are screen recordings with a voice on top. The voice says “tap here, then here, and you're in.” The picture does the real teaching: which button, where it sits, what the pop-up says. A patient who can't see the screen gets almost nothing they can act on.
That gap lands on the people these videos are meant to help. The American Foundation for the Blind's healthcare fact sheet reports that in its Barriers to Digital Inclusion survey, 79% of blind and low vision respondents had problems with telehealth websites and 72% with telehealth apps, at least some of the time. The fact sheet doesn't give the survey year, so read it as a signal, not a current rate.
Watch one of your own walkthroughs with your eyes closed. These are the gaps you'll likely hear:
- “Tap here” and “click this.” The narration points at something only the picture shows.
- Silent cursor moves. The pointer travels to a menu and the narrator says nothing.
- Pop-ups and permission prompts. “Allow camera access?” appears and gets dismissed without being read aloud.
- Typed text. A date of birth or visit code shows up in a field but is never spoken.
- Error and loading screens. The demo worked, so the narrator skips what a patient sees when it doesn't.
Caption problems specific to screen demos
Auto-captions add a second layer of trouble. YouTube Help tells creators to always review automatic captions and fix what was mistranscribed, and notes that mispronunciations, accents, dialects and background noise can throw them off. Screen demos have their own weak spots:
- Button labels. Caption them as they appear on screen, with the same capitalization: “Join Video Visit,” not “join this it.”
- App and product names. Brand names are the words auto-captions guess at most often.
- Spelled-out codes. “Enter A-7-K” can come out as a word. Check every character.
- On-screen error messages. If the narrator reads one, caption it word for word.
- Speaker names. When a staff member and a “patient” role-play, label each line (“Nurse:” and “Patient:”) so a deaf viewer knows who is talking.
What Section 504 asks of these videos
HHS's updated Section 504 rule adopts WCAG 2.1 AA for the web content and mobile apps of health centers and other HHS-funded recipients. For recorded walkthroughs, two success criteria do most of the work:
- Captions, 1.2.2 (Level A). Prerecorded video with audio needs accurate captions. Auto-captions you haven't checked rarely get button names and codes right. See Section 504 video requirements for health centers.
- Audio description, 1.2.5 (Level AA). When the picture shows something the soundtrack doesn't, like which button to tap, that information has to reach a viewer who can't see it. See when audio description is required.
The rule reaches past your website. The regulation's text at 45 CFR 84.84 covers mobile apps a recipient provides or makes available, including through contractual or licensing arrangements. A vendor-built patient app you send patients to is part of the picture, and so are the videos that teach it.
HHS's 2026 interim final rule set the compliance dates at May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for those with fewer. Use the deadline checker to confirm yours.
This is a plain-language reading of the rule, not legal advice. Ask your counsel about your own situation.
Which of your walkthroughs are in scope
Not every tutorial on your channel carries the same weight. Sort them before you start fixing, so the videos patients actually use come first.
| Where the video lives | How the rule likely treats it | What to do |
|---|---|---|
| Embedded on a current page of your website, such as a “Getting started with the portal” page | In scope | Fix captions and description first |
| On YouTube, uploaded before your compliance date, not embedded anywhere current | Probably exempt (unclear) | Fix if it's still in use or someone asks |
| On YouTube, uploaded after your compliance date | In scope | Caption and describe before you publish |
| Any video a patient asks for in an accessible format | Has to be made accessible either way | Turn it around quickly |
Old doesn't mean archived. The archived content exception applies only when all four conditions hold: the video was made before the deadline, it's kept only for reference, it hasn't changed since, and it sits in an area clearly labeled as an archive. A two-year-old tutorial that patients still use to log in isn't kept for reference. The archived video exception guide walks through each condition.
Requests cover everything, old or new. Put a clear way to ask on the page where your tutorials live. The accessibility request form template gives you a starting point.
Write the description into the script
The cheapest audio description is the one you never have to add. When the narration names every action, location and prompt, the soundtrack carries the steps and the picture only confirms them. That often closes the gap 1.2.5 is about, though you still need to check each finished video. These rules work for describing on-screen steps in video of any kind:
- Name the button exactly as it reads on screen.
- Say where it is: “bottom right,” “at the top, under your name.”
- Add color or icon when it helps: “the green Join button,” “the paper-airplane icon.” Low vision viewers benefit too.
- Read every prompt aloud, and say what to choose: “A box asks to use your camera. Tap Allow.”
- Say what the patient will see next, so they know the step worked.
- Spell codes and read numbers in the same groups shown on screen.
- Never move the cursor in silence. Pause the recording if you need time.
For example, here is one step from a how to join a telehealth visit video, before and after.
Before: “Tap here, then here, and you're in.” After: “On the home screen, tap Appointments at the bottom of the screen. Find today's visit and tap the green Join Video Visit button. A box asks to use your camera and microphone. Tap Allow. You'll see yourself on screen and a message that says your provider will join soon.”
If you're not sure whether a finished video still has steps that only the picture shows, run it through the check below.
A routine a team of one can keep
- 1
Script first
Write the narration using the rules above before you record. Keep it in a shared document. It becomes your caption source later.
- 2
Record one task per video
Join a video visit. Message your care team. Check in on the app. Short, single-task videos are faster to fix and re-record.
- 3
Correct captions in the YouTube caption editor
In YouTube Studio, open the video's Subtitles page and edit the automatic track. YouTube Help says editing auto-generated captions creates a new caption track with your revisions, and you change timing with the two timestamp boxes next to each line. Paste from your script where it helps, then check button names, codes and speaker labels. The full walkthrough is in how to add captions to YouTube videos.
- 4
Run a blindfold test
Give a colleague a phone with a test account. Have them close their eyes, play the video and follow along. Every place they stall is a missing description. Fix it in the narration if you can. If you can't, add description using how to add audio description to YouTube.
- 5
Re-record when the portal changes
A renamed button breaks the narration and the captions at once. After each portal or app update, rewatch your tutorials. Add a “last checked” date to each video's description so you know where you stand.
Videos made by your portal or telehealth vendor
Your portal or telehealth vendor may offer ready-made tutorials. Embedding them doesn't shift the responsibility. Under 45 CFR 84.85, the exception for third-party content doesn't apply when the third party posts because of a contractual, licensing or other arrangement with you. Before you embed a vendor video, ask:
- Do the videos have checked captions, not auto-captions alone?
- Does the narration name every button and prompt, or is there a version with audio description?
- Will you update the videos when the interface changes, and tell us when you do?
- Can we get the caption files to post on our own channel? (The SRT file guide explains the format.)
- Does the app itself meet WCAG 2.1 AA? A good video can't fix an app a patient can't use.
Get the answers in writing, and in the contract when you can.
Free checks to run this week
Start with what you already have. Scan your channel with your work email to see which videos are in scope, probably exempt (unclear) or already OK. Run the website video check on your portal help pages. Then put your most-watched telehealth setup video through the audio description check.
Sources
- Cornell LII (45 CFR 84.84)
- Cornell LII (45 CFR 84.85)
- Federal Register / GovInfo (HHS OCR interim final rule, 2026)
- YouTube Help
- YouTube Help
- American Foundation for the Blind
This is a reading of the rules, not legal advice. Something out of date? Tell us and we'll fix it.