W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2005

Re: Strikethrough elements and JAWS

From: James Nurthen <jnurthen@gmail.com>
Date: Mon, 24 Jan 2005 11:27:32 -0800
Message-ID: <231078ef050124112728e47024@mail.gmail.com>
To: w3c-wai-ig@w3.org

I agree with your sentiments - however decisions like this are not
mine to make - however I can make recommendations....

Has anyone actually got this to work in JAWS? I just tried setting
what I thought were the correct settings for the following HTML:
<P>A Sheriff can employ <del>3</del><INS>5</INS> deputies. </P>


<P>A Sheriff can employ <span style="text-decoration:line-through">
3</span><span style="text-decoration:underline">5</span> deputies.

However - neither were read by JAWS. Can someone suggest some valid
HTML which would be picked up by JAWS.


On Sat, 22 Jan 2005 15:23:34 -0500, Derek Featherstone <feather@wats.ca> wrote:
> John Colby wrote:
> > [jms] <blockquote> But I guess that we really need a technique where
> >  we don;t have to fiddle with the defaults of JAWS - ad that seems
> > like a job for the manufacturer to parse stuff sensibly from square
> > 1. </blockquote>
> And John Slatin wrote:
> > Actually, I think developers should follow the specification and use
> > <del> and <ins>, etc., as they're meant to be used. It would be nice
> > if screen readers, including but not limited to JAWS, could
> > automatically switch into "proofreading" mode when they encounter
> > those elements
> I agree wholeheartedly that we shouldn't rely on tweaks to settings in
> screen readers, and I also agree with John when he suggests a "proofreading
> mode" (great idea, if nobody has already caught on to it). At the same time,
> I'd suggest that there can be cases where it makes sense to suggest some
> tweaks to users of certain types of technology.
> If I recall correctly from earlier in the thread, this is an application
> which isn't open for "general consumption". In that case, wouldn't it be
> reasonable to make suggestions as to settings that should be used by people
> using screen readers? Perhaps in an orientation guide, with a specific set
> of suggestions for creating the "optimal profile" for screen reader settings
> rather than the factory defaults. We're using that strategy for a current
> project that has a very specific audience and isn't just an informational
> web site. We are specifically calling it an orientation guide rather than
> "help" -- too often "help" is reserved for information to help you when you
> get stuck, not before you get started.
> Doing so would serve two purposes:
> 1. Enables the user to more effectively use the application that has been
> designed with semantics, standards, and accessibility in mind.
> 2. Helps the person/people using screen readers to become more effective
> with their software - not just for the application in question, but for
> everything they do. I don't think becoming more familiar with the
> capabilities of their software is a bad thing.
> Given the fact that this is an application, I'd like to think that education
> should be one of the techniques that is considered to help with
> accessibility...
> Just some thoughts,
> Derek.
> --
> Derek Featherstone     feather@wats.ca
> phone: 613.599.9784;   toll-free: 1.866.932.4878 (North America)
> Web Accessibility:  http://www.wats.ca
> Personal: http://www.boxofchocolates.ca
Received on Monday, 24 January 2005 19:28:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:30 UTC