View Single Post
Old 07-15-2022, 12:08 PM   #163
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,009
Karma: 147977995
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 Turtle91 View Post
Its not that the device won't read what's in the alt=""...its that the standard wants people to use <hr>. If you don't like that answer then don't use it. You can use any other non-compliant technique you want to use. But arguing with US about it isn't going to get you anywhere because WE don't control the standard.

If you want to know how every accessibility compliant device reacts when reading an <hr/> then I would suggest either reading the user's manual on all the different devices, or test them out.
When the program reading the eBook comes to the hr, what is it supposed to do according to the standards?
JSWolf is offline   Reply With Quote