Helping older volunteers use a tablet

A large share of the people keeping food pantries open are retired, and a fair number of them did not use a computer at work. They are not bad at technology. They are being asked to use tools designed by people who have never watched them try.

Almost everything that goes wrong is one of six things, and five of them are fixable in an afternoon by whoever sets up the tablet.

What actually goes wrong

1. Text is too small to read, and the person will not say so, because saying so feels like admitting something.
2. A tap lands slightly off and nothing happens, so they tap harder and faster, which registers as a double tap and does something unexpected.
3. A menu hidden behind three lines or three dots is invisible — not overlooked, genuinely not seen as a control.
4. The screen scrolls under a finger resting on it, and the thing they were reading vanishes.
5. A message appears and disappears before it can be read, so they never learn whether it worked.
6. Something goes wrong once, in public, in front of a queue — and after that they avoid the tablet entirely.

Setting up the device

• Turn the system text size up before anyone touches it. Not to the maximum — one or two steps up, then ask them to read something across the room's light.
• Turn off auto-lock, or set it to the longest option. Nothing kills confidence like a screen going black mid-task.
• Turn off automatic updates during opening hours. A dialog box appearing at 9am on a Saturday is a small disaster.
• Put a real case on it with a stand. A tablet that slides on a table is a tablet that gets tapped wrong.
• Put the one thing they need on the home screen, alone. Not in a folder. Not on page two.
• Write the wifi password on tape on the back. Every time.

How to teach it, in one sitting

Teach the single most common task, all the way through, three times. Not a tour of the features. Not what everything does. One task, three repetitions, with you sitting beside them and not touching the screen.

The third repetition is the important one, because that is where they do it without prompting and discover they can. Stop there. Come back next week for the second task.

Never take the device out of their hands to show them. The moment you do, the lesson becomes a demonstration of your competence.

Things worth saying out loud

• "You cannot break it. There is nothing on here you can delete that I cannot get back." Say this first, and mean it — make sure it is true before you say it.
• "If it does something strange, that is the software being badly made, not you."
• "There is no rush. The queue can wait thirty seconds."
• "If you get stuck, put it down and do it on paper. We will type it up later." Always have the paper fallback, and never treat using it as a failure.

What to demand from your software

You are allowed to have standards here. Any tool your pantry uses should have controls big enough to hit reliably, text you can enlarge without the layout falling apart, plain words instead of jargon, confirmation messages that stay on screen until dismissed, and no critical function hidden behind a hover or a swipe.

This is exactly why Laevo is built the way it is. It is not a coincidence and it is not an accessibility checkbox — it is the main design constraint, and features that break it do not ship.