How to convey text that is bold as important to JAWS users
I am listing information that has some warnings attached and would like to let JAWS users know that that text is important. How would you suggest conveying text that is bold to sighted users to JAWS users?
Thanks!
Thanks!
Hi Charlie and welcome to the Forum!
I've moved your post as it rightly belongs in 'Site Building & Testing'.
To emphasise text as being important for a screenreader user, you should use the <em> tag. This doesn't make the text bold but italicises it. The point is, that it conveys importance to the user. e.g.
HTH!
I've moved your post as it rightly belongs in 'Site Building & Testing'.
To emphasise text as being important for a screenreader user, you should use the <em> tag. This doesn't make the text bold but italicises it. The point is, that it conveys importance to the user. e.g.
| Code: |
| <p>The trip planned for tomorrow will leave from the <em>south</em> entrance, and not the north as previously advertised.</p> |
Thanks. I wasn't sure where to post since this was my first time.
I tried using em but Jaws just reads the text and doesn't announce that emphasis is added. Perhaps a setting in jaws?
I tried using em but Jaws just reads the text and doesn't announce that emphasis is added. Perhaps a setting in jaws?
Well, you live and learn.
Apparently JAWS, and other screenreaders, do not support <em>.
Sorry Charlie, I've only just found this out for myself!
The Paciello Group Blog has a relevant article on this subject.
Apparently JAWS, and other screenreaders, do not support <em>.
Sorry Charlie, I've only just found this out for myself!
The Paciello Group Blog has a relevant article on this subject.
Thanks for looking and providing the link.
| Gary Miller wrote: |
| Well, you live and learn.
Apparently JAWS, and other screenreaders, do not support <em>. Sorry Charlie, I've only just found this out for myself! The Paciello Group Blog has a relevant article on this subject. |
That is a grim article. There seems to be no obvious workround.
Hacking your code to achieve a specific non-default audio effect in a specific product is wrong in at least 2 ways:
As the article states:
Keep using semantic markup. AT can choose to provide whatever is most useful for their customers.
- Presentional markup.
- Proprietary hacks.
As the article states:
| The Paciello Group wrote: |
| This is merely another example where [two] screen reader vendors are not serving their customers well. |


