Archive for October, 2009

Adobe and Barnes & Noble eBook Collaboration

Adobe and Barnes and Noble announced today a partnership to advance the open eBook platform standard. This was part of a broader announcement by B&N featuring their new nook device – which is very sweet – definitely the highest techno-lust quotient of any eReader device to date.
The adoption of EPUB, PDF & ACS4 by B&N is an extremely significant milestone. First, it puts to rest concerns that B&N would adopt EPUB as a base format but frustrate consumer expectations of interoperability and confuse the marketplace with a non-interoperable content protection solution based on their Fictionwise eReader acquisition. Instead, B&N is adopting the cross-platform Adobe solution that is already used by Sony, OverDrive, and nearly a hundred others. And, by adding support for password-based content protection for EPUB, Adobe is addressing the need to deliver a more lenient “social DRM” option as part of our solution. And from the perspective of the overall ecosystem, today’s announcement is huge: we have, within the last two months, seen two “legacy” proprietary eBook formats – BBeB and eReader – superseded by the open standard EPUB solution with Adobe’s cross-platform content protection. In essence, there is now a clear “DVD of eBooks” format standard, and everyone significant has adopted it (with now only one remaining exception).
This partnership is a double win-win: a win for both companies involved, as well as for the rest of the ecosystem and consumers. It’s clearly a good move for B&N and Adobe, it’s going to help accelerate consumer adoption of eBooks by cementing the standard eBook platform – EPUB and PDF with the option of ACS4 DRM – and giving consumers content portability across their choice of devices.
While Adobe and Barnes & Noble work at very different levels of the value chain, I feel we really have a shared vision, one that William Lynch, President of, emphasized at the nook launch: “Any Book (Magazine, or Newspaper), Any Time, Anywhere (On Any Device)”. Today, we all took a big step towards realizing this vision.

Adobe eBooks – Update on Accessibility Support

A few inquiries have come in about a press release earlier this week by the Reading Rights Coalition noting that the Los Angeles Public Library has suspended purchasing eBooks compatible with Adobe Digital Editions, because there is no accessibility support in our solution. This post is intended to clarify the situation and provide an update on our roadmap.
The basic concern of the Reading Rights Coalition is legitimate. Adobe Digital Editions is a PC application that replaced the eBook support that was present in older versions of Adobe Reader. While there are many new capabilities in Adobe Digital Editions, most importantly support for epub in addition to PDF, and overall its more consumer-focused user interface, Adobe Reader did support screen readers and a “read out loud” feature, neither of which is presently in Adobe Digital Editions. This is a regrettable situation. It stems from the fact that, for a number of reasons, we made the decision to build Adobe Digital Editions in a technology called Adobe Flex, targeting the Adobe Flash desktop runtime that became Adobe AIR. While the browser-based version of Flash Player has for quite some time included accessibility support, the desktop configuration has not, and neither the AIR team nor our Digital Editions team was able to incorporate accessibility support in our respective version 1 implementations.
We agree completely that eBook accessibility is critical. Adobe is helping to create the cross-platform standard for interoperable eBooks. Clearly, accessibility support is a fundamental requirement. One of the key motivations for supporting epub was that it was a more structure-based and thus more inherently accessible file format makes. So, the current situation is simply unacceptable.
So what are we doing about it?
First, the next major release of Adobe Digital Editions, expected within the coming year, is going to support accessiblity features. Earlier this week, Adobe previewed AIR 2, and we disclosed that screen reader support was going to be included. This will be a key enabler for us.
Additionally, Adobe has begun working with several vendors of accessibility-oriented software and devices to get them access to Adobe eBook rendering and DRM technology via our Adobe Reader Mobile SDK, so their solutions can consume Adobe eBooks. Our Reader Mobile SDK is not a revenue generator for Adobe; our standard terms are focused on proliferation (and with 17 announced licensees so far this year we are doing pretty well on that front). This is similar to the Open Screen Project for Flash licensing. But since many accessibility vendors are either nonproffits or have limited financial resources, we have gone even further in extending extraordinarily favorable terms to get them access to our portable document technology. I expect we will be able to make some specific announcements around this very shortly, but the bottom line is that there will soon be multiple means for visually-impaired end users to consume Adobe eBooks.
One still controversial issue is that some publishers are concerned lest non-visually-impaired consumers get access to “read out loud” functionality that would potentially undercut sales of audio books. Adobe plans in this regard are to support in our DRM system a permission setting that will enable publishers to disable “read out loud” functionality in software systems that are NOT focused on the visually impaired. But, we plan to default this permission setting to “enable” and recommend strongly that publishers not set it to “disable”. As well we plan to exempt accessibility-oriented software from being limited by this setting. We feel this approach will strike an appropriate balance between giving publishers the rights to determine how to distribute their copyrighted content, and ensuring that accessibility is provided.
Again, the current situation is unfortunate. As someone who has helped foster the adoption of epub, including the decision to support DAISY as a type of basic content within epub, it is a black eye for me personally that Adobe’s solution does not presently provide accessibility support. I am grateful that the Los Angeles Public Library has only “suspended” purchasing Adobe eBooks, and I look forward to working with our partners to, in short order, remedy the situation.