Medicaid's Accessibility Crisis: When Policy Changes Reach No One

Oregon is racing against a federal September deadline to notify roughly 600,000 Oregon Health Plan members about new work requirements that could strip their coverage. State officials estimate up to 200,000 people could lose insurance altogether. And according to reporting from Disability Scoop (opens in new window), many of them won't see it coming.

This isn't primarily a Medicaid policy story. It's an accessibility and communication failure — one with life-altering consequences for disabled people and low-income adults who depend on this coverage. The barriers aren't just bureaucratic. They're structural, layered, and in many cases, predictable. Understanding why this breakdown happened — and what it would take to fix it — matters for every government agency that delivers essential services to people who have no margin for error.

The Comprehension Gap Is the Core Problem

Research published earlier this year found that approximately 1 in 9 Medicaid enrollees surveyed during the pandemic reported they didn't have Medicaid — even though they did. Some believed they were uninsured. Others named different coverage entirely. Georgetown University's Leo Cuello, a research professor at the Center for Children and Families, points to a structural cause: states deliberately brand their Medicaid programs under different names to reduce stigma and simplify enrollment.

In Oregon, it's the Oregon Health Plan. In Washington, Apple Health. In Connecticut, HUSKY Health. Then there's another layer: most enrollees receive benefits through managed care organizations — coordinated care organizations in Oregon — and carry insurance cards bearing names like CareOregon, Trillium, or PacificSource. As Cuello puts it: "Someone could be told they have Medicaid, the Oregon Health Plan or coverage through a CCO, without realizing those are all connected."

This is the comprehension gap that agencies must bridge before any policy change notification can be effective. When the underlying system is opaque to the people it serves, new requirements land in a vacuum.

What Accessible Government Communication Actually Requires

The ADA's Title II requirements (opens in new window) mandate that public entities ensure their programs and services are accessible to people with disabilities — and that includes the communications that govern access to those programs. The DOJ's updated Title II web accessibility rule (opens in new window) extended those obligations explicitly to digital content, requiring conformance with WCAG 2.1 Level AA (opens in new window) for state and local government websites.

But technical WCAG conformance is necessary, not sufficient. Consider what Shannon Hughes, a 45-year-old Oregon Health Plan member quoted in the Disability Scoop piece, described: spending hours on the phone submitting documents to reverse a coverage denial caused by the state incorrectly counting her income. She speaks English, has internet access, and was actively trying. She still nearly lost coverage.

"It's really hard to figure out, even if you're trying your best and you speak English and you have good internet," she said. "Let alone so many people that aren't even in that situation."

That observation maps directly to what WCAG 2.1 Success Criterion 3.1.5 (Reading Level) (opens in new window) addresses — content should not require more advanced reading ability than lower secondary education level without providing supplemental aids. Government eligibility notices routinely fail this standard. They're written for administrators, not enrollees.

| WCAG Criterion | Requirement | Application to Medicaid Notices | Compliance Risk | |---|---|---|---| | 3.1.5 Reading Level | Content readable at lower secondary level or supplemental aids provided | Eligibility notices use regulatory language inaccessible to many enrollees | Medium — often overlooked in audits | | 1.4.3 Contrast (Minimum) | 4.5:1 contrast ratio for normal text | PDF notices with light gray text on white backgrounds common in government forms | High — frequently cited in audits | | 1.3.1 Info and Relationships | Structure conveyed through markup, not just presentation | Complex eligibility tables in PDFs lack semantic structure for screen readers | High — affects blind and low-vision users | | 2.4.6 Headings and Labels | Descriptive headings and labels | Multi-page notices often lack navigable heading structure | Medium | | 3.3.2 Labels or Instructions | Clear instructions for input fields | Online renewal portals frequently have unlabeled or ambiguous form fields | High — directly causes enrollment failures |

The Operational Capacity Problem States Face

From an operational standpoint, what Oregon faces is a multi-system communication challenge with a compressed timeline. The Oregon Health Authority is reportedly in a dispute with federal authorities over late and confusing guidance — which means state teams are trying to build compliant outreach materials without clear parameters for what they're communicating.

This is where organizational capacity becomes the binding constraint. Producing accessible notices at scale — across multiple languages, reading levels, formats (print, digital, audio), and delivery channels — requires systems and workflows that most state Medicaid agencies haven't built. It's not a question of intent. It's infrastructure.

The pattern connects to what our research on organizational capacity building consistently shows: agencies often commit to accessibility outcomes without building the internal processes to sustain them. A notice that's WCAG-conformant as a PDF but delivered only via a portal that screen reader users can't navigate solves nothing. Accessibility has to be end-to-end.

For state agencies facing similar communication challenges right now, the operational questions worth asking are concrete:

• What formats are notices delivered in? Plain-text email, accessible PDF, and web-based versions should all be available — not just one.
• What reading level are notices written at? Tools like the Flesch-Kincaid Grade Level test take minutes to run. Notices targeting Medicaid enrollees should target Grade 6–8.
• What languages are covered? Oregon's LEP population is substantial. Federal requirements under Executive Order 13166 (opens in new window) require meaningful access for limited English proficient individuals.
• What's the phone and in-person fallback? For enrollees who can't navigate digital systems — including many people with cognitive, sensory, or physical disabilities — the phone channel has to actually work.

The Stakes Are Specifically High for Disabled Enrollees

The new requirements under the One Big Beautiful Bill Act largely apply to low-income adults who gained Medicaid eligibility through ACA expansion. Many people with disabilities will qualify for exemptions — but only if they know to claim them, understand the process, and can navigate the verification system.

Dr. Daniel Nelson, a primary care physician and researcher at Oregon Health & Science University, describes the systemic confusion clearly: "Medicaid's structure is confusing even for people who are experts. It becomes extraordinarily challenging for people to understand exactly what coverage they've got."

For someone with a cognitive disability, a communication disorder, or limited literacy, that confusion isn't just frustrating — it's a barrier to exercising a legal right. The ADA's equal access mandate (opens in new window) requires that government programs be accessible to people with disabilities. That obligation doesn't pause when federal policy changes create administrative complexity.

Agencies looking to audit their own communication accessibility should start with manual testing methodology — automated tools won't catch plain-language failures, confusing form flows, or phone systems that time out before a caller with a speech disability can complete their request.

What Comes Next

Oregon's September deadline is immediate. The operational path forward for state agencies in this position isn't complicated to describe, even if it's hard to execute:

1. Audit existing notice templates against WCAG 2.1 AA and plain-language standards before sending at scale.
2. Establish a dedicated phone line with extended hold capacity and trained staff for enrollees who can't use digital channels.
3. Partner with Centers for Independent Living and disability advocacy organizations to reach enrollees who are least likely to self-navigate the system.
4. Publish exemption criteria in plain language — not buried in regulatory text — so enrollees can self-screen before contacting the agency.
5. Test the renewal portal with actual screen reader users, not just automated checkers.

Shannon Hughes said she hopes the state will tell people in advance so they can figure something out. That's a reasonable expectation. Meeting it requires treating accessible communication as infrastructure — not an afterthought to policy implementation.