Looking again at the very latest epub 3 epub:type Semantics vocabulary guide from March 2025, they have introduced lists of allowable tags for epub:types which of course includes the body tag itself which directly conflicts with all the aria roles.
I understand epub:types for Nav landmarks, and footnote and endnote and their backlinks, but outside those areas epub:type attributes are *not* used by e-reading systems and are *not* used for accessibility software as clearly and brutally stated by the Daisy Knowledgebase website.
https://kb.daisy.org/publishing/docs...epub-type.html
Given that, do we want to add another full dialog and code class, and menu item just to insert them if no one is using them? Many of them are epub dictionary specific, and index specific but are not being used at all.
Thoughts?
Should I just merge endnote, footnotes, and bibliography entry into the roles but mark clearly they are epub:type only in the descriptions?
Or should we create a second menu item, class, and Dialog to insert the majority of the available epub:types from the vocab doc like the proof of concept did for aria publishing roles?