[KevinH]

Originally Posted by noteon

Thanks! A few things I'm unclear on:

1. The readme says to make sure you have "properly added the appropriate semantic tags to mark your ebook files appropriately." Then in the list of things the plugin does, #5 says it will "add in appropriate epub:type semantic tags," and #6 says it will "map epub:type attributes to their appropriate aria role attribute."

For number 5, Yes, the nav has a landmarks section. These user supplied landmarks semantic tags (epub:type) will be added to the proper body tag or id for each chapter if possible by the plugin

But, the user can and should use the epub3 semantics tool and manually add epub:type attributes to various tags in each part of the book. They should do this before runnng the plugin. The plugin itself will convert the epub:type to an aria role and add that in as well.

2. In #2, the plugin "fills in any missing title tag that is a child of the head tag." Is this the text it collects when "The ncx or nav is then parsed to collect titles for every xhtml file?" I was not able to get this to work; is there a precondition of some sort in the xhtml file?

It will not replace existing title tag contents in head. So make sure you have the latest version of the plugin and that the current title tags are truly empty (no whitespace). The titles for each file are taken from the nav.