Using the UX display guide with Daisy files

[HadrienGardeur]

With the advent of the European Accessibility Act and the growth of born-accessible EPUB files, users that have mostly relied on Daisy files in the past will increasingly use services with a mix of adapted (Daisy) and born-accessible publications (EPUB).

In order to provide a consistent user experience for these users, it feels important to also consider how Daisy publications could benefit from these same techniques and terms.

While ONIX is already format-agnostic and would in theory allow to express these metadata on Daisy publications, I think that it's very unlikely that ONIX will be used alongside the distribution of Daisy.

• Could we rely on alternate distribution or metadata record formats to convey this same information? (I can answer yes for OPDS)
• Could we express this information in Daisy or infer it somehow?

I'm no Daisy expert but based on my limited knowledge of the format, there are three main use cases for Daisy:

• full audio, which would mostly behave like an audiobook with additional navigation capabilities
• full text, which would be fairly similar to an EPUB 2.x
• and synchronized text and audio, which would be fairly similar to a reflowable EPUB with Media Overlays

The typical production for synchronized text/audio is sentence-level synchronization, but the granularity of what's synchronized could also be conveyed by a new metadata since it's relevant for users.

[GeorgeKerscher]

Bookshare uses ONIX as the primary of populating their catalog. @clapierre

[avneeshsingh]

DAISY books has its own metadata. It is mostly dublin core, in fact a good amount of EPUB metadata also came from the same concepts. And in DAISY, we had extended the metadata by adding dtb prefix metadata. We have not worked on metadata crosswalk for DAISY, but I believe that most of information like screen reader friendly, audio sync with text, logical reading order etc. can be interpreted from metadata provided in DAISY books.