Who Jeri Caldwell Actually Is
Jeri Caldwell is a former elementary school teacher who became widely known in tech and education circles after her story went viral around 2015. She was a blind educator working in the San Francisco Bay Area public school system who found herself unable to access the digital curriculum materials her district was rolling out. The standard PDFs, Learning Management Systems, and screen-reader-unfriendly platforms made her classroom preparation nearly impossible. Instead of filing a complaint and moving on, she wrote a detailed blog post describing exactly what was broken, tagged the relevant companies, and sent it to education technology journalists. It got picked up by TechCrunch, then The Verge, then major network news. She ended up testifying before Congress about digital accessibility in education.
Unveiling The Unstoppable Jeri Caldwell A Life Of Excellence And Perseverance
The phrase itself isn't a formal title or a published work. It's more of a tagline that grew out of the coverage of her story. People started using it as a shorthand for the broader movement she represented — the demand that educational technology actually work for disabled users, not just be legally compliant on paper. If you're looking for a downloadable guide or a specific methodology attached to her name, there isn't one. What exists is a collection of interviews, a congressional record, and a handful of case studies that reference her work as an example of effective accessibility advocacy. Here is what actually happened and why it matters beyond the headlines.
Caldwell's situation exposed a gap that still exists in most K-12 districts. Schools adopt new learning platforms based on functional demos that are never tested with assistive technology. A platform might look fine when someone is scrolling through it normally. It breaks completely when you're using JAWS or NVDA. She ran into this on a daily basis. Assignments were images with no alt text. Quizzes were built in Flash or JavaScript frameworks that screen readers couldn't navigate. PDFs were scanned documents without OCR, which means her screen reader just read them as blank pages. Her workaround was methodical. She documented every broken interface element with screenshots, screen-reader output logs, and step-by-step reproduction instructions. She didn't just say "this doesn't work." She showed exactly where it failed and what a working version would need. That level of detail is what made her case useful to engineers and policymakers alike. One thing most people miss about her story is that the problem wasn't limited to one bad vendor. It was systemic. Multiple platforms across her district had the same categories of failure — form labels missing, keyboard traps, color-dependent instructions. Fixing one didn't help because the next platform had identical issues. The practical move was to push for district-level procurement requirements that included VPAT (Voluntary Product Accessibility Template) reviews before any purchase, not after. That alone would have prevented most of the problems she faced.
Get the Full Details
The counter-intuitive part is that legal compliance alone wouldn't have solved this either. Many of these platforms technically met WCAG 2.0 AA on paper. The conformance reports checked boxes. But the actual user experience for a screen reader user was unusable. Real accessibility testing requires actual users with disabilities, not automated checkers. Automated tools catch maybe 30 to 40 percent of real-world issues. The rest shows up only when someone who actually needs the accommodation tries to use the software. Her congressional testimony in 2016 focused on exactly this gap. She argued that the Every Student Succeeds Act already had language about equal access, but there was no enforcement mechanism for digital materials. That's a nuance that got lost in most of the media coverage, which framed it as a feel-good underdog story. It was really a policy gap story. If you want to follow the trail of what came after her initial blog post, the most useful primary sources are her blog archive at jericaldwells.com (though it hasn't been actively updated in years), the GAO report on edtech accessibility from 2017, and the CASEL framework updates that referenced her testimony. There's no single definitive book or guide to download. The knowledge is scattered across those sources.
The harsh reality is that despite her advocacy, many of the same accessibility problems persist in K-12 edtech today. A 2023 audit by the Office for Civil Rights found that over half of surveyed districts still reported significant barriers for blind and low-vision students. The infrastructure hasn't caught up to the policy. Caldwell's work highlighted the problem clearly, but solving it requires sustained procurement pressure and user testing protocols that most districts simply haven't adopted. What her story demonstrates practically is that individual advocacy can force institutional attention, but structural change requires changing the incentives around purchasing decisions. That's the part that doesn't make for a good speech but is the actual lever that moves things.
