Quote:
Originally Posted by Turtle91
You are right that you can change i/b using css, but you can’t change accessibility software that relies on them to be tagged properly….
Just because you haven’t seen it doesn’t mean it’s not out there and used properly. You obviously haven't seen my books (or read the examples I've posted here) then you would have seen them...
Again…these are all arguments that have been presented here before, you just choose to ignore them. That’s fine for your personal books, but please don’t present it here as the way it SHOULD be done.
Edit: take a look at the daisy accessibility listing for em/i strong/b |
In the eBooks I've edited from major publishers, even though the eBooks may be ePub3 with accessibility in the OPF, It's been all <em> or all <i>. Same with <b> and <strong>. I've not seen any mixed eBooks that use both <i> and <em>.
But what about italics and bold in CSS? I've seen plenty of cases of italics and bold in CSS. Would you not use italics and bold in CSS when you'd prefer <em> and <strong>? If em and strong are a thing to use, then they should also be able to be used in CSS like italics and bold. Also, there's a lot of cases where a span is used for italics/em and bold/strong.
Also, if you do change what em or strong does in CSS, then software to read an ePub that would read em/strong differently, might not do so correctly they no longer mean what the default says they do.