View Single Post
Old 08-04-2023, 09:56 AM   #12
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,878
Karma: 6120478
Join Date: Nov 2009
Device: many
To note ... it is Accessibility that wants those titles filled in properly (alongside img alt, and semantic tags).

IMHO, both epub2 and epub3 devs should strive to make an epub as Accessible as possible. Adding those titles automatically from either ncx or nav entries for that file or even from local header tags for that file is trivial work for a plugin to do. The AccessAide plugin will help you do that as well as make it easier to fill in img alt tags with something more meaningful, add semantics where needed, etc.

If just a title updater plugin is needed, I could throw something together to do just that but there are other things that should be added to make an epub more Accessible.

As for why epub3 vs epub2, it is to help provide better Accessibility (smil, more semantics, etc) and to future proof the epub even when it does not need specific epub3 only features.

My 2 cents ...
KevinH is online now   Reply With Quote