Amalia arrived at the health centre with a folded notebook and one clear question: she needed an appointment for pain that had been getting worse for weeks. At reception she was told that routine appointments were requested through the app. The app required a phone able to receive codes, an email address, and a short video call to “confirm the need.” Amalia has a basic phone; her daughter lives far away, and the neighbour who knows how to complete the process works mornings. She was not handed a written refusal. She encountered a route built as though her equipment, time, and privacy were ordinary conditions of access.
That is how many digital promises work. A service calls itself open to everyone because the screen is available, while real availability depends on unnamed resources: reliable coverage, a compatible device, credit, a remembered password, comfortable reading, hearing, a camera, private space, and help that does not turn support into dependence. A right does not disappear only when someone says “no.” It can narrow through requirements that look technical and are therefore treated as though they sit outside public responsibility.
Making the context clear#
Inclusive design is not a large-text button added after the rules have been fixed. It starts with Amalia’s question: what does a person need in order to receive care without giving up more data, money, or independence than an in-person visit requires? The comparison matters. If a receptionist can hear a situation and book an appointment, the digital route should not force someone to record video, install a heavy app, and wait for a code that may never arrive. Digitising a channel can make an agenda easier to manage; it does not permit weaker safeguards for people unable to travel that channel.
Inclusive design is not a large-text button added after the rules have been fixed.
Equivalent alternatives are not decorative detours. “You can come in person” is inadequate when the telephone list has been closed, when the person must make several journeys, or when the earliest appointments are kept for app users. Asking an older person to give a relative their password is not equivalent either: it transfers labour and exposes health information. A comparable route offers the same outcome, a reasonable wait, an understandable explanation, and similar control over personal data. It might be a staffed phone line, an appointment desk, an assisted form without video, a community point staffed by public workers, or a referral from social care. What matters is that it is not a second-class door that punishes those who need it.
What changes in practice#
An exclusion test begins with outcomes rather than intentions. A team may say that video confirmation saves time and still exclude people without cameras, with weak coverage, shared housing, or no safe place to speak in front of a screen. Testing means running real journeys. People with different phones, languages, ages, visual abilities, and caring responsibilities should try to request the same appointment and record each step: what is requested, how long it takes, what fails, what can be understood, and what happens after an error. The test needs low-coverage days, old devices, and hours when a carer cannot speak privately.
The evidence from those tests should not be used to label groups as “not digital enough.” The responsible question is not why a person failed to adapt. It is which requirement produced the barrier and who could have prevented it. Perhaps the code was sent only by SMS, video was demanded before urgency was assessed, the app used too much data, or the error message named no way forward. Identifying the mechanism makes repair possible. Blaming the person preserves the mechanism and makes the next failure look like an isolated private story.
Deciding with information#
Privacy is part of accessibility. A video call can be convenient for someone with a room of their own, good connection, and confidence on camera. It can be impossible or unsafe for someone living with a controlling partner, living in residential care, or unwilling to display their home in order to justify pain. When video becomes a universal requirement, it turns a clinical or administrative option into a condition of surveillance. Inclusive design asks for genuine consent: it explains why the channel is proposed, allows refusal without loss of place, and does not interpret refusal as lack of cooperation.
Identity and access also need to be separated. Confirming that a person is who they say they are may require reasonable steps, especially in health services. But proportionate verification does not need telephone, email, camera, and biometrics by default. The public body must justify every data request, provide safe alternatives, and delete what is not needed for the purpose. If Amalia can identify herself with a document and a conversation at the desk, requiring a live image for a routine appointment needs a stronger reason than a vendor’s convenience. Security that only works for people already included is not public security; it is silent selection.
Reviewing and adjusting#
Public responsibility does not end when a platform is bought. A provider may build the app, but the centre chooses to use it, sets its rules, and retains the duty to care. There should therefore be an identified person or team with power to change the flow, release protected appointments, and answer a complaint. “The system handles it” does not say who assessed the harm or when it will be repaired. A useful incident record keeps the obstacle, response, deadline, and agreed improvement without turning the person who complained into a behavioural file.
An accessible complaint route needs more than an automatic email. It should be available by phone, in person, and in writing; allow assistance from another person with consent; give a clear answer; and permit review without requiring someone to repeat their story to five channels. The person should learn whether the failure was technical, organisational, or a matter of judgement, and what remedy follows: a priority appointment, travel reimbursement, corrected data, a call from an identifiable number, or a lasting change to the process. Repair matters when it reduces the burden that caused exclusion, not merely when it records that someone objected.
Measuring the system means looking beyond completed requests. An app can show a high completion rate because people who abandon the route never appear in the count. It is useful to publish how many people use each channel, how many stop midway, how long each route takes, how many require assistance, and which incidents recur. Those figures should be read with patient groups, reception staff, social workers, and people who live with the barriers. Not to turn a life into a spreadsheet, but to stop the spreadsheet from hiding an inequality the desk sees every day.
Amalia’s scene supplies a simple test before any change is approved: if the connection fails, there is no camera, a code cannot be read, or privacy is unavailable, can the same care still be obtained without extra delay, cost, or exposure? If the answer is no, the solution is unfinished. The team does not need to wait until someone misses care to find that out. It can pilot the service, pause the contested requirement, and show an alternative route from the first screen.
Digital rights become real when no one must prove that they deserve a non-digital route. For the person designing or procuring the next system, the immediate action is concrete: choose an essential service, complete it without a smartphone or video, and compare the result with in-person care. Then correct the difference, assign responsibility, and test again with people who were previously left out. The promise is not that everything happens on a screen. It is that no screen quietly decides who is allowed to receive care.
