Quote:
Originally Posted by JSWolf
... Programs reading a book won't be doing anything different with <em> and <strong> then <i> and <b>.
|
Where, may I ask, did you get that idea? Is it wishful thinking on your part, or is it based on an exhaustive study of text-to-speech devices/apps???
You are, and have always been (AFAIR), thinking of <i>/<b> <em>/<strong> as purely visual presentations. You consistently ignore other functions - I suppose because they are not functions of
your device. No matter how many times people point this out to you, you continue to ignore the non-visual applications of <em>/<strong>...
bookman156 brings up valid points, and links to references, and you simply say 'Sorry, but both links are wrong.'...talk about putting your head in the sand... 'those links are wrong because I think they are wrong' doesn't advance your argument.
Perhaps you could post a link to an accessibility standard, or to a text-to-speech standard, that says "We will no longer read emphasized, or strong, text in any way different than the rest of the words on the page, so stop using them." ~rotsa ruck