Accessibility

Designing for every patient: accessibility at the bedside

On a hospital ward, disability and sensory impairment are not edge cases — they are close to the median patient. That single fact should reorder how we design the bedside screen: captions, assistive audio, large high-contrast type, and remote-first navigation are not features bolted onto a finished product. They are the product.

Published July 15, 2026 by TVshuru Health · Freshness checked July 15, 2026

Most consumer software is designed for an imagined "average user": someone with sharp vision, unimpaired hearing, steady hands, and a working memory that can hold a menu structure. Hospitals do not admit that person very often. The people in the beds are, by the nature of illness and age, more likely than the general population to have limited sight, reduced hearing, tremor or weakness, pain, fatigue, and clouded attention — frequently several at once. If a bedside platform is built for the average user, it will work beautifully in the demo and fail the patient who needs it most.

The good news is that designing for the range of real patients is not a matter of goodwill or guesswork. There is a clear picture of how common disability and sensory loss are on a ward, a legal framework that sets a floor, and a growing body of research on what actually helps older and impaired people adopt digital health tools. Put together, they point to the same conclusion: accessibility is the whole design, not a compliance appendix.

On a hospital ward, disability is the norm

Start with prevalence. According to the CDC, more than 1 in 4 US adults reports a disability, and among people aged 65 and older that figure rises to roughly 2 in 5.¹ Because inpatients skew markedly older and sicker than the general public, the share of patients on a typical ward living with a mobility, cognitive, hearing, or vision limitation is higher still. The "average user" the industry designs for is, statistically, a minority in the hospital bed.

Hearing loss illustrates the point sharply. Disabling hearing loss affects about 22% of adults aged 65 to 74 and 55% of those aged 75 and older.² On a geriatric or medical ward, that means an audio-only interface — a video that speaks its instructions, a chime that signals a request was received — will simply not land for a large fraction of patients. Vision changes track age in the same way, which is why small, low-contrast text set in a designer's favorite thin typeface is not a stylistic choice on a hospital screen; it is a barrier that quietly locks people out of their own care information.

The sensory ward: captions, assistive audio, and readable type

Once you accept that hearing and vision loss are common, the design consequences are concrete rather than abstract. Every piece of video or spoken content needs synchronized captions, so a patient with hearing loss can follow the same education their nurse selected for them, and guided on-screen education has been shown to improve patients' comprehension of their condition compared with printed handouts.⁸ Audio needs to be more than background: clear narration, adjustable volume, and — where possible — an assistive-listening path that a patient can route to their own hearing aids or headphones. Text needs to default to a large size with strong contrast, and it must scale up further on demand without breaking the layout, because a comfortable reading size for a 40-year-old designer is not a comfortable reading size for a 78-year-old patient without their reading glasses.

These are not exotic requirements. They are the same accommodations the law already expects of health-care communication. The Americans with Disabilities Act's effective-communication rule requires health-care providers to furnish auxiliary aids and services — captioning, large print, and screen-reader-compatible content among them — so that communication with people who have disabilities is as effective as communication with everyone else.³ A bedside interface that carries care instructions, consent information, and daily plans is squarely inside that obligation. Building captions and readable type in from the start is not gold-plating; it is how the platform meets a standard the hospital is already held to.

The legal floor — and why it is only a floor

For the technology itself, the relevant benchmark is Section 508, which requires that information technology provide access comparable to that available to people without disabilities, and which adopts the WCAG 2.0 AA success criteria as its technical standard.⁴ WCAG 2.0 AA is a practical, testable checklist: sufficient color contrast, text alternatives for non-text content, captions for media, keyboard-or-remote operability, predictable navigation, and content that does not depend on a single sense to be understood. For a bedside platform, treating WCAG 2.0 AA as the design baseline turns "accessibility" from a vague aspiration into a set of pass/fail criteria a team can verify.

But a floor is not a ceiling. Meeting WCAG on a color-contrast checker does not guarantee that a frightened, medicated, exhausted patient can actually navigate the thing. Real accessibility at the bedside also means reducing the number of steps to reach anything important, using plain language rather than clinical jargon, keeping the layout predictable so muscle memory can form, and never hiding a critical action behind a gesture that a patient with a tremor cannot perform reliably. Underlying all of it, research on engaging hospitalized patients finds that giving them clear access to information about their own care is what empowers them to participate.⁹ Compliance is the entry ticket. Usability under the specific stress of being a hospital patient is the actual goal.

Remote-first — and a phone in the patient's own hand

The most important accessibility decision in a bedside platform is often the input method. A television across the room cannot be a touchscreen, so the primary control is a physical remote. That constraint is a gift if you take it seriously: a small number of large, well-labeled, tactile buttons, with focus that is always visibly where the patient left it, is one of the most accessible interfaces there is — no fine motor precision, no hunting for a moving cursor, no small tap targets. Designing remote-first, rather than porting a touch app onto a TV, is what makes the screen usable for patients with limited dexterity or vision.

For anything that benefits from a personal, private, familiar device, the answer is to hand off to the patient's own phone. A QR code on the screen lets a patient move a private action — reading their information, adjusting a setting, making a video call — onto the device they already know how to operate, with their own accessibility settings (their text size, their VoiceOver or TalkBack, their captions) already switched on. This matters because the evidence on older-adult adoption of digital health is consistent: uptake hinges on simple design, clear instructions, on-hand support, family involvement, and a provider's endorsement, not on novelty.⁵ A phone handoff engages three of those levers at once — the familiar device, the family member who can help, and the personal accessibility settings the patient has already tuned.

Family involvement deserves particular emphasis, because it is both an accessibility strategy and a comfort one. In a study of older inpatients, video calls reduced anxiety and fear of death compared with telephone calls, and about three-quarters of participants chose video when offered.⁶ A relative on a video call is not only company; they are often the person who reads the screen aloud, repeats the nurse's instructions, and helps the patient press the right button. An accessible bedside platform makes that help easy to summon.

Cognitive accessibility counts too

Accessibility is not only about the senses. Many older inpatients arrive with, or develop, confusion and disorientation, and a cluttered or unpredictable interface makes that worse. The Hospital Elder Life Program — a structured set of low-tech interventions built around reorientation, cognitive engagement, and simple daily routines — has been shown to reduce the odds of delirium by roughly half across a dozen studies.⁷ The mechanism is orientation and gentle engagement, exactly the kind of thing a calm bedside screen can support: a clear display of the date, where the patient is, what is happening today, and who is on the care team, presented simply and consistently. Designing for cognitive load — fewer choices per screen, generous labels, no time-pressured interactions — is as much a part of accessibility as contrast ratios, and it serves the same population.

The honest caveat: designed in, or it excludes

Here is the caveat that should sit at the center of any accessibility claim, not in a footnote. Technology can just as easily exclude as include, and it does so precisely when it is designed for the average user and then "made accessible" afterward. Bolting captions onto a video that was scripted to be understood by ear, enlarging text in a layout that was never built to reflow, or adding a screen-reader label to a control that requires a precise gesture — these are patches that look like accessibility on a checklist and fail the patient in the bed. Accessibility has to be designed in from the very start, as a first constraint on the design, or the finished product will quietly leave out the people the hospital is most responsible for.

None of this replaces the nurse, the physician, or the certified nurse call system, and none of it makes the platform a medical device. TVshuru Health is built to complement clinical care, not to substitute for it. What accessible design does is make sure that the calm, capable bedside interface a hospital offers is one that every patient — not just the imagined average one — can actually see, hear, reach, and understand. On a ward where disability is the norm, that is not a nice-to-have. It is the point.