Introduction to Schema.org Accessibility Metadata
This resource defines all of the schema.org accessibility metadata properties and provides guidance on what to include in your OPF file.
Follow this step-by-step guide to extract accessibility metadata from your EPUB and translate it into ONIX.
Subject(s):
Metadata
Resource Type(s):
Step-by-Step
Audience:
Technical
Before reading this, you might want to read:
This resource was authored by Amanda Lee, Metadata Consultant. Amanda has worked in Canadian publishing for over 10 years. As an independent consultant, Amanda has managed projects focused on using accessible publishing or metadata to ensure everyone looking for a Canadian book can get it. Those projects include managing metadata workflows for Canadian publishers, training publishers in enhanced metadata and digital distribution, researching the state of accessible book publishing, researching the effects of specific pieces of metadata on sales of books, and more.
Drag your EPUB file into the Ace by DAISY main screen or use the “Check EPUB” button. Once it’s processed, click into the Metadata tab (highlighted below).

Sort the metadata by Accessibility (highlighted).
Open the Accessibility Properties Crosswalk. Using the metadata in Ace, match each item in the Name column to a header in the crosswalk. Then, find the item in the Value column in the related column of the crosswalk and copy down the instructions to convert to ONIX. Repeat until you’ve got every metadata feature represented (or as many as possible).
For example, to find this item…


Open the ONIX Codelists (available with easy navigation at onix-codelists.io or using the official EDItEUR codelist browser).
Find the lists indicated in the information you entered. Find the codes within the list and copy them down. Repeat until you’ve got every metadata feature represented (or as many as possible).
Using the example above, which was “List: 81; Code: 10 combined with List: 196; Code: 10 means all text is actual text.”, you would…
ONIX is the metadata that is produced by your database (such as CoreSource, BooksoniX, ONIXEdit, BookConnect, etc.) or your distributor’s database. When you enter information—not just accessibility data but any metadata—into your database it lives there. When that data is “distributed”, “disseminated”, or any other term that means “sent”, it gets converted to an ONIX file. That ONIX file, which looks a lot like HTML code, is loaded by your trading partners into their own databases, which then power the way data is displayed on their websites.
ONIX is a very robust set of codes that can be somewhat limited by the capabilities of your databases. In your database, you’re looking for Accessibility Metadata or E-publication Accessibility Details, where you would enter the applicable accessibility metadata information.
Below is an example from the CoreSource platform. In your EPUB asset’s Basic Information tab, search for the “Product Form Feature(s)” field and add the applicable metadata. Currently, this can be done manually for each title via the user interface, or for multiple titles through CoreSource’s metadata spreadsheet.
