← Book Production Lab Cambric Book Production Lab · Maintained reference

A valid EPUB is the floor. A usable ebook is the release standard.

A maintained EPUB 3 preflight matrix covering package validity, navigation, semantics, reflow, accessibility, metadata, and retailer QA.

Version 1.0.0 Updated 2026-07-09 15 records
Use this when you need to

Make the production decision explicit.

  • Define an ebook QA gate beyond “the file opens”
  • Separate EPUB conformance from device usability
  • Review navigation and accessibility systematically
  • Trace a retailer rendering problem back to source or conversion
Open dataset

EPUB 3 Preflight Matrix

Checks are grouped into package validity, semantic structure, navigation, rendering, accessibility, and distribution QA. Conformance is verified with EPUBCheck; usability is verified in more than one reading system.

Download JSON
AreaCheckPass conditionVerificationIf missed
PackageMimetype and containerArchive structure and required files conform to EPUB 3.3EPUBCheckFile rejected before content is inspected
PackageManifest integrityEvery referenced resource is declared and every declaration resolvesEPUBCheck plus unzip inspectionMissing styles, images, fonts, or chapters
PackageSpine orderReading order matches the intended book sequencePackage inspection and linear readChapters appear out of order
NavigationNavigation documentVisible table of contents links to meaningful destinationsReading-system navigation panelReader cannot move through the book reliably
NavigationLandmarksKey regions such as body matter are identified when appropriateMarkup inspectionReduced assistive navigation
StructureHeading hierarchyHeadings describe document structure without visual-only levelsDOM/outline inspectionConfusing navigation and accessibility
StructureLanguage metadataPackage and content language are declared correctlyEPUBCheck and markup inspectionIncorrect pronunciation or storefront metadata
ContentImage alternativesMeaningful images have useful alternatives; decorative images are identified appropriatelyAccessibility inspectionContent is unavailable to nonvisual readers
ContentLinks and notesInternal, footnote, endnote, and external links resolve and return sensiblyAutomated link check plus device testBroken references or navigation traps
TypographyReflow stress testText survives large fonts, narrow viewports, and reader overridesTwo reading systems at multiple settingsClipping, overlap, or unusable layout
TypographyCSS restraintStyles preserve hierarchy without blocking reader preferencesCSS review and override testUnreadable or inconsistent device rendering
FontsEmbedded font rights and fallbacksAny embedded font is licensed, declared, and has usable fallbacksManifest/CSS inspectionLegal issue, missing font, or blank glyphs
MetadataTitle, creator, identifierCore metadata is present and matches the release recordPackage inspectionRetailer mismatch or catalog confusion
ValidationEPUBCheck resultNo unresolved errors and every warning has been reviewedCurrent EPUBCheck releaseRetailer rejection or latent package defect
DistributionRetailer/device sampleIngested preview is checked after platform conversionRetailer preview plus representative appsValid source becomes a poor delivered book

Limitations

  • EPUBCheck conformance is necessary but does not prove good typography, accessibility, or retailer-specific rendering.
  • Reading systems implement parts of EPUB and CSS differently, so representative device testing remains required.
  • Retailer ingestion may transform a valid EPUB and introduce a result that differs from the source preview.

Primary sources checked

These links define platform or open-standard requirements; none is a formatting-software affiliate link.

Why an ebook is not a smaller print PDF

A print interior resolves every line onto a fixed physical page. A reflowable EPUB packages structured documents, resources, metadata, navigation, and styles that a reading system composes for a particular screen and reader preference. Font size can change. Margins can change. A phone can become a tablet. A sighted user can switch themes, while an assistive-technology user may navigate by headings or listen to the same structure. The source must survive all of those interpretations.

That is why visual similarity to print is the wrong primary test. The ebook should preserve hierarchy, emphasis, reading order, navigation, and intentional breaks while allowing the reading system to do its job. Excessively rigid CSS may make one screenshot look controlled and make the actual book fail at large text or on a different engine. Good ebook production is structured restraint.

Conformance, accessibility, and rendering are separate checks

EPUBCheck evaluates the package against the specification and catches many broken references, invalid declarations, and markup errors. That is essential, but a clean result does not tell you whether alternative text is useful, headings describe the document, link labels make sense, or a 200% font setting creates an unreadable layout. Accessibility requirements add semantic and descriptive expectations. Device QA adds the behavior of actual reading systems.

Treat the three layers as complementary. First, eliminate conformance errors and review every warning. Second, inspect structure and accessibility with human judgment and appropriate tools. Third, read representative chapters in more than one engine, at more than one viewport and font size. Finally, inspect the retailer’s ingested preview because the distribution system may transform the source EPUB before a customer receives it.

One manuscript source, two deliberately different outputs

Print and ebook editions should share content truth without sharing layout assumptions. A print blank page may have no role in the EPUB. A running head disappears. A page-number cross-reference may need different wording. A decorative image might remain decorative, while an informative figure needs an alternative. If the author maintains unrelated print and ebook masters, a late correction can reach one format and miss the other.

Cambric’s value proposition is one structured manuscript that can produce fixed print pages and a reflowable EPUB. That does not remove format-specific QA; it makes the source of the two outputs coherent. Correct the manuscript or structure once, regenerate both artifacts, then apply the appropriate preflight to each. The result is a controlled divergence rather than two books drifting independently.

What the matrix proves—and what it refuses to claim

The matrix is grounded in the W3C EPUB 3.3 and EPUB Accessibility specifications and the EPUBCheck project. It is a maintained interpretation of the work a publisher should perform, not a certification service. No row claims that Cambric automatically satisfies every accessibility criterion, every retailer extension, or every unusual manuscript. Those claims would require versioned output specimens and reproducible test reports.

That boundary is useful to buyers. It distinguishes an honest production tool from a promise that collapses a complex release process into one button. Cambric exports EPUB 3 and lets the author maintain the source; the publisher still validates and inspects the released artifact. Our next evidence milestone is a downloadable, versioned sample EPUB with its EPUBCheck report, not a broader adjective in marketing copy.

Apply the research

Create print and ebook from one maintained manuscript.

Cambric exports EPUB 3 and print PDF from the same structured project. Keep corrections synchronized, then run the format-specific checks this matrix makes explicit.

Build the ebook source in Cambric $199 once · Windows + Mac · local-first projects · 30-day guarantee
Questions this resource answers

Production FAQ

Is passing EPUBCheck enough?

No. It establishes important package conformance, but you still need semantic, accessibility, navigation, reflow, link, device, and retailer-ingestion QA.

How many ebook readers should I test?

At minimum, use more than one engine and test narrow and wider viewports at multiple font sizes. Add the retailer preview for every distribution destination that transforms the file.

Should an EPUB look exactly like the print book?

It should preserve content, hierarchy, brand cues, and intentional structure, but a reflowable ebook should not imitate fixed pages at the expense of reader controls and accessibility.