Accessibility Metadata in Upload

Accessibility Metadata in Upload

Overview

When uploading EPUBs into our platform, publishers can include accessibility metadata that helps readers understand the accessible features of a publication. This metadata can be provided in three ways:

  1. By including it in your EPUB using the EPUB Accessibility specification (and related EPUB Accessibility Techniques). Metadata sent this way will automatically be extracted from the EPUB and provided to users.
  2. Directly providing it by using the accessibility metadata template in our Upload system. (This is based on the Schema.org standards used in #1 above)
  3. Sending it to VitalSource through an ONIX feed (speak with your customer success contact for details)

This metadata benefits all readers, not just those with disabilities, by making features like adjustable text and read-aloud functionality discoverable.

Schema.org – Accessibility Metadata

The Upload template follows Schema.org accessibility fields. These include key descriptors such as:

  • Access Modes (e.g., visual, auditory, textual, tactile)
  • Accessibility Features (e.g., alternative text, table of contents navigation, structural markup)
  • Accessibility Hazards (e.g., flashing, motion simulation)
  • Accessibility Controls (e.g., keyboard navigability, voice control)

For detailed breakdowns:

Displaying Accessibility Information to Readers

Accessibility metadata should be presented in a clear, consistent, and user-friendly way. This ensures readers—regardless of technical expertise—can understand the accessibility options available for each publication.

The W3C Accessibility Metadata Display Guidelines (2025) provide a framework for how VitalSource translates your metadata into meaningful end-user information.

Additional Resources

Summary

  • Upload supports accessibility metadata through Schema.org fields or ONIX feeds.
  • Correct metadata helps users discover accessibility features and avoid hazards.
  • Following W3C guidelines ensures metadata is presented clearly to end users.
  • Publishers are encouraged to consult DAISY, APLN, and Inclusive Publishing for detailed implementation support.
Was this article helpful?
Have Questions?