Digital Healthcare Accessibility: A Patient-Centered Care Priority

By Szabó Zoltán József | Guest contributor

I am trying to book a hospital appointment online. I know which department I need, but finding out how to make an appointment is unexpectedly difficult. I move through several menus before I can tell whether I should book online, telephone the hospital, or continue on another website.

Sometimes I find the information, only to discover that the text has been posted as an image. When I magnify it, the letters become blurred and pixelated. The information is technically there, but I cannot read it properly.

I have a visual impairment and use screen magnification and other digital accessibility tools every day. The difficulty is not a lack of computer skills. It is that the website does not always support the way I need to use it.

Digital healthcare can make scheduling, referrals, and communication faster. But faster administration is not necessarily more equitable access. We also need to ask whether patients can find information, understand it, use it, and complete the next step in their care.

What is digital healthcare accessibility?

Digital healthcare accessibility means designing websites, patient portals, scheduling tools, documents, and communications so people with disabilities can use them. The practical test is whether a patient can find a service, complete the required task, and continue to the next stage of care using their preferred access method.

For healthcare teams, that means examining the entire journey: booking, referral updates, intake, results, and follow-up. An accessible form cannot resolve a barrier that prevents patients from finding it.

Why does healthcare accessibility begin before online booking?

The patient journey starts before someone clicks “Book an appointment.” They first need to identify the appropriate service and find a reliable way to contact it.

On Hungarian hospital websites, I have repeatedly struggled to locate appointment instructions. Department details, telephone numbers, and online options may sit in different menus. With a magnified screen, I see a smaller part of the page at once, so following a complicated navigation structure takes more effort.

Text embedded in images creates another obstacle. Enlarging a low-resolution image cannot restore the clarity of its letters, and the content may be inaccessible to a screen reader. Properly structured web text can be resized, reflowed, and interpreted by assistive technology. These distinctions are addressed in the Web Content Accessibility Guidelines (WCAG) 2.2. W3C’s explanation of text reflow shows why enlarging content should not force patients to scroll back and forth to read ordinary text.

For developers of patient scheduling systems, this has a practical implication: accessibility cannot begin at the appointment form. It must extend to the route patients take to reach that form. Otherwise, someone may abandon the process before the scheduling platform records an attempted booking.

Accessible medical records: Can patients actually read their results?

Electronic medical records can spare patients an extra trip to collect their results. Yet receiving a document and being able to use it are different things.

In Hungary’s EgészségAblak healthcare app, my laboratory results appear as PDF documents. On my own phone, with the viewing setup I use, the document does not rotate with the device into a landscape view that would allow me to enlarge it comfortably. This describes my experience, not a claim that the application behaves identically on every device.

A laboratory report is not just a collection of numbers. I need to read the test names, results, units, and reference ranges in their correct relationships. When the display makes that difficult, opening the file does not amount to meaningful access.

A PDF is not inherently inaccessible. Its structure, the quality of the embedded text, the viewer, and compatibility with assistive tools all matter. Poor accessibility can make it harder to prepare questions for a clinician or understand the information discussed at a follow-up appointment.

Delivering a document is an IT outcome. Making its contents usable is part of the quality of care.

Connect digital accessibility with the in-person patient journey

Web accessibility and physical accessibility are often assessed separately. Patients experience them as parts of one journey.

I have encountered clinic calling systems where the displayed queue number is too small for me to read reliably. Information posted on consulting-room doors can also be difficult to make out. A patient might have booked successfully, arrived on time, and still struggle to know when or where to go.

Simple changes can help: larger numbers, stronger contrast, clearer directions, and audio announcements alongside visual displays. Yet an audio-only system may create a barrier for someone who is deaf or hard of hearing. Multiple communication methods matter more than assuming one format will suit everyone.

For healthcare organizations, the relevant endpoint is not simply a confirmed appointment. It is a patient who can navigate the entire process, including arrival, check-in, consultation, and follow-up.

How digital healthcare barriers affect patients differently

My own experiences illuminate only one part of the problem. A service that works with screen magnification may still be inaccessible in other ways.

Blind patients using screen readers such as NVDA, JAWS, VoiceOver, or TalkBack need controls, form fields, and error messages to be properly labeled and navigable. The W3C accessible forms tutorial provides practical guidance on labels, instructions, and feedback. A scanned report without accessible text or a calendar that works only through visual interaction may prevent them from completing a task.

