Quote:
Originally Posted by ElMiko
@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 look for classes to see what's being used where. A class that does italic or bold is a pain. So I change them to <i> and <b>.
[/quote]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.[/quote]
There is no visual difference between <i> and <em>. Also, nobody has been able to say what TTS reads <i> and <em> differently. So I too stick with <i>. However, if the class that's being used specifies italic, I leave it be.
Quote:
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;
}
|
There's no need to do so as <em> is italic by default. I've seen some CSS define <i> and <b> to be italic and bold when is also not needed.