Start with a book you cannot open. Not one you decline to open — one the latch defeats you, or the print swims, or the page refuses to turn. The book is not broken. The design simply assumed a reader you are not. That gap between what a thing assumes and who actually shows up to use it is the whole subject of accessibility.
So, a plain definition. Accessibility is the quality of a product, place, or piece of content being usable by people across the widest practical range of abilities — including people who are blind or have low vision, deaf or hard of hearing, have limited mobility, or process information differently. It is not a special feature bolted on for a small group. It is a measure of how much of the intended experience survives when a reader's body or senses differ from the designer's imagined default.
The word carries a few near-synonyms that are worth untangling, because they get used interchangeably and shouldn't be. Accessibility overlaps with usability, with inclusion, and with universal design, but each term answers a different question. Getting them straight helps you judge a device, an app, or an EPUB file on its actual merits rather than its marketing.
How does accessibility differ from usability?
Usability asks whether a thing is easy and pleasant to use for the people who can already use it. Accessibility asks whether it can be used at all when someone's abilities differ from the assumed norm. A reading app can score well on usability — clean menus, quick page turns, tidy library views — and still fail on accessibility if its buttons carry no labels a screen reader can speak.
The two are related but not interchangeable. Good usability work usually assumes a typical user and smooths the path. Good accessibility work starts by dropping the assumption of a typical user entirely. That is why the two can conflict in practice: a gesture-only interface may feel streamlined to one reader and be a locked door to another, which is why the same app often needs a settings page for turning pages without using your hands at all.
A useful test: if removing a feature would only inconvenience some readers, that feature is a usability nicety. If removing it would exclude readers entirely — text-to-speech, adjustable type size, captions — it belongs to accessibility.
How does it differ from inclusion?
Inclusion is the broader value; accessibility is one of its practical instruments. Inclusion is the commitment that disabled readers, older readers, and readers outside the mainstream belong in the audience at all. Accessibility is the concrete work that makes the commitment real: labelled controls, reflowable text, audio alternatives, sensible colour contrast.
You can have inclusion without accessibility — a publisher that sincerely wants disabled readers and still ships image-only PDFs has the sentiment and not the product. You can also have accessibility without much inclusion, in the form of a compliance checklist done grudgingly. The terms differ in kind: one is a stance, the other is a set of verifiable properties.
What is universal design, then?
Universal design is the design philosophy behind the best accessibility work: build for the widest range of abilities from the start, rather than retrofitting later. The curb cut is the classic illustration. A ramp cut into a sidewalk exists for wheelchair users, and it serves people with strollers, delivery workers with carts, and travellers dragging suitcases. The same pattern runs through reading technology.
Large, adjustable type helps readers with low vision, and it also helps anyone reading in sunlight or with tired eyes. Audio narration serves blind readers and commuters alike. Spoken menus serve readers who cannot see the screen and anyone whose hands are occupied. When you read about reading with low vision on screens, you are reading about features whose benefits spill well past their original audience.
What does accessibility mean for e-readers and ebooks?
For hardware, it means the device's documented features: screen readers that speak the interface, text sizing that goes far enough to matter, high-contrast modes, physical buttons alongside touch. How far each major device goes is a fair point of comparison — our Kindle versus Kobo accessibility comparison walks through what each ecosystem documents, and our e-reader accessibility checklist turns those features into questions to ask before buying. This connects to our earlier piece, Kindle Vs Kobo Accessibility Features: What Each E-Reader Offers.
For content, accessibility lives in the file itself. A well-built EPUB carries structure — real headings, reading order, image descriptions, synchronised text and audio — that assistive technology can interpret. An image-only scan carries none of it. This is why our guidance for indie authors publishing an accessible EPUB treats the file format as the first decision, not the last. A braille display, for instance, can only render what the file actually contains as text; the mechanics are covered in our piece on reading ebooks with a braille display. For related coverage, see What Should Indie Authors Check Before Publishing An Accessible EPUB?.
Students face the stakes most directly, since course materials arrive on deadlines that do not flex. The routes to accessible textbooks exist, but they work only when the underlying files were built accessibly in the first place.
What does this mean in practice?
Our analysis is that the plain-language definition is the useful one: accessibility is whether the experience survives contact with a wider range of bodies and senses than the designer imagined. Keep three distinctions in hand when you encounter the word.
- Accessibility is a property of the thing — a device, an app, a file, a building. It can be checked, listed, and compared.
- Usability is a property of the experience for people who can already get in the door. Pleasant is not the same as open.
- Inclusion is the commitment behind the work; universal design is the method that usually serves everyone better anyway.
When a product page claims accessibility, the honest question is which specific properties back the claim — spoken interface, adjustable text, described images, alternative input. Vague uses of the word, applied to a slogan or a general attitude, mean little. Precise uses of it, tied to features you can verify in a settings menu or a file, mean a great deal. The rest of this site's accessibility coverage applies exactly that test, device by device and file by file.
What the word does not mean is finished. Standards evolve, devices gain and occasionally lose features, and publishing formats keep adding requirements. Accessibility is best read not as a badge but as a direction of travel — toward designs that assume, from the first sketch, that the reader might be anyone.
Sources: calcworkshop.com · math.libretexts.org · desmos.com