For deaf and hard-of-hearing patients, an instructional video or virtual consultation is not accessible merely because it is online. Accurate captions, written alternatives, and, where appropriate to the individual, sign-language interpretation can be essential to communication.

Patients with limited dexterity or movement may understand every instruction and still be unable to activate a tiny button, perform a precise drag gesture, or finish before a short session timeout. Some use keyboards, switches, voice control, or other alternative inputs.

My wife and business partner, Alexa, has a physical disability and experiences hand tremors. Where I might struggle to locate a control visually, she may find the precision required to operate it difficult. We are both experienced technology users; the barriers are different.

Some patients with intellectual or cognitive disabilities, and some autistic patients, may benefit from predictable navigation, plain-language instructions, manageable steps, and clear error messages. The W3C’s cognitive accessibility resources address many of these design considerations.

These are examples, not fixed rules for disability categories. People with similar diagnoses may use different tools and have very different preferences. The right question is not simply “What disability does this patient have?” but “What is preventing this person from completing this task?”

Digital literacy and digital accessibility are different problems

When someone struggles with a healthcare portal, it is tempting to assume they need training. Sometimes they do. Sometimes the instructions are unclear. And sometimes the interface is unusable with their particular way of interacting with it.

In my professional work supporting people who choose medical aids and learn to use them, I often make a similar distinction. Does someone need a clearer explanation, or do they understand the task but lack a usable way to perform it?

The first problem may call for better patient education. The second calls for a change in the tool or process. Clear information cannot compensate for an inaccessible interface; an accessible interface cannot compensate for incomprehensible medical instructions.

Which accessibility standards apply to digital healthcare?

Technical standards provide an essential foundation. WCAG addresses digital accessibility, but passing an automated test alone does not establish that a patient can complete a real-world task. Standards-based checks and testing with patients answer different, complementary questions.

In the United States, Section 504 of the Rehabilitation Act is the basis for HHS digital accessibility requirements applying to covered recipients of HHS federal financial assistance. Following a one-year extension announced in May 2026, the compliance deadline for the relevant WCAG 2.1 Level AA requirements is May 11, 2027 for recipients with 15 or more employees, and May 10, 2028 for those with fewer than 15. These deadlines do not eliminate other existing duties concerning equal access and effective communication.

In England, the NHS Accessible Information Standard sets requirements for NHS and publicly funded adult social care services to identify, record, flag, share, meet, and review relevant information and communication needs related to disability, impairment, or sensory loss.

The NHS requirements make clear that this is an ongoing process.

A record stating “visually impaired” is not specific enough to tell a provider whether a patient needs large print, a screen-reader-compatible document, or another format. The patient should be asked. Crucially, recording that preference must change what happens next. If the following appointment letter arrives in the same unusable format, the record has achieved little.

In referral management, communication requirements deserve attention alongside appointment details and clinical information, with appropriate consent, privacy protections, and access controls.

Make patient communications usable, not just deliverable

Automated patient communication workflows can reduce administrative work by delivering reminders, referral updates, and patient instructions. But delivery receipts and open rates do not tell us whether an individual understood the message or could act on it.

A text message may arrive successfully, while the link inside it remains unusable. A patient may open an appointment instruction without understanding the preparation required.

The U.S. Agency for Healthcare Research and Quality recommends the teach-back method to check understanding: patients or caregivers explain, in their own words, what they have been told. It tests the clarity of the explanation, not the patient’s intelligence.

Digital services do not need to turn every message into a quiz. They do need ways for patients to indicate that something is unclear or inaccessible, and a defined route to human assistance. A patient who changes communication channels should not automatically have to restart the entire process.

What should healthcare teams measure beyond completed bookings?

Online booking rates, completed referrals, message delivery, and average processing times are useful operational metrics in healthcare reporting and analytics. But they can overlook people who never reach the booking screen or cannot finish authentication.

I would add three practical questions to the evaluation of a digital patient journey:

Can patients find the service?

Assess where people leave the process, including the steps before the booking or intake platform opens.

Can they complete the task using their own access method?

Test magnification, screen readers, alternative input devices, accessible documents, and communication preferences. Distinguish chosen assistance from assistance forced by an inaccessible system.

Can they reach the next stage of care?

When someone encounters a barrier, can they report it, switch channels, and continue without repeatedly providing the same information?

