Book Appointment

Six Myths About Accessible Cancer Hospital Information

Healthcare IT

Few settings ask more of a person’s attention than a cancer centre, and few are more often explained in language built for specialists. Families arrive anxious, frequently exhausted, sometimes reading in a second language, and are handed leaflets and web pages that assume a calm, fluent, able-bodied reader. Several beliefs keep that pattern in place. This article examines six common myths about accessible cancer hospital information and sets out, precisely, why each one fails. Nothing here is clinical guidance, and no treatment is endorsed or questioned.

Myth 1: “Plain language means dumbing it down”

Plain language is a discipline, not a reduction. It means choosing the common word where one exists, putting the most important point first, and defining a technical term once at the point of need. Specialists read plain text faster, too. A consent-free admission form, a scheduling page or a description of the day-care unit gains nothing from jargon, and loses readers who are frightened, fatigued or unfamiliar with the vocabulary. Precision and clarity are compatible: the best patient pages state exactly what happens, in what order and where, and leave interpretation to the clinical team.

Myth 2: “Accessibility only matters for a small group”

Design built around an average user excludes more people than is usually acknowledged. Older readers, people with low vision, people with limited dexterity, people using older phones and people reading in a second language together form a substantial share of any hospital’s audience. More importantly, the same person can fall into several categories over a single week. A caregiver reading on a phone in a waiting room, in poor light, with a child on their lap, is temporarily in the position of someone with a disability. Features that serve the edge case, such as readable text size and clear headings, quietly serve that situation too.

Myth 3: “A good PDF counts as publishing the information”

Downloadable documents are convenient for the author and frequently hostile to the reader. Many are untagged, so screen readers cannot navigate them; many are laid out for print and become unreadable when zoomed on a phone. Where a document must exist, a plain web page carrying the same content should sit beside it, and the file should carry real headings and text alternatives. This is no abstract preference. A treatment-centre brochure that cannot be read aloud by assistive software is, for some patients, simply not available. Anyone reading our summary of how cancer hospitals typically shape individual care plans should find it on an ordinary web page, not locked in an attachment.

Myth 4: “One contact method is enough if it is staffed well”

A single channel, however well run, excludes someone. A web form defeats people who find typing difficult; a phone line defeats people who are hard of hearing or who cannot afford a long call; an in-person desk defeats someone who cannot travel. Offering two or three routes, and saying plainly what each is best for, is more reliable than perfecting one. It also reduces load on the busiest route, since people select the option that suits their situation. The principle extends to appointments and test results: patients should be able to ask for information in the format they find easiest to use, such as large print, spoken word or a simple summary sheet.

Myth 5: “Translation can wait until the English pages are finished”

Language support is often treated as a final polish. In practice, many patients and relatives depend on it from the first search. If full translation of every page is unrealistic, begin with the pages that most affect the visit: how to arrive, what to bring, who to contact, and what the process looks like. State clearly which pages are available in which languages, and how to request help for the rest. Pages such as our list of questions families often want answered after a diagnosis are most useful when they can be read in the language a relative is most comfortable using.

Myth 6: “Physical access is the building’s problem, not the website’s”

Step-free routes, accessible toilets, resting places and lifts only help if people know about them before they travel. The website is where that knowledge lives. A precise description of the accessible entrance, the nearest transport and the location of borrowable wheelchairs removes uncertainty for patients whose energy is already limited. Written directions should accompany every map, and photographs should come with text descriptions. When a patient has travelled from another city or country, such details matter even more, which is one reason pages like our discussion of accreditation when considering hospitals abroad should be paired with plain, practical arrival information.

What replaces the myths

The evidence from everyday practice points to a short list of habits: plain words at the start of every page, text that can be enlarged without breaking, a second route to every service, useful descriptions of the physical space, and honest statements about which languages are covered. Each habit costs little individually. Together they change how it feels to approach a hospital at a difficult time.

It also helps to publish a statement of intent. Web teams that build and optimise sites for others increasingly do this for their own pages; the group behind cmsGalaxy, whose services span website development and technical search work, lists its accessibility commitments openly, which gives any organisation a concrete example of tone and scope. A hospital statement can be shorter still: what has been done, what remains in progress, and how to ask for another format.

Why the myths persist

These beliefs survive because the people who hold them rarely meet the readers who are affected. A page that works for its author, tested on the author’s own screen in the author’s own office, feels finished. The reader who gave up halfway never writes to say so. Closing that gap means going looking for it: invite a handful of patients and relatives to try a real task, listen without defending the page, and treat every stumble as information about the design rather than about the person.

A closing check

If you only have time for one test, take your most visited patient page and ask three questions. Can a reader with an ordinary phone and moderate eyesight understand its first paragraph in one pass? Can the same page be used with a keyboard alone or read aloud by assistive software? Does it state, in plain terms, who to contact in a different format? Where the answer is no, the fix is almost always editorial and quick. Design for the people most easily forgotten, and the page improves for the remainder as well.