MarginaGet Margina
Artigos

Publicado

EPUB Accessibility: What 'Accessible' Actually Means for an Ebook

'Accessible' on an ebook listing sounds like a settled fact, but it's a specific, checkable claim about WCAG conformance and metadata — not a label a file earns just by being an EPUB. Here's what the claim covers, where it breaks down, and what a reading app can and can't fix.

What "Accessible" Actually Means

"Accessible" on an ebook listing looks like a fact. It's really a claim, and a specific one. EPUB Accessibility 1.1 sets the bar at WCAG 2.0 Level A as a floor, with Level AA recommended — and the spec doesn't leave the claim vague. A conformant file is expected to carry metadata that says what senses you need to use it (accessMode), what adaptations it includes, like alt text or captions (accessibilityFeature), and any hazards, like flashing content, a reader should know about in advance (accessibilityHazard). A plain-language summary is recommended on top of that, so a person — not just a machine — can tell what they're getting before they open the file.

None of this is spot-check territory. Conformance is meant to apply to the whole publication, cover to cover. A book can't lean on an inaccessible fallback for the parts that were harder to fix and still call itself conformant — the primary content and any fallback both have to clear the bar. That's a higher standard than "most of it works fine," worth knowing before you take the word at face value.

Why It Matters

The gap between a real claim and a marketing adjective shows up fastest at the checking stage. Automated tools like DAISY's Ace catch a genuine slice of WCAG requirements — broken structure, missing alt text, malformed markup — but not all of them. Some criteria only a person can verify: does the reading order actually make sense read aloud, does a described image describe the right thing. A conformance claim worth trusting names who did the verifying, not just which tool ran.

That claim can also slip through the cracks before it reaches you, independent of the file itself. When a publisher's metadata doesn't make it all the way through to a retailer's records, an actually-accessible book becomes invisible to anyone filtering for one — the work got done, but it never reached the person who needed it. A file can also be accessible on paper and still fail in practice: DRM wrapping can keep assistive technology from reaching content that would otherwise read just fine. Accessibility work upstream doesn't count for much if it doesn't survive the trip to your device.

Where You'll See It

The format itself splits accessibility outcomes in two. Reflowable EPUBs — the default for most novels, articles, and text-heavy books — let a reading app adjust font size, spacing, and line breaks to the display, exactly the flexibility assistive technology depends on. Fixed-layout files work differently: the page geometry is locked in place, which is why they're common for illustrated books and comics and much harder to make truly accessible — there's less room to adapt around whatever a given reader needs.

One more distinction worth making: media overlays, the synchronized text-and-audio feature some EPUBs include, are optional. A book with no built-in narration at all can still be fully WCAG-conformant, because a screen reader doesn't need pre-recorded audio to read structured text aloud. Don't mistake "no audio track" for "not accessible" — they're unrelated questions. The format's own structure — XHTML content wrapped in a defined package — is what a screen reader actually leans on, audio or not.

How Margina Handles It

A reading app's job here is narrower than it sounds: read what's already in the file rather than reformat it. When a reflowable EPUB's heading structure and reading order were authored correctly, that structure carries straight through to VoiceOver or TalkBack as written. Margina isn't in the business of rebuilding a file's accessibility from scratch — it can't recover information that was never there to begin with.

What it can do is sit on top of that with font, contrast, and spacing controls that apply regardless of what a file's own metadata claims, useful on the days a book's own accessibility work falls short. No account, no server involved in getting a PDF or EPUB onto your phone, no rewriting of the file underneath you.

Frequently Asked Questions

Does the word "accessible" on an ebook listing mean anything official?

It can, but only if it's backed by a real conformance claim. EPUB Accessibility 1.1 defines a specific string publishers can attach to a file — WCAG level plus who certified it. A store page that just says "accessible" with no metadata behind it isn't making a checkable claim.

What is EPUB accessibility metadata, in plain terms?

A short set of fields embedded in the file itself: what senses you need to use it (accessMode), what adaptations it includes like alt text or captions (accessibilityFeature), and any hazards like flashing content (accessibilityHazard). Well-made files also include a plain-language summary.

Are all EPUBs accessible by default, since the format supports it?

No. EPUB the format can support accessibility, but a specific file is only accessible if its creator did the work — proper heading structure, alt text, a real reading order — and ideally documented it. Plenty of EPUBs in the wild carry none of that.

What's the difference between an accessible EPUB and one with audio narration?

They're separate things. Media overlays (synced text-to-speech audio) are an optional EPUB feature, not a requirement — a book can be fully WCAG-conformant with no built-in narration at all, since screen readers can read the text directly.

Can a reading app fix an EPUB that wasn't made accessible?

Only partially. An app can make sure it doesn't get in the way — clean text rendering, working with VoiceOver or TalkBack, honoring font and contrast settings — but it can't retroactively add alt text or fix a broken reading order that was never in the file.

Conclusion

"Accessible" is a claim you can check, not a label a file earns by default. The parts worth remembering: a real conformance claim states a WCAG level and names who verified it, a checker pass alone isn't the whole story, and the format's own structure — not any single feature like narration — is what carries the work through to the reader. As EPUB Accessibility 1.1.1 and related W3C work move forward, the metadata trail behind that claim is likely to matter more, not less.

If you're reading files you already have — sent to yourself, downloaded, saved from somewhere — Margina opens PDFs, EPUBs, and Word docs straight from your phone's storage, no account required.