View Single Post
Old 10-05-2024, 06:12 PM   #23
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,054
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
Did you read the linked document??



Eg you must use the proper html tags if you want the assistive device to recognize it properly… css styling alone does not cut it.

Edit for clarification:
CSS properties (italic/bold) are for presentation (visual appeal). The html tags are what trigger the assistive technology. You can add other css styling to describe elements of the ‘voice’ but italic/bold in and of themselves in css don’t mean anything to accessibility devices.
But that's not how it really happens. The big publishers do not use <em> and <strong> "properly". So what's the point?
JSWolf is online now   Reply With Quote