Log in   Register a New Account

Accessify Forum - Discuss Website Accessibility

New to the forum?

Only an email address is required.

Register Here

Already registered? Log In

Currently Online

No registered users are online.

How to convey text that is bold as important to JAWS users

Reply with quote 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!
Reply with quote Hi Charlie and welcome to the Forum! Smile

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>
HTH!
Reply with quote 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?
Reply with quote 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.

Sad
Reply with quote Thanks for looking and providing the link.
Reply with quote
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.

Sad


That is a grim article. There seems to be no obvious workround.
Reply with quote Hacking your code to achieve a specific non-default audio effect in a specific product is wrong in at least 2 ways:
  1. Presentional markup.
  2. Proprietary hacks.
Individual products can choose to render however they want - that's the whole point of semantic markup. Other products may choose to render it differently, such as Braille output adding emphasis marks or Lynx applying a colour.

As the article states:
The Paciello Group wrote:
This is merely another example where [two] screen reader vendors are not serving their customers well.
Keep using semantic markup. AT can choose to provide whatever is most useful for their customers.

Display posts from previous:   

All times are GMT

  • Reply to topic
  • Post new topic