A Network Signal Is Not Digital Inclusion: Africa Must Measure What People Can Actually Do

An African digital future cannot be measured by towers and SIM cards alone. A community-focused argument for affordability, skills, useful services and reliable access.

ITBank original Community Voices editorial perspective prepared with AI assistance and grounded in attributed public evidence. The author is the ITBank Editorial desk, not a claimed guest contributor, interviewee or first-person witness. Draft pending editorial approval.

There is a habit in the technology industry that deserves to be challenged. A network operator installs new infrastructure, a government celebrates more subscriptions, and the headline declares that another community has entered the digital age. But a person can live beneath a mobile tower and remain effectively excluded from the digital economy.

That distinction is not a minor statistical argument. It is about the difference between the ability to receive a signal and the freedom to make something useful happen with it.

The International Telecommunication Union's Facts and Figures 2025 estimates that only about 36% of people in its Africa region used the internet that year. The urban and rural figures were markedly different: roughly 55% and 21% respectively. The GSMA's 2026 Africa report likewise highlights a large population living within mobile broadband coverage but not using mobile internet. Different institutions measure different populations and indicators, but their message is clear: installing infrastructure does not finish the job.

An ordinary day is a better test than a coverage map

Imagine a learner trying to watch a lesson, a market seller confirming a payment or a parent submitting a school application. Each task has its own barriers. The phone may be old. Data may run out before a form is completed. The site might be designed for a desktop computer. An automated password reset may require access to a second phone number. Electricity might disappear halfway through a transaction.

This is a hypothetical illustration of common design risks, not a claim that ITBank interviewed those specific people. Yet each obstacle is one a product team can test.

A useful definition of inclusion should ask whether people can complete important tasks safely, affordably and without assistance they cannot reliably obtain.

The four costs of being connected

There is the price of an appropriate device; the price of enough data to finish a task; the time spent working around interruptions; and the risk of mistakes or fraud. Families budget for all four, whether or not a technology company's marketing department counts them.

An 'affordable' data bundle may still be inadequate if the required application demands continuous video or downloads hundreds of megabytes. A free public-service portal is not really free to the person who travels to a better-connected location to use it.

We should not use a single country average to describe an entire continent. Conditions in a rural district of Zambia, a neighbourhood in Accra and a commuter corridor in Cairo can differ dramatically. Good policy begins by observing those differences.

What providers could measure instead

Publish the median cost of successfully completing a typical task on a modest phone. Report how many attempts are needed before an application succeeds. Test whether a user can recover from an interrupted session without starting again. Invite people with disabilities and people who use local languages into usability studies, and pay them appropriately for their time.

A school service should measure applications completed, not merely visitors. A payments app should measure problems resolved, not only downloads. An internet provider should make performance and complaint handling as understandable as its coverage claims.

A 30-day community test

A local association, school or civic group could choose three digital tasks its members regularly attempt. With participants' informed consent, document the cost, device type, steps completed and reasons for failure. Collect no account passwords or confidential transaction details.

Present the findings to the service provider or relevant institution with specific requests: smaller pages, better error messages, accessible support or an offline alternative. Return a month later to see whether anything changed. Such a small exercise cannot stand in for a statistically representative national survey, but it can reveal concrete barriers a service team could fix.

Where responsibility sits

Governments can support competitive connectivity markets, transparent service quality and accessible public services. Providers can simplify products and be honest about total cost. Schools and community organisations can help people develop digital skills without presenting users as deficient when software is poorly designed.

The responsibility should not always be shifted onto the person least able to afford it.

Africa does not need to choose between ambitious infrastructure and everyday inclusion. It needs to demand that the first leads to the second.

The question for our community: What is one ordinary online task people around you still struggle to complete, even when they technically have an internet connection? What would make that task reliably possible?

ITBank Community Voices — editorial perspective, informed by ITU and GSMA research. This is not a first-person testimonial or a commissioned community interview.