WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Strikethrough Content with Screen Readers

for

From: Hoffman, Allen
Date: Nov 22, 2010 7:39AM

Don't focus on the screen reader, you are not in control of that for the
end-user.
Focus on coding in consistent fashion. If you need users to know
something specific about the pricing by using the specific tag, identify
it textually also. This will be interpretable by all until a more
supported method based only on the tagging becomes available.



-----Original Message-----
From: Randall Pope [mailto: <EMAIL REMOVED> ]
Sent: Friday, November 19, 2010 4:09 PM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] Strikethrough Content with Screen Readers

Vivek and all,

Using different tones to read the different prices, is no help for the
people who cannot hear, mainly the deaf-blind people who depends solely
on
braille display to read the web pages.

Simple html markup is the best way to go to make it accessible. As for
the
strike out, i think it would be best to use good proper language writing
to
address the strike out issue.

<rant>Why does most developers focus accessible issues for the hearing
blind only and not all people with disabilities? We have a good number
of
senior citizens who are having issues with their vision and hearing
losses.</rant>

<Jared>Thank for the humor thoughts. Grinning</Jared>

Randall Pope
American Association of the Deaf-Blind (AADB)

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of
<EMAIL REMOVED>
Sent: Friday, November 19, 2010 9:46 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] Strikethrough Content with Screen Readers


While reading the strikethrough element, JAWS does not recognize it
differently and thus user is not informed about the striked content.

One way to solve this is, change JAWS settings, so that it reads it in
different tone.

Eg: New Price<del>30</del>20$. In this case, if JAWS settings are not
done, it reads it as "New Price 3020$". This is incorrect information.
If we change the settings, JAWS reads 30 in different tone - high pitch
voice and the user will come to know about the content. Is there any way
the developers of the content can do anything, so that the screen reader
user do not need to change the settings and still get the correct
information?



Is there any other screen reader apart from JAWS, which takes care of
such issues?



peace, veiky



This e-mail and any files transmitted with it are for the sole use of
the
intended recipient(s) and may contain confidential and privileged
information.
If you are not the intended recipient, please contact the sender by
reply
e-mail and destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding,
printing or copying of this email or any action taken in reliance on
this
e-mail is strictly
prohibited and may be unlawful.