WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: <strong> vs <em>

for

From: Hunt, Jan
Date: Feb 12, 2007 1:20PM


John Foliot wrote:
Backwards compatibility. It is preferred that you use the <em> and
<strong>
elements when required, but because of legacy documents the screen
readers
(for now) will read them essentially the same.

Sorry, I didn't make myself real clear on the original question. What I
should have said is "why is it when I use JAWS or HomePage Reader, I
hear no difference in words marked up with any of these tags <i> <em>
<b> <strong> from the basic paragraph text." There is no emphasis or
stronger voice inflections for any of them. Actually, I would never know
the tags existed within my web page had I not coded them myself.

Do you-all hear a difference in the pronunciation of text marked up with
any of these tags?

Thanks!

-----Original Message-----
From: John Foliot - Stanford Online Accessibility Program
[mailto: <EMAIL REMOVED> ]
Sent: Monday, February 12, 2007 11:03 AM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] <strong> vs <em>

Hunt, Jan wrote:
> Why is it that when I use JAWS or HomePage Reader, I detect no
> difference in <em>, <i>, <b> or <strong>?

Backwards compatibility. It is preferred that you use the <em> and
<strong>
elements when required, but because of legacy documents the screen
readers
(for now) will read them essentially the same.

JF



>
> -----Original Message-----
> From: Darian Glover [mailto: <EMAIL REMOVED> ]
> Sent: Saturday, January 27, 2007 1:36 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] <strong> vs <em>
>
> <em> renders as emphasized text. <strong> renders as strong
> emphasized text.
>
>
> Darian.
>
>
> On 1/22/07, Gary Williamson < <EMAIL REMOVED> > wrote:
>> Generator Microsoft Word 11 (filtered medium) I' ve heard on the
> grapevine that <strong> shouldn' t be used to emphasise text for
> screen readers as it shouts a word rather than emphasises it! If this
> is the case what can be used as an alternative? I' ve heard <em> can
> be used instead, however, I' m not sure how?
>>
>> Regards
>>
>> Gary
>>