View Single Post
Old 09-20-2019, 07:19 AM   #177
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,138
Karma: 148951761
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by AliceWonder View Post
If you don't use the abbr tag with abbreviations - then according to ePub accessibility guidelines you are suppose to put that lack of standard accessibility technology into a meta tag in your .opf file so that those who need it can know to avoid your book.

I hope those who don't use abbr tag with abbreviations do that.

Basically you should aim for either WCAG 2.0 (or 2.1) AA or AAA conformance and if you don't have AA conformance, you need to identify what accessibility features your ePub is missing. There's a meta tag for doing just that.
That meta tag won't help anyone. Most people don't look at the code for an eBook. That meta tag won't help when someone is buying your eBook. You have to give up trying to do things with what the current standards say and go with what actually works.
JSWolf is offline   Reply With Quote