View Single Post
Old 04-14-2025, 03:38 PM   #6
ElMiko
Evangelist
ElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileRead
 
ElMiko's Avatar
 
Posts: 480
Karma: 65460
Join Date: Jun 2011
Device: Kindle
@JSWolf — yeah... using <span>s just for italics just feels really cumbersome to me and visually confusing while I'm editing. This is, obviously, merely a "me" problem, so I get it that others are happy to take this approach. but for me the decision tree is simply to <i> or to <em> at this point.

I'm inclined to err on the side of accessibility (especially since a word that's been erroneously emphasized aurally is less bothersome to me than one that's erroneously de-emphasized). However, I'm also struggling to see the <em> effect in practice with the—admitedly simple—text-to-speech programs I've tested. So... until I get more clarity I'm sticking with <i>. Praise regex, going back and switching to <em> should be trivially easy.

In that case, though, I'm also wondering: is it best practice is to include a css feature that specifies the appearance of <em>? e.g.:

em {
font-style: italics;
}
ElMiko is offline   Reply With Quote