You don't need every attendee holding a smartphone. Church translation for older members works best when the translated audio goes out over a radio transmitter or your existing hearing-assist loop, so someone can slip on a simple headset and listen in their native language — no app, no QR code, no account. As of a Pew Research Center survey conducted Feb. 5–June 18, 2025, 78% of adults 65 and older own a smartphone, the lowest of any age group (Pew Research Center, Jan. 8, 2026). Plan for the ones who don't.
Here's the short checklist this post walks through:
- Send the audio over RF, not just an app — feed the operator's headphone-out into a radio transmitter.
- Reuse the hearing-assist loop you already have — those receivers are half the battle.
- Hand out simple headsets at the door, pre-tuned to the right channel.
- Label channels by language, not by frequency numbers nobody remembers.
- Teach two ushers, not the whole congregation, to help newcomers.
- Never drop a word — the audio should keep every sentence, even when it falls behind.
Why won't older members just use the app?
Because the phone in their pocket may not be a smartphone, and if it is, they may not use it the way younger folks do. That same Pew data shows 90% of adults 50 to 64 own a smartphone, but ownership drops to 78% at 65 and older (Pew Research Center, Jan. 8, 2026). And only 14% of adults 65 and up say they use the internet "almost constantly," compared with 63% of those 18 to 29 (McKnight's Senior Living, Jan. 21, 2026).
So when you ask a 78-year-old visitor to scan a QR code, download an app, grant permissions, and pick a language — before the opening hymn — you've built a wall, not a door. A headset already tuned to "Portuguese" asks nothing of them but to put it on.
What does a no-QR-code setup actually look like?
Simpler than you'd think. The translated audio has to travel from the operator to the listener somehow, and radio is the friendliest path for anyone who won't touch a screen.
The RF path in plain terms
You take the operator's headphone-out — the translated voice in a given language — and feed it into a radio transmitter. Listeners hold a small receiver and a headset, turn it to the right channel, and hear the message. That's it. This is exactly why an RF-first approach matters: the older member is served without ever meeting a QR code.
You may already own half of it
If your sanctuary has a hearing-assist loop or an FM/infrared assistive-listening system, you already have receivers and headsets in a drawer somewhere. Point a translation channel at that same system and you've extended it — no new hardware for the listener.
Do we already have the receivers we need?
Quite possibly. Assistive-listening receivers you bought for hearing loss double as translation receivers, and the need for them is real. About one in three people in the U.S. between 65 and 74 has hearing loss, and nearly half of those older than 75 have difficulty hearing (NIDCD/NIH).
And many who could use help aren't using hearing aids — a cohort study found only 29.2% of older adults with hearing loss used them (JAMA Network study via NCBI/PMC). Translated audio piped straight into a headset at a comfortable volume serves both needs at once: the person who needs it louder and the person who needs it in Portuguese are often the same person.
Are churches required to provide assistive listening?
Usually not federally, but check your state. Places of worship are commonly exempted under the ADA, though that depends on activities, funding sources, and state or local building codes (Center for Hearing Access, Feb. 19, 2024).
Two states are the notable exceptions. Most places of worship aren't required to comply with ADA standards except in California and Texas, where the California Building Code and the Architectural Barriers Act in Texas require religious facilities to provide assistive listening devices (TrippComm, Dec. 10, 2025). Where ADA standards do apply, venues with 50 or fewer seats must provide at least 2 receivers, and 51–200 seats must provide more. Even where you're exempt, doing it anyway is simply good ministry.
How do we make the headset side foolproof?
The goal is zero decisions at the door. A person walks in, someone hands them a headset, and it just works.
- Pre-tune the receivers before the service so no one hunts for a frequency.
- Label by language, so channel one says "Português" on the sticker, not "Ch. 1 / 72.1 MHz."
- Station two ushers near the entrance who know how to hand off a headset and adjust volume. You don't need the whole congregation trained — just two friendly faces.
- Have spare batteries and a wipe-down cloth, because reused headsets and long services both happen.
Grandma doesn't want a tutorial. She wants to hear the sermon. Give her the headset, point to her seat, and let the message do the rest.
Why does "nothing gets skipped" matter for older listeners?
Because a summary isn't the sermon. When translated playback falls behind the live speaker, some systems catch up by skipping ahead. That means the listener loses a sentence — and the listener most likely to be relying on the headset is often the one least able to fill the gap from lip-reading or context.
The approach behind Jesus Speaks is different: when the audio runs behind, it speeds up slightly rather than dropping content, so every word is spoken. That's a technical choice with a pastoral heart underneath it. The person in the back pew with the headset hears the whole message, not the highlights. For older members who came specifically to hear the Word preached, that faithfulness is the entire point.
A word of encouragement before you build this
Don't let the tech talk intimidate you. You're not wiring a data center; you're making sure the widow in the third row and the visiting family from Braga hear the good news in words they understand. Start with what you own — the hearing loop, a couple of headsets, one operator — and grow from there. The kingdom has always made room for the person who can't read the fine print.
If your ministry wants translated audio that reaches the members who'll never scan a code, you can subscribe to set up real-time translation built for a service like yours.