Navigation document without toc, page-list, or landmarks #826
Comments
|
The
But the other two are optional. Inclusion of |
|
Thanks. I looked over this sentence. I would like 5.4.2.1 Introduction to specify that toc nav is require while toc page-list and toc landmarks are optional. |
|
We don't make normative statements in informative sections. The most I'd offer to do for this is add the following to the toc nav description: "The toc nav is the only navigation aid that has to be included in the EPUB Navigation Document." |
|
Should we also recommend page-list with a reference to accessibility docs? |
|
We've tried not to cross-pollinate requirements to avoid them getting out of synch. If we move the recommendation into the packages spec, it also potentially becomes a warning for everyone who doesn't include. If you want it considered, though, please open a new issue. |
|
Proposed Solution Add the following qualification to the nav types introduction: "The toc nav is the only navigation aid that has to be included in the EPUB Navigation Document." |
|
Ok to leave accessibility requirements in a11y docs. |
#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
Is the use of
<nav epub:type="toc" ...>, or<nav epub:type="page-list" ...>, or<nav epub:type="landmarks" ...>required? If I am not mistaken, the current text allows a navigation document not to have any such.The text was updated successfully, but these errors were encountered: