I support Ted in that AHL should have synchronization mechanism between renditions, but that looks like a separate topic from a11y and image spine to me.
Now suppose the book instead had two renditions, one with bitmaps as
spine items, and the other with textual equivalents in XHTML spine
items. How are these friends expected to read the book together?
Ah…I guess I’m lost here, sorry. Could you elaborate a bit more?
When you say “additional methods for discovery”, is it about accessMode property you mentioned before? Is it proposed before and declined, or someone said it’s a bad thing? And how does it related to image spines?
/koji
There's one issue that we plan on adding to the 3.0.1 tracker as a follow up to the AHL F2F meeting : the introduction of a new metadata element, that would provide a list of "features" required for the publication.
Scripting or support for fixed layout could be one of those features, but support for bitmap in spines could certainly be on that list too.
As ONIX metadata can be included in the EPUB itself, these information from ONIX code list 196 could then made available to Reading System.
Luc
De :
epub-work...@googlegroups.com
[mailto:epub-work...@googlegroups.com] De la part de Matt Garrish
Envoyé : mercredi 24 avril 2013 22:12
À : epub-work...@googlegroups.com
Objet : Re: Simultaneous reading, A11Y, and alt="" (re:
bitmaps as spine items)
Thank you Matt for creating a new issue, I agree with you that it’s important to track but it’s a separate issue.
Given that, it looks to me that we’re all fine—or at least can live with—adding image spines support in EPUB 3.0.1. I’d appreciate to know if there were any issues we missed.
/koji
We could model this off of current browser behavior – which appears to treat these as background images with a background-size of ‘contain’ (tested IE10 / Chrome / Safari / Firefox ).
+1
<firefox.png><opera.png><chrome.png>
+1