A publisher investigating why a standards-compliant ebook would not open on Kobo devices traced the failure to a CSS declaration accepted by other reading software but rejected through an Adobe-based rendering path. André Klein documented the case after a reader reported that his new book appeared corrupted across several generations of Kobo hardware.
Klein had validated the file against EPUBCheck ruleset 3.3, the widely used conformance checker for EPUB packages. He also supplied an EPUB 2 version that passed its applicable checks, but the Kobo failure remained. The same material opened on Kindle, Apple Books and Thorium, according to his account, indicating that the package was not universally unreadable even though Kobo would not load it.
The investigation moved to Adobe Digital Editions because Kobo uses Adobe’s Reader Mobile Software Development Kit, or RMSDK, for standard EPUB files. Digital Editions reproduced the failure without a useful diagnostic: the book did not display, yet a later import attempt indicated it had already been added. That behavior left Klein to isolate the cause by repeatedly simplifying otherwise valid copies of the book.
Changes to folders, metadata, identifiers, the archive structure and its manifest did not solve the problem. Disabling the stylesheet did. Klein then divided the CSS into smaller sets until he found a modern sizing rule that triggered the failure. Replacing it with the older declaration `max-width: 150px` allowed Adobe Digital Editions to open the title. The supplied account does not provide an independent compatibility test, so the finding is best understood as a reproducible diagnosis of this specific book.
Klein argues that the deeper defect is not merely a renderer lacking recent CSS features. CSS parsers are expected to ignore declarations they do not recognize, while this path caused the entire ebook to fail silently. EPUBCheck can validate the package and inspect CSS syntax, but it cannot guarantee that every reader will handle a valid unsupported declaration correctly. Passing conformance tests therefore did not predict behavior in this implementation.
An update to the account identified a second Kobo path. Standard `.epub` files are routed to the Adobe engine, while files named with the `.kepub.epub` extension use Kobo’s maintained WebKit-based renderer. That distinction means the same underlying content may encounter different rendering behavior based on its format route. Klein published a revised edition so readers would not meet the original failure.
The episode narrows the practical lesson for ebook producers. Validation remains necessary for catching malformed packages, but compatibility testing is a separate step when a store or device relies on an older engine. When a Kobo title fails despite clean EPUBCheck results, testing in Adobe Digital Editions and reducing the stylesheet may reveal an implementation-specific problem that the formal checker cannot report.
