When I started looking closely at the learning platforms schools ask families to use, I noticed something easy to miss if it doesn’t affect you: almost all of them are built in English first.
For families who speak Spanish at home, that one fact quietly changes everything. A child might be able to follow along in class, but the parent often can’t — and a parent who can’t understand the material can’t sit beside their kid and help them with it. The language barrier becomes an opportunity barrier. And it’s invisible to the people who never have to think about it.
For me, the English-first technology trend was never abstract. My own children use the technology I’ve built, and I built it for families like the ones all around me — so that the opportunity to understand money, technology, and how to build something of your own doesn’t depend on which language gets spoken at the dinner table. I’m tired of watching the same families get left a step behind — not because their kids are any less capable but because no one built the on-ramp in a language they could use.
That language gap is what I set out to close.
It matters now more than ever because a growing number of states are starting to require students to take a personal finance course to graduate. For example, California’s Assembly Bill 2927 requires students to complete a stand-alone personal finance course to graduate high school starting with the class of 2030-31, with schools required to offer it by 2027-28. But if the lessons exist only in English, many households that need that knowledge are also the ones least able to access and reinforce it at home. A mandate built that way doesn’t close the gap. It can widen it.
I’ve spent the past three years building a bilingual K-12 learning platform, and the single most important thing I’ve learned is this: there is a world of difference between a product that has been translated and a product that is bilingual. Most edtech tools that advertise Spanish support only translate the interface — the menus, the buttons, the navigation — but the instruction itself stays in English. To a district evaluating the tool in a demo, it looks bilingual. To a parent sitting down with their child at the kitchen table, it isn’t.
This is the part I think edtech keeps getting wrong. We tend to treat language as the last step: build the English version and then add Spanish later if the budget allows. But a lesson a family can’t understand together hasn’t really been delivered — it’s just a box that got checked.
So, what does taking this seriously actually look like? Having sat on the builder’s side of these conversations, here is the concrete guidance I’d offer.
Five Questions for Edtech Vendors
When a vendor says their product “supports Spanish,” ask the following questions to differentiate true bilingual instruction from a translated menu bar:
-
Is the instructional content itself available in Spanish — for every lesson and at every grade level — or only the interface? Ask them to open a mid-unit lesson in Spanish during the demo, not the homepage.
-
Is the audio in Spanish or only the text? Many parents are stronger listeners than readers in either language. Text-only translation still excludes them.
-
Are parent-facing communications translated? Progress reports, dashboards and notification emails are how parents actually use the platform. If these features are in English, the parent is cut out of the loop no matter what the student sees.
-
Was the Spanish content written or reviewed by educators or was it machine translated? Machine translation of math word problems and financial terms produces errors that would confuse a struggling reader.
-
When new content is released, are both languages released together? If Spanish content is released a semester after the English content, Spanish-speaking families are permanently a step behind — by design.
A vendor with a truly bilingual platform will answer these questions in 30 seconds. A vendor with a translated interface will pivot to their roadmap.
Small Changes Keep Parents in the Loop
Teachers can’t rewrite their district’s software, but they can keep Spanish-speaking parents in the learning loop with the tools they already have.
-
Send the “what we’re learning this week” note home in both languages. Even if the learning platform is only in English, a two-line bilingual summary tells a parent what to ask their child about at dinner. Free translation tools are imperfect, but a two-line note reviewed by parents is achievable weekly.
-
Show parents the language toggle if one exists. Many families never discover a product’s Spanish mode because nobody walked them through it at back-to-school night. A five-minute demonstration in the fall can change a family’s entire year.
-
Assign homework with the parent in mind. When assigning homework on an English-only platform, include one question the student must explain to their parent in the family’s home language. This makes the parent a participant instead of a bystander. Plus, explaining a concept in another language is one of the best comprehension checks there is.
-
Flag the gaps upward. District procurement teams rarely hear which tools are failing bilingual families because the feedback doesn’t travel that far. A teacher noting that “the educational unit has no Spanish audio and my students’ parents can’t understand it” is exactly the evidence a district needs at renewal time.
Requirements Don’t Create Access
Taking access seriously isn’t complicated. It means treating a second language as a design requirement, not a stretch goal. It means making the platform bilingual from the first line of code, in the text and the audio, so a parent and child can move through a lesson together. It means making sure the highest value subjects — the ones tied to a student’s economic future — are the ones that exist in both languages first, not last. None of this is exotic. It’s just a decision about who you’re building for, made early enough to matter.
Discussion about this post