W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2008

RE: JavaScript and Screen Readers

From: Ryan Jean <ryanj@disnetwork.org>
Date: Tue, 19 Aug 2008 13:33:46 -0400
To: "'Benjamin Hawkes-Lewis'" <bhawkeslewis@googlemail.com>
Cc: "'David Woolley'" <forums@david-woolley.me.uk>, <w3c-wai-ig@w3.org>
Message-ID: <E1KVV7Z-00016v-NM@bart.w3.org>

This is what I'm trying to do. Let's say you had the following text on a
page:

The boy woke up. He kissed his dad. He helped his dad get ready for work.

Now, that is readable by a screen reader. Below that is a link which
activates the "document.write()" which re-writes the page to:

He kissed his dad.

This however is not readable. Now, it still falls under the W3C guidelines
as it is readable the first time around, but how do I get it to read the
second time, after the link has been clicked? The only way I figured out so
far is to put it inside a textarea tag. But the issue there is you lose all
HTML coding.

Sincerely,
Ryan Jean
Assistant IT Specialist
The Disability Network
Flint, MI


-----Original Message-----
From: Benjamin Hawkes-Lewis [mailto:bhawkeslewis@googlemail.com] 
Sent: Tuesday, August 19, 2008 10:53 AM
To: Ryan Jean
Cc: 'David Woolley'; w3c-wai-ig@w3.org
Subject: Re: JavaScript and Screen Readers

Ryan Jean wrote:
> No, it will read the alt but not standard text.

Without a test case, I'm still not precisely sure what you mean.

> And you are right about forcing it. It's the only way I could figure out
to
> still reload new information and have JAWS read it, inside the textarea
tag.

This Juicy Studio article describe a way to force JAWS to update its 
buffer with a less drastic hack:

http://juicystudio.com/article/improving-ajax-applications-for-jaws-users.ph
p

--
Benjamin Hawkes-Lewis
Received on Tuesday, 19 August 2008 17:36:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:28 GMT