Episode 6 of the ReDefine Digital podcast recap. What WCAG means when a real person is on the other end of the phone, and the two compliance deadlines — tracking pixels and accessibility — that healthcare marketers can no longer treat as hypothetical. It covers 2 of my Insights posts in about five minutes, in a format you can listen to instead of read.
This is an AI-generated audio recap (two synthetic hosts, Pip and Mara) of written posts by Christina Dion, produced via WordPress.com’s Posts to Podcast feature. The hosts summarize my published posts; the analysis and every claim in it come from the written pieces linked below, which remain the source of record.
Prefer audio only? The same episode:
Prefer to read? The posts covered in this episode
Transcript
Generated transcript of the AI hosts, Pip and Mara. Section headings mark where the conversation moves from one post to the next.
Pip: ReDefine Digital — where compliance stops being a checkbox and starts being a phone call you didn't expect to make.
Mara: Today we're covering work from Christina Dion across two territories: what WCAG actually means when a real person is on the other end, and the pair of legal deadlines that healthcare marketers can no longer treat as hypothetical.
Pip: Let's start with how accessibility gets personal.
When WCAG Stops Being a Requirement
Mara: The question underneath this post is simple and uncomfortable: what does it take for a compliance standard to feel real? The post traces a career arc from knowing nothing about WCAG to making it a core conviction.
Pip: The turn comes in an email from a blind man who tried to book an appointment and hit a wall. The post puts it plainly: "That phone call is where WCAG stopped being a compliance requirement and became a person."
Mara: What that means in practice is that the law eventually caught up — HHS Section 504 and Section 1557 now require WCAG conformance from organizations receiving federal financial assistance, which covers most hospitals through Medicare and Medicaid alone. Noncompliance puts the revenue itself at risk, not just a fine.
Pip: Turns out the moral case and the legal case arrived at the same address.
Mara: Those same legal stakes — and what they look like inside a real audit — are exactly where the next piece picks up.
The Two Deadlines Healthcare Can't Ignore
Mara: Healthcare marketers are sitting on two documented, non-negotiable compliance exposures, and the post on the two deadlines healthcare marketers can't negotiate names both with specificity: tracking technology on authenticated pages, and accessibility conformance timelines that have already generated litigation.
Pip: On the tracking side, the numbers are not theoretical. "Health systems have paid more than $100 million across roughly 19 settlements tied to tools like Meta Pixel and Google Analytics running on authenticated patient portal sessions. Allina Health settled for $12.5 million in 2026. Atrium Health settled for up to $1.8 million."
Mara: So the upshot is a consistent fact pattern — a third-party script loading where a patient is logged in, sending data to a vendor with no Business Associate Agreement covering it. The post walks through exactly what to check: which scripts fire on authenticated pages, whether consent mechanisms actually gate those scripts before firing, whether scheduling flows have drifted to third-party domains outside your governance, and whether every relevant vendor has a current BAA on file.
Pip: A chat widget on a behavioral health page with no documented BAA status — that's described as a narrower, more manageable problem than an undisclosed ad-tech pixel. Still needs an answer in writing, though.
Mara: On accessibility, HHS pushed the Section 504 and 1557 deadline to May 11, 2027 for organizations with fifteen or more employees. The lawsuits have not waited — Frazier v. HCA Holdings named more than 159 hospitals over inaccessible websites.
Pip: Moving the deadline does not move the defects.
Mara: Right — and the post is specific about what those defects actually look like: heading structure that skips levels, pages missing a main content landmark, icon-only buttons with no accessible name, insufficient color contrast on navigation elements, video with no caption track. None require a redesign. Most are config-level or component-level fixes.
Pip: The catch the post flags is worth sitting with — automated scanning tools only catch roughly a third to half of WCAG's success criteria. Reading order, focus behavior, real screen-reader flow needs a human tester. A clean automated scan is a floor, not a finish line.
Mara: The frame the post closes on is that compliance work shouldn't be the department that says no. The better question is how to accomplish the goal while responsibly managing the risk — an MVP, a sequenced fix, an honest inventory of what's actually running on your pages today.
Pip: One blind man's email, a hundred million dollars in settlements, and a deadline that keeps moving while the defects stay put.
Mara: The through-line is the same: know what's actually on your pages, and act before someone else makes you.
Pip: More from ReDefine Digital next time.
