Quote:
Originally Posted by KevinH
You do understand the purpose of semantic tags like h1-h6 in html markup, right? You can of course use CSS to make the headings look virtually any way you want, but using the proper heading tags allows automated reading system to auto-detect structure for those who need accessibility help.
|
Quote:
Originally Posted by DiapDealer
If you use Sigil's Tools->Table Of Contents->Edit Table Of Contents you will find a dialog that allows you to do the same thing. Create/edit/delete your ToC headings (nest them, unnest them if you like), point them to the page (or ID) you want them to be linked to, click "OK" and Sigil updates the underlying code in the EPUB automatically. Badabing badaboom.
|
Maybe people get confused because in Sigil they are two separate functions:
- "Tools" -> "Generate Table of Contents"
- Creates TOC using <h1-6>.
- "Tools" -> "Edit Table of Contents"
- (Doesn't have an icon and many people don't even notice it)
- Is similar to Calibre's TOC Editor.
where Calibre has the Generate functionality folded into a button in the "Edit Table of Contents" tool.
Quote:
Originally Posted by Hitch
And folks should bear in mind--when accessibility starts being checked by Amazon--which most surely, sometime soon, they will start to do--you can bet your booties that using the wrong class of element, to do a job, is going to become a problem about which the self-pubs will come to care. Just like the fact that typos, poor formatting, etc., all of which was blown off, before, have now come home to roost with the far-more-stringent Kindle Quality standards.
|
Next up we are going to get people promoting minus signs instead of hyphens/en-dashes/em-dashes! It
looks the same to me! Who needs Text-to-Speech in books?
