Quote:
Originally Posted by Sarmat89
ToCs are created manually, as the text content of the header and the ToC entry is different.
|
IMHO, it's much more efficient to generate TOCs from h1..h6 entries, and if the text of the TOC entry is not identical with the content of the header tag, you can define it as a h1..h6
title attribute, which some tools, e.g. Sigil, use for generating the TOC.
Moreover, both
W3C and
DAISY recommend the use of h1..h6 tags:
Quote:
|
Originally Posted by W3C
Heading markup will allow assistive technologies to present the heading status of text to a user. A screen reader can recognize the code and announce the text as a heading with its level, beep or provide some other auditory indicator.
|
Quote:
|
Originally Posted by DAISY
Headings are one of the primary means of navigation for users of assistive technologies.
Each section should have a numbered heading (e.g., h1) that reflects its level in the document hierarchy, as numbered headings allow assistive technologies to navigate the document structure.
Each heading element must represent a single heading. Do not break a heading up into separate tags for visual formatting.
|
IMHO, publishers and ebook producers who don't use h1..h6 tags to mark headings violate best practices.