An accessibility statement can help you shortlist an app, but only a real task can show whether it works for the child in front of you. Access depends on the app, the device, the child’s preferred tools and the setting in which the task happens. Make the trial collaborative: the child is the expert on what feels clear, tiring, private or frustrating.
Choose three meaningful tasks
Avoid wandering through every menu. Pick actions the child genuinely needs, such as signing in, finding an assignment, listening to instructions, creating an answer and sending it. Write them down before the trial. Success means the child can complete the task with their usual supports—not that they can endure it once while an adult takes over.
Use the same device, keyboard, switch, stylus, headphones or communication support the child will normally have. Test in the likely environment too. Captions that work in a quiet kitchen may be essential in a noisy classroom; small targets may become harder on a moving bus.
Check how information is presented
- Can text be enlarged without buttons disappearing or sentences being cut off?
- Is important meaning conveyed by words or symbols, not colour alone?
- Do videos have accurate captions, and is a transcript available when needed?
- Can spoken instructions be replayed, slowed or read as text?
- Does a screen reader announce controls in a useful order with meaningful names?
- Can distracting animation, sound or visual clutter be reduced?
Android’s official accessibility overview includes tools such as TalkBack, captions, magnification, Reading mode, Switch Access and Voice Access, although availability varies by device, version and language. App Store listings may include accessibility details, but developer claims still need hands-on confirmation.
Check how the child acts on the screen
Look at target size, spacing, timing and the number of precise gestures. Can the child use a keyboard instead of dragging? Is there enough time to respond? Can an accidental action be undone? Does the app work in landscape or portrait if the device is mounted? For speech input, test the child’s actual voice and environment rather than assuming recognition will be reliable.
If a caregiver must repeatedly tap a tiny icon, remember a hidden sequence or interpret an unexplained error, the app is shifting work onto the family. Record the barrier precisely; “the submit button disappears at 200% zoom” is more useful to a school or developer than “it is inaccessible.”
Protect autonomy during the trial
Ask before changing settings or touching the child’s device. Offer choices: “Would you like me to read the message, turn on the screen reader, or wait while you try?” Stop when fatigue or frustration makes the result unreliable. Accessibility testing should not become a performance the child must pass.
For blind and low-vision learners, EdCaptain’s one-useful-task-at-a-time guide to digital access tools can help structure practice. For social apps and games, the guide to accessible online games and group chats adds communication and safety considerations.
Share a concise access note
After the trial, capture four things: the task, what worked, the barrier and the adjustment that helped. For example: “Mina can open assignments with Voice Access; the date picker has unlabeled buttons; a teacher-supplied direct link avoids that screen.” Include device and app versions because updates may change the result.
If the app is required by school, share the note early and ask for an equivalent route while the barrier is addressed. Do not require the child to disclose more health or disability information than necessary to explain the access need.
Decide: use, adapt, replace or escalate
Keep the app if core tasks work comfortably. Adapt it if a stable device setting or alternative input solves the problem. Replace it when barriers make regular use unrealistic. Escalate to the school, developer or support team when the app is required and no equivalent route is offered.
Re-test after major updates and when the child’s tools or tasks change. Accessibility is not a one-time badge; it is the continuing fit between a person, a task and a product.
