View Single Post
Old 02-03-2024, 06:32 AM   #68
paperwhite13
Zealot
paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.paperwhite13 can eat soup with a fork.
 
Posts: 131
Karma: 9236
Join Date: Jun 2020
Device: Kindle PW3 [KOReader]
Quote:
Originally Posted by Sarmat89 View Post
It makes no sense to use <h#> tags for anything. They were intended for technical documentation, where there is a strict hierarchy of headers having the corresponding inline numeration, and which can be indexed to build the tables of contents.
Books, however, do not have a hierarchy of headings (what level is 'Epilogue', for example), their headers are not numbered (a separate element is used which combines the number with some descriptive text, they can have very long subheadings, which are grammatically connected to the heading itself. That means they cannot be put into ToC automatically, unless another extra element is added, the title attribute. It is better to represent headers as what they are, a set of paragraphs, without inapplicable abstractions.
Maybe, but DAISY Consortium does require the use of header tags for acccessiblity. And leaving aside that not all books are fiction books with an epilogue, one could say that an hierarchy can easily be approximated -- I would put Epilogue on the same level as a regular chapter.
paperwhite13 is offline   Reply With Quote