Language Access Shouldn’t Depend on Who’s Willing to Ask
In PublicInput’s 2024 State of Community Engagement Report, 28% of Spanish-speaking residents said they’re uncomfortable requesting an interpreter at a public meeting. When a translation option is already available instead of something they have to ask for, comfort jumps to 71%.
That’s a meaningful gap, and it points to something specific: the barrier to language access is often the act of asking, not just the supply of interpreters.
The Meeting That Gets Covered, and the Ones That Don’t
Most agencies can staff a Spanish interpreter for the meeting that draws attention: the city council or county commissioners meeting. Fewer can cover the planning commission, the parks board, the zoning board of appeals, or Tuesday’s special session on the budget.
But those are often exactly the meetings where the decisions that reshape a neighborhood get made: a rezoning, a rate increase, a road diet. A resident who doesn’t speak English fluently has just as much at stake in that meeting as in the one three weeks later that happened to have interpretation booked.
Human interpretation for every meeting, every language, and every board is expensive and hard to schedule on short notice. Most clerks are already stretched managing the meeting itself. Adding “book an interpreter for six different bodies” isn’t a realistic ask, so coverage naturally narrows to whichever meeting gets the most scrutiny.
Why Asking Doesn’t Work
Even where interpretation exists, it depends on someone raising their hand and requesting it, in person, in front of their neighbors, in a room where they may already feel like an outsider.
The data bears this out. In the same survey, residents were consistently more comfortable with language access that showed up automatically, without a request:
- 77% were comfortable with communications that were already translated
- 71% were comfortable using an online translation option
- 66% were comfortable requesting a translation
- 66% were comfortable requesting an interpreter, meaning 28% were not
Comfort drops a little more each time a resident has to take an extra step to get access that should have been there from the start. Requesting an interpreter, the most manual and most visible option on the list, is where that discomfort peaks.
Some of the hesitation is about not wanting to be singled out. Some is not knowing whether the interpreter will actually show up. Some is simply not knowing the option exists at all. Whatever the reason, if the only path to language access runs through a request, a meaningful share of residents will quietly opt out instead of asking.
What It Looks Like When Access Doesn’t Require Asking
The fix is making language access something that’s already there when a resident shows up, in whatever language they speak, however they choose to attend, rather than adding more interpreters.
That means covering more than one flagship meeting: every board, every commission, every special session, at the same standard. It means offering more than one or two languages on request: enough coverage that a resident doesn’t have to check in advance whether their language is supported. And it means making that access available across every way people actually attend, so the format someone chooses doesn’t determine whether they can follow along.
When that’s the standard, a resident doesn’t have to ask, explain, or hope someone is available. They just show up and participate, the same as anyone else.
This is the problem PublicInput built Live Meeting Interpretation to address: real-time interpretation and captions across 130+ languages, available at every meeting, in every format, without a request required.
