printPageNumbers vs pageBreakMarkers

  • This topic has 1 reply, 2 voices, and was last updated 1 year ago by APLN Moderator.
Viewing 2 posts - 1 through 2 (of 2 total)
printPageNumbers vs pageBreakMarkers thread
Author Posts

Where are we on moving over to the new standards?

Also I assume we should be moving to: meta property="pageBreakSource">urn:isbn:9781234567891/meta>

I was also wondering about schema:accessibilityFeature”: annotations vs longDescription for extended descriptions that exist on a separate xhtml page.



APLN Moderator


Thank you for this interesting discussion topic!

A new version of Ace was released last week that addresses the printPageNumbers and pageBreakMarkers issue:

According to W3C “printPageNumbers” is not formally deprecated and can still be used, but “pageBreakMarkers” is the recommended value.

As for “pageBreakSource”, while it is being developed as a replacement for dc:source and page-source properties, it is not formally part of EPUB 3 and might produce a validation error with epubcheck. The following DAISY Knowledge Base page will be updated once the use of “pageBreakSource” is fully recommended:

Moreover, for extended descriptions that exist on a separate xhtml page within the EPUB, the accessibility feature “longDescription” is typically used, particularly for complex content such as images, tables, charts, etc. The “annotations” value is used when the “publication comes with explanatory annotations that improve the accessibility of the work” from the “author, instructor, and/or others.”

See the following links for more on these accessibility features:


Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Want to join the discussion?

a wooden table with a white keyboard on top, and a persons hand writing on a piece of paper

View our current resources