Phones, tablets and computers can open schoolwork, books, friendships and hobbies—but an accessibility menu with dozens of settings can overwhelm a child. Start with one real task the child wants to do. Then teach the smallest set of tools that makes that task comfortable and independent.
A useful first task might be reading a message, opening a homework document, finding a favourite song or taking a photo. Success gives the child a reason to learn the gestures and shortcuts that follow.
Begin with the child’s current vision and preferences
Blind and low-vision users do not all use technology in the same way. Some enlarge the entire screen. Some change text size, spacing, colours and contrast. Some listen through a screen reader, use a refreshable braille display, or switch between visual, speech and braille access depending on the task. The W3C describes all of these as ordinary access patterns.
Ask what feels tiring, slow or confusing. Do not assume a child who can see a screen should always read it visually. Equally, do not cover a useful screen and insist on speech alone. A vision specialist or assistive-technology teacher can help evaluate efficiency across longer tasks.
Use a four-step teaching ladder
- Make the display comfortable. Try text size, zoom, brightness, dark or light themes, bold text, pointer size and reduced clutter. Change one setting at a time and test it in a real app.
- Add spoken access. Read-aloud features may speak selected text; a full screen reader announces controls and supports navigation without sight. These are different tools. Practise moving by headings, links or buttons rather than swiping through every item.
- Teach a reliable route. Choose two or three gestures or keyboard shortcuts for home, back, search and help. The child should know how to stop speech, undo an accidental action and return to a known place.
- Build independence. Let the child open the task, solve small problems and decide when to ask. An adult can describe options without taking the device away.
Practise recovery, not just perfect performance
Technology fails. An app may update, focus may jump, or magnification may leave only a small part of the screen visible. Practise phrases and actions such as “I lost focus,” “I need the heading list,” “I’m going back to the home screen,” and “This file is not accessible.” These are access skills, not signs of failure.
Keep a one-page cheat sheet in the child’s preferred format. It can list a few gestures, shortcuts and the name of the setting that worked. Avoid storing passwords on that sheet. Older children should learn basic privacy: use a screen curtain when appropriate, wear headphones for personal information, lock the device and check before granting camera or microphone permissions.
Check the content, not only the device
A perfectly configured screen reader cannot repair every inaccessible worksheet. Images need meaningful descriptions, headings need correct structure and controls need clear labels. Low-vision users also need layouts that remain readable when enlarged. If a school file becomes cropped, scrambled or silent, report the barrier and request an accessible version rather than blaming the child’s skill.
UNICEF’s work on accessible digital textbooks shows why content should offer multiple ways to engage, not a single fixed presentation. Our school planning guide includes timely accessible materials and assistive-technology teaching. The low-vision assessment guide explains how functional observations can inform access decisions, while assistive technology for learning differences offers a useful trial-and-review approach.
A calm 15-minute practice
Pick one outcome: “Send Grandma a voice message.” Let the child do the parts they know. Demonstrate only the next missing step, then reset and try once more. End by asking, “What made that easier?” Save the answer as a setting or shortcut the child can use again.
The best tool is not the most advanced one. It is the one the child can choose, explain and use to do something that matters.
Let the child teach it back
Once a tool works, ask the child to show a trusted adult how they use it. Teaching back reveals whether the steps are memorable and gives the child useful language for school. Try the same task on a second device only after the first route is secure. Keep the goal portable: the child should understand that “screen reader,” “magnification” and “text size” are functions, even when different brands use different gestures or names. Review settings after updates because defaults can change. If an app remains inaccessible, document the exact control or screen that fails and request an alternative rather than adding endless practice.
