Digital Inclusion in Practice: Completion, Understanding, Control and Recovery
Service completeness

Opening an app is only an entry point. Inclusion depends on whether people can finish payment, registration, consent and help-seeking without losing control.

Age inclusion should be assessed through a complete task; one enlarged screen does not prove that the service works.

ONE TASK, MANY BARRIERS

Registration, payment or identity checks can fail at any step

Code countdowns, app switching, jargon, preselected options, face-recognition failure and hidden human support can each stop a user near the end. Delegation also creates risk when permission, receipts and withdrawal are unclear.

DESIGN FOR FOUR OUTCOMES

Completion, comprehension, control and recovery

  1. 01

    Complete: frequent paths are short and do not rely on precise gestures.

  2. 02

    Understand: price, consequences and next steps use everyday language.

  3. 03

    Control: permission is limited by task and time, visible and revocable.

  4. 04

    Recover: errors, timeouts, payment failure and identity failure lead to continuation, cancellation or a person.

MEASURE RESULTS

Measure completion and recovery

Useful measures include independent completion, first-attempt completion, error recovery, time to human help and involuntary abandonment. Results should be segmented by task complexity, digital experience, physical ability and environment; an average satisfaction score can hide those facing the greatest barriers.

Service principle

An inclusive service lets people with different abilities complete necessary tasks, retain decisions and reach human support without losing context.

A ROLE FOR AI

Use AI for explanation and handover; leave high-risk decisions to the user

AI can restate complex instructions, identify missing material and carry a summary into human support. Payment, consent, health and personal-data decisions must still show the real amount, consequence and status. When understanding fails, a person should take over with the existing context instead of asking the user to start again.

BEIIU LOOKS FOR TASK COMPLETION

BEIIU asks whether a person can complete registration, payment, consent and help-seeking independently—not whether an interface carries an “elder mode” badge. If a crucial step still requires a relative to take over, the service has not crossed the capability gap.

Sources and methodology