View Single Post
Old 03-07-2016, 10:20 AM   #24
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,887
Karma: 6120478
Join Date: Nov 2009
Device: many
This inability to prevent the warning with the latest epubcheck 4.0.1 version really bothers me. So I have created an epubcheck issue on github asking if the epubcheck validator was even correct in this case and if so, how should the warning be prevented. My personal opinion is that it is a bug. Somehow the warning gets triggered by an xlink:href in an svg "image" element but epubcheck does not actually look at that same "image" element to determine if a xlink:title attribute actually exists. Epubcheck should simply not generate a warning if there is no way to prevent it! The idea behind the warning is to convince users to add accessibility information (such as a title that explains what is going on) but adding the title doesn't seem to prevent the warning which defeats the whole purpose.

I will let you know if and when I receive a response on how best to "fix" this.

KevinH
KevinH is offline   Reply With Quote