Beyond connectivity: The apomechanic web and digital exclusion by design
By Dr Muhammad Shabbir
Digital accessibility for persons with disabilities is not charity, decoration, or technical polish. It is a condition for equal participation. But the larger failure is not limited to awareness. It lies in a persistent confusion that weakens digital policy: the belief that ‘internet access’ and ‘digital accessibility’ mean the same thing.
They do not.
A person may be connected, equipped and skilled, yet still unable to use a digital service because the service itself does not work with their body, senses, or assistive technology. This is not a failure of access in the ordinary sense. It is a failure of design, architecture, and accountability.
This distinction reflects a broader shift in thinking about digital inclusion, from mere connectivity to meaningful and usable participation, as emphasised in global frameworks such as the International Telecommunication Union’s (ITU) work on meaningful connectivity, and the rights-based obligations articulated in the United Nations Convention on the Rights of Persons with Disabilities.
This condition can be understood as apomechanic exclusion: exclusion produced by the mechanism itself.
The term comes from the Greek apo (away from, separation caused by an agent) and mechane (machine or engineered apparatus). A system is apomechanic when its own mechanism becomes the agent of exclusion. The user is present. The user is capable. The system does not fail the users. It is built to exclude them.
A three-tier model of access
The language of the digital divide has been useful, but it is too blunt for the problem before us. Digital access is not binary. It operates across at least three layers.
| Tier | Term | Core Question | Main Barrier | Main Responsibility |
|---|---|---|---|---|
| Tier 1 | Conduit Access | Is the connection available? | Infrastructure and affordability | State, market, ISPs |
| Tier 2 | Instrumental Access | Does the user have a usable device and basic skills? | Devices, assistive technology, digital literacy | Education systems, social services, market |
| Tier 3 | Interactive Access | Does the digital environment work with the user’s sensory, motor and cognitive needs? | Code, interface, content, workflow, standards compliance | Designers, developers, platform owners, procurers, regulators |
Before I proceed, let me state plainly: This article presupposes the fulfilment of Tiers 1 and 2 for persons with disabilities. It is written to isolate and name the specific, unrecognised barrier that remains after connection and basic skills are achieved.
This is not to dismiss the reality that for millions of people with disabilities globally, even Conduit and Instrumental Access are precarious or absent. The affordability of devices, the cost of data, and the availability of assistive technology training are profound, material struggles, particularly and acutely compounded in the Global South.
I acknowledge that gap with full seriousness. However, the barriers of affordability and skills are better recognised in existing policy vocabulary; the third-tier barrier remains less clearly named. The barrier we are naming today has been consistently swallowed by that vocabulary, rendered mostly invisible by it.
The compound nature of these barriers in the Global South, where a user may simultaneously face poverty, skill exclusion, and interface hostility, deserves dedicated analysis of its own. Here, my task is narrower: to name the distinct, third-tier exclusion that remains even when the first two tiers are resolved.
This layered understanding aligns with capability-based approaches to development, which emphasise not just access to resources but the real ability to use them.
Exclusion by design
The physical-world analogy is simple. A wheelchair user arrives at a building with transport, mobility equipment, and the skill to move independently. The building has only stairs. We do not blame the wheelchair. We do not prescribe confidence training. We say the building is inaccessible.
The digital equivalent is no different.
A government portal that relies on unlabeled graphics, a banking app that cannot be navigated with a screen reader, an education platform without captions, a recruitment system that traps keyboard users, or a form that times out before assistive input can be completed all produce the same result.
The user is not absent. The user is not deficient. The system is exclusionary.
The system does not fail the user. It is built to exclude them.
The illusion of digital inclusion
The confusion between access and accessibility is politically convenient.
Governments report kilometres of fibre, devices distributed and citizens trained. Companies report downloads, registrations and user growth. These indicators are easy to count and politically attractive.
But they do not answer the most important question: Can users with disabilities actually use these systems?
A blind person counted as connected may still be unable to use banking services. A deaf student may be enrolled but excluded from learning. A motor-impaired user may have access but cannot complete a transaction.
Connectivity records presence. It does not guarantee participation.
This is why the old language of the digital divide is insufficient. It makes exclusion visible only when people are offline. It struggles to describe those who are online but rejected by the system.
Where systems fail in practice
The next phase of digital accessibility must be less ceremonial and more forensic.
Institutions should stop asking only whether their platforms are accessible in a general sense. They should ask a harder question: where does our system become apomechanic?
To explain: Where does a blind user lose control? Where does a deaf user lose information? Where does a keyboard user get trapped? Where does a person with a cognitive disability face avoidable confusion? Where does the workflow break?
This requires apomechanic audits: detailed examinations of how digital systems exclude users at the point of interaction. Such audits should include technical testing, standards compliance, user testing with persons with disabilities and review of procurement and design decisions. An apomechanic audit would test whether a person with a disability can complete real tasks, not merely whether a website passes automated checks.
Accessibility cannot remain a late-stage patch. It must be built into planning, procurement, coding, testing, deployment and maintenance.
The cost of being excluded
Apomechanic systems impose costs that institutions rarely measure.
Users with disabilities spend extra time navigating barriers. They depend on family members, colleagues or strangers to complete private tasks. They lose opportunities because forms cannot be submitted, classes cannot be accessed, payments cannot be made, or applications cannot be completed.
This is not inconvenience. It is unequal citizenship.
Thus, the cost of apomechanic exclusion for persons with disabilities is emotional, economic and political. It turns independence into dependence. It converts digital rights into negotiated favours. It makes users with disabilities pay, again and again, for failures they did not create.
Misplaced responsibility
The dominant response to digital exclusion still too often focuses on the user. Train the user. Subsidise the device. Improve digital literacy. Encourage confidence.
These interventions may be useful, but they do not solve apomechanic exclusion.
No amount of training can make an unlabeled button readable. No confidence workshop can caption a lecture. No assistive technology can fully rescue a system that was never designed to work with it.
The failure lies with the people and institutions that design, buy, regulate, and operate digital systems without treating accessibility as a core obligation.
Regulating digital exclusion
Digital accessibility must be treated as a rights-based duty, especially for essential services such as government, banking, healthcare, education, telecommunications and transport.
Standards such as WCAG should be embedded in procurement rules, software development, public-sector contracts and regulatory audits. Compliance should not depend on goodwill. It should be enforceable.
Regulators should ask a direct question: Does this system work for persons with disabilities in real use?
If it does not, the system is not merely imperfect. It is exclusionary.
A digital service that cannot be used by persons with disabilities should not be celebrated as innovation. It should be treated as a governance and design failure.
Beyond access, toward accountability
We need sharper language because vague language protects weak accountability.
Internet access is not digital accessibility. A network signal is not a usable service. A digital portal is not a functioning system. A user may be connected, yet unable to act. Apomechanic exclusion is precisely this condition: presence without usability, connection without function.
The concept of apomechanic exclusion names the specific violence of being connected but blocked by the machine itself. It shifts attention from what users lack to what systems refuse to provide.
The task ahead is not only to connect the disconnected. That work remains essential. But we must also dismantle the mechanisms that exclude those already connected, skilled and ready to participate.
Until then, digital inclusion remains a promise that excludes those it claims to serve.
The views expressed in this blog are those of the author and do not necessarily reflect the views of the European Union.