These are proposed evaluation questions, not a validated clinical measurement scale. Drop-offs have many causes; not every abandoned task represents an accessibility defect. Yet treating every failure as patient disinterest or poor digital literacy is equally misleading.

The pattern and resolution of access-related problems should be visible in the service’s quality-improvement work, not lost in a general category of incomplete interactions.

Test the complete patient journey with people with disabilities

The WHO and International Telecommunication Union’s guidance on accessible telehealth emphasizes building accessibility into service design rather than treating it as an afterthought.

Testing should therefore cover complete, realistic tasks: finding a specialist, booking an appointment, reading instructions, attending the clinic, and accessing results. Involve people with different disabilities using their own assistive technologies. Observe how they recover when something goes wrong.

The W3C likewise recommends involving users with disabilities alongside technical accessibility evaluation. One person’s experience cannot represent an entire disability group, and user testing does not replace standards-based assessment. Both are necessary.

Findings also need owners, corrective actions, and follow-up testing. Otherwise, accessibility remains a one-time project instead of part of routine healthcare quality management.

A practical digital healthcare accessibility checklist

Healthcare teams can use these questions to turn the patient journey into specific review tasks:

• Finding care: Are service descriptions, contact details, and appointment instructions easy to find and available as readable web text?
• Booking and authentication: Can patients use the process with a keyboard, screen reader, magnification, or alternative input? Can they recover from an error or timeout?
• Patient intake: Do digital patient intake forms provide clear labels, manageable steps, and understandable instructions?
• Documents and results: Is the text accessible, and are headings, reading order, and relationships between results and reference ranges preserved?
• Communication: Have patients been asked which formats and channels they can use? Does that preference change subsequent messages?
• Arrival and check-in: Do visual and audio information work together, with another way to get help when needed?
• Assistance and recovery: Can a patient report a barrier or change channels without unnecessarily restarting the process?
• Accountability: Does each accessibility issue have an owner, a corrective action, and a follow-up test?

These questions are a starting point for improvement, not a conformance audit. Review the patient access tools and connected workflows together rather than evaluating each screen in isolation.

Make accessibility part of patient-centered care

Independence does not mean never asking for help. Involving a caregiver may be a deliberate and appropriate choice. But choosing support is different from being forced to disclose private health information because a system cannot be used independently.

A digital healthcare service can be faster and more automated without becoming more accessible. Its success should also be judged by whether patients can perceive the information, understand their options, perform the task, and move through the care pathway with the greatest possible control over their decisions.

The measure of patient-centered digital healthcare is not simply how efficiently the system processes a patient. It is whether the patient can actually make it through the process.

---

Frequently asked questions about digital healthcare accessibility

Why is accessibility important in patient-centered healthcare?

Patients need to be able to find, understand, and act on information throughout their care journey. If a portal or document prevents someone from booking, preparing for a visit, or reading results, administrative efficiency alone does not provide meaningful access.

What makes online appointment scheduling accessible?

Accessible scheduling includes clear instructions, labeled controls, keyboard operation, support for assistive technology, and usable error messages. The journey to the booking form and a way to recover when something goes wrong also matter.

Are PDF medical reports always inaccessible?

No. Accessibility depends on the document’s structure, text, reading order, and compatibility with the viewer and assistive technology. For laboratory reports, patients also need to understand which result, unit, and reference range belong together.

Is an automated accessibility scan enough?

No. An automated scan can identify some technical problems, but it cannot establish whether patients can complete an entire task. Combine technical evaluation with testing by people with disabilities using their own access methods.

How can healthcare teams improve accessible patient communication?

Ask patients which formats and channels they can use, record those needs, and apply them to subsequent communications. Provide clear instructions and a way to reach human assistance when information is unclear or inaccessible.

About the author

Szabó Zoltán József is a Hungarian medical-aids specialist, patient education practitioner, and author writing about healthcare communication and accessibility. He is the co-founder and managing director of Értéksziget®, established in 2009, and the professional editor of its Knowledge Centre, which provides practical information on home care, rehabilitation, and medical aids.

He holds a higher-education qualification in institutional communications and a vocational qualification in medical-aids retail, and is a member of the Hungarian Chamber of Health Care Professionals. His professional articles have appeared in Hungarian and international publications, including WEBBeteg and All Health and Care UK. As a person with visual impairment, he also brings firsthand experience to his work on accessible patient communication, health literacy, and informed decision-making.