page-list and pagebreak #829
Comments
|
As I recall, that's by design. We weren't going to make production dependent on the epub:type attribute. You can include just the page-list. Including both is part of the accessibility techniques. |
|
Or are you asking for an informative note, like: "See also the pagebreak term [StructureVocab] for identifying page break locations in EPUB Content Documents." |
|
I first thought that nav page-list is required to use epub:type="pagebreak" but this requirement is not made clear. Your first reply shows that there are no such requirements. Your second reply provides an informative note. Your note is a good one, but another note (based on your first reply) would be useful. |
|
What about making a normative statement: "The destination of the page-list references MAY be identified using the pagebreak property [StructureVocab]." This would perhaps give better precedent for increasing the requirement in the accessibility specification. |
|
Proposed Solution Add an informative "may" about use of pagebreak property. |
#755 - change alt-script to alt-rep and clarify language #761 - make image cmts required when there is a viewport #773 - update roadmap and add diagram #778 - clarify package conformance #780 - generalize backwards compatibility statement #800 - clarify svg handling for fxl documents #808 - replace spaces with underscores in rootfile examples #822 - fix obsolete feature labels/descriptions #823 - add note about incomplete RS requirements for scrolled-continuous #824 - add clearer content model for nav elements #826 - note toc nav is required in intro #828 - clarify ordering requirements for toc nav references #829 - note optional use of pagebreak with page-list adds a link to the informative a11y faq; patches errata not applied to doi examples; probably some other minor stuff, too
Shouldn't the definition of nav page-list mention epub:type="pagebreak"?
The text was updated successfully, but these errors were encountered: