Accessibility metadata should be included with every ebook, as it lets the reader know about what accessibility features have been included! This introduction discusses the importance of accessibility metadata, and shares examples of each type.
Subject(s):
Metadata
Resource Type(s):
Standards and Best Practices
Audience:
Technical
Before you read this, you might want to read:
There is a lot of talk about accessibility metadata these days! You probably know it is highly recommended, really useful, and important to include in every ebook. But what is less well known is the most important stuff – like what it is, how to create it, and where to include it. This page should help clarify all of these key questions, or at least set you on the right path.
Accessibility metadata is metadata that shares the accessibility features in a book. When it is included in an ebook, it enables potential readers to know if the book meets their needs, and tells them all about the amazing accessibility features you have been working so hard to include. Accessibility metadata should always be included in an ebook’s OPF file, and creating and including ONIX records with accessibility metadata is highly recommended.
Accessibility metadata allows you to share all kinds of details about the book, like if you have included accessibility features such as page navigation or image descriptions, if the display is customizable, if there are any hazards (like sound or flashing) which could cause a physical reaction, and much more! Including as much accessibility metadata as possible will ensure that readers can be confident that they are picking a book that meets their needs.
There are three types of accessibility metadata which should be included with an EPUB.
Head on down to the Related Content section below to visit an in-depth overview of each type! But first, we’ll look at a few examples:
This is an example of some Schema.org accessibility metadata that comes from the “CreativeWork” Class, which is used for books (and movies, photographs, software programs, etc.). This metadata is included in an ebook’s OPF file.
<meta property="schema:accessMode">textual</meta> <meta property="schema:accessMode">visual</meta> <meta property="schema:accessModeSufficient">textual,visual</meta> <meta property="schema:accessModeSufficient">textual</meta> <meta property="schema:accessibilityFeature">alternativeText</meta> <meta property="schema:accessibilityFeature">structuralNavigation</meta> <meta property="schema:accessibilityFeature">MathML</meta> <meta property="schema:accessibilityHazard">noSoundHazard</meta> <meta property="schema:accessibilityHazard">noFlashingHazard</meta> <meta property="schema:accessibilityHazard">noMotionSimulationHazard</meta> <meta property="schema:accessibilitySummary">This publication has no major violations in the ACE by Daisy App, and conforms to WCAG 2.0. Images are described, and there are several levels of navigation. It is not known to contain any element that may cause seizures or other physical reactions.</meta>
This is an example of some ONIX accessibility metadata for “Product Form Feature Type: E-publication accessibility detail”. The text wrapped in “<!-- …-->”, like <!--No reading system accessibility options disabled--> are human-readable comments that describe the “ProductFormFeatureValue” under each “ProductFormFeatureType”. The ONIX record is a separate XML file that is sometimes packaged with an ebook, and sometimes kept separate.
Note that this is just an example, so you have an idea of what it looks like. For an exhaustive list, check out Related Content below.
<Product> <DescriptiveDetail> <ProductFormFeature> <!--No reading system accessibility options disabled--> <ProductFormFeatureType>09</ProductFormFeatureType> <ProductFormFeatureValue>10</ProductFormFeatureValue> </ProductFormFeature> <ProductFormFeature> <!--Table of contents navigation--> <ProductFormFeatureType>09</ProductFormFeatureType> <ProductFormFeatureValue>11</ProductFormFeatureValue> </ProductFormFeature> <ProductFormFeature> <!--Reading order--> <ProductFormFeatureType>09</ProductFormFeatureType> <ProductFormFeatureValue>13</ProductFormFeatureValue> </ProductFormFeature> <ProductFormFeature> <!--Short alternative descriptions--> <ProductFormFeatureType>09</ProductFormFeatureType> <ProductFormFeatureValue>14</ProductFormFeatureValue> </ProductFormFeature> <ProductFormFeature> <!--Language tagging provided--> <ProductFormFeatureType>09</ProductFormFeatureType> <ProductFormFeatureValue>22</ProductFormFeatureValue> </ProductFormFeature> </DescriptiveDetail>
Last but not least, there is conformance and evaluation metadata – this set of metadata should only be included once a publisher/book has been certified. When it is applicable, this metadata is included in an ebook’s OPF file.
<link rel="dcterms:conformsTo" href="http://www.idpf.org/epub/a11y/accessibility-20170105.html#wcag-aa"/> <meta property="a11y:certifiedBy">Accessibility Certifying Body</meta> <meta property="a11y:certifierCredential">Credential that Establishes authority of certifying body</meta> <link rel="a11y:certifierReport" href="https://linkToCertificationReport.html"/>
This specification discusses discovery and accessibility of EPUB publications. Discovery relates to accessibility metadata. Accessibility includes guidelines in WCAG 2.0 and some additional items on page navigation and media overlays. The specification also discusses how to indicate conformance, information about optimized publications for specific use cases such as audiobooks, and a short section on distribution considerations.
This archived webinar from the DAISY Consortium on June 24, 2020 discusses metadata. schema.org and Dublin core metadata is included in the EPUB file itself; and the Onix and Marc21 standards provide the ability to have external metadata used alongside the EPUB and can be used to include accessibility information in book catalogs.
This page has brief explanations of how to mark up several types of content including sections, headings, emphasis, figures, sidebars, and blockquotes among others. It also discusses ARIA roles for the included elements where applicable. The page ends with a discussion of accessibility metadata.
This is an excellent reference with details and best practices for many EPUB accessibility topics. It provides explanations and code examples. Coverage includes EPUB accessibility, validation, metadata, HTML, and CSS from the perspective of using available markup elements to their full potential for accessibility.
This course on LinkedIn Learning by Laura Brady covers how to use InDesign to make ebooks that are as accessible as possible. Items covered include separating style and content, navigation and structure, and image descriptions. Page lists and the Ace Accessibility checker are also covered.
This specification explains how to present the accessibility metadata in an EPUB file to end users. It covers several areas: screen reader friendly, full audio, accessibility summary, conformance, certification, hazards, and lists all available metadata.
This page covers how to determine accessibility information based on the ONIX metadata. ONIX can be useful because it is available in a catalog before a user obtains the EPUB itself. Categories covered are: screen reader friendly, full audio, accessibility summary, conformance, certification, hazards, and listing all available accessibility metadata.
This page discusses the European accessibility requirements set to come into effect in 2025. Research was done to discover whether the existing metadata schemes of ONIX and schema.org metadata provide the needed information about the accessibility of ebooks. The results suggest that these do provide what is needed. A more detailed report is also available for download.
Content Source Acknowledgement
AccessiblePublishing.ca: EPUB Semantics, ARIA Roles, & Metadata
DAISY: Metadata in Publishing (Webinar)
DAISY Knowledge Base: Evaluation Metadata