If two people are using the same book, one from xyz and the other from abc and they are not identical, there will be no coordination. We know xyz is looking to put them in, when a title does not come from the publisher with them, and here is where we need the standardization. All kinds of good reasons for having virtual page numbers. Interesting thread! IMO this is not an accessibility issue and is better positioned as a usability issue. So how do they do that if the source of the pagination is itself? If we need a separate issue for an accessibilityFeature of digitalPageNumbers I am fine with that but then we would also need to revise the statementĮPUB Creators MUST identify the source of the pagination in the Package Document metadata. I am less concerned maybe with the initial issue of self referencing for the source-of pagination although it is related. My only issue is that right now we don't have a way to state that in the accessibility metadata if accessibilityFeature = "printPageNumbers" is only for print book page synchronization we don't have the equivalent for digital only.
I doubt a single publisher would do that, my thought was two competing publishers producing the same style of book with all else being equal I would want to purchase the one that had the embedded page breaks for consistent page navigation across all readers my students have. All the page breaks are virtual, for example, whether they come from a print source or not. Experience suggests that when we move into these kinds of nuances it leads to confusion and misapplication of terms. I understand your desire to put this in, but I also think this gets misleading as an accessibility feature.
That's why I'm saying this is a usability, or best practice, issue. This is the ideal, for sure, but I don't think it falls within the scope of an accessibility spec to mandate this.
Your other questions I would categorize as: It's a misnomer to say that it is its own source, since that's self-referential. I think you're arguing something different than what is the source of the pagination, though, which is what I'm trying to get clarified in this issue.Ī digital-only publication has no source for its page breaks. Previously we identified this by having accessibilityFeature="printPageNumbers" and then role=doc-pagebreaks along with the requirement of dc:source and we did discuss for EPUB only (ie no print version) this would self reference the EPUB and then additionally the the metadata of pagination.ĭo we now need to add a new accessibilityFeature value of "digitalPageNumbers" or "virtualPageNumbers" and then perhaps keep dc:source as self referencing the EPUB's ISBN, and then make it clearer with the refines property="source-of" being a new "virtualPagination" or "digitalPagination"Ĭorrect but if there are 2 books one with virtual page breaks embedded and one withoutīut is this a reality with digital-only books? Why would a single publisher produce two versions of the edition only varying by the inclusion of page breaks? We need a way to identify there are embedded page breaks for discovery. Having these page numbers embedded in the publication means that no matter the reading system used or the size of one's screen that when a teacher says go to page 23 everyone gets to the same page. We still need some solution if there are page numbers added by the publisher for a digital only solution where there is no print version.
0 kommentar(er)
