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

RE: Section 508 Question on Javascript - Section 1194.22, Paragraph (l)

From: Fitzgerald, Jimmie <Jimmie.Fitzgerald@jbosc.ksc.nasa.gov>
Date: Wed, 14 Feb 2001 09:33:21 -0500
Message-Id: <F89C8E35B2B4D111983F0000F84A12770494CEFC@kscmbs42.ksc.nasa.gov>
To: w3c-wai-ig@w3.org
As I've said before, we are more concerned here with 508 than we are with
WAI from the W3C.  With that in mind...

Does anyone have a page/site/snippet of code demonstrating JavaScript or
VBScript for accessibility?

I'd like to see a page with DHTML writing some dynamically created content
with a script and an explanation of how and why that isn't accessible.  I'd
then like to see the same page made accessible without sacrificing the DHTML
portion of it.  If that can be done.

I've seen lots of talk about this and the 508 is not clear on it at all but
I've not seen anyone post url's to examples or anything like that.  Maybe I
just missed it?

I am all for accessibility but unless I can see some hard evidence related
to script issues such as the one I am asking for here, I'll be inclined to
continue scripting my little heart out.  I suppose I am failing to get the
point on why Lynx or Script-less browsers are considered in the arena of the
ADA.  American Disabilies Act right?  Not BDA (Browser Disability Act).
Sorry if I sound a little insensitive here, not trying to be.  Just confused
on all this talk about browsers.  Aren't we trying and really only trying to
make sites accessible to *people* with disabilities?  Thought I had a clue
about all this last week and this week, I am feeling pretty stupid about it
all.



Jim Fitzgerald

-----Original Message-----
From: Gregg Vanderheiden [mailto:gv@trace.wisc.edu]
Sent: Wednesday, February 14, 2001 9:00 AM
To: w3c-wai-ig@w3.org
Subject: RE: Section 508 Question on Javascript - Section 1194.22,
Paragraph (l)


Hi Graham
Here is the answer from Doug Wakefield at the Access Board  who put the
regulations together
With his permission I am reposting here  and on the SEC508 list


Gregg



Hello Gregg,

In response to the question on the list concerning functional text in
scripts:

When a script has no associated text or label, the screen reader often reads
some content of the script itself in a jumble of letters and words. We have
chosen not to forbid the use of scripts, by rather to require that script
functions provide text that will accurately tell a user the purpose of the
script or action.

Although there are some event handlers in JavaScript's that can pose some
tricky access problems, the bigger problem is the manner in which scripts
write to the screen.

Doug Wakefield


-- ------------------------------
Gregg C Vanderheiden Ph.D.
Professor - Human Factors
Depts of Ind. and Biomed. Engr. - U of Wis.
Director - Trace R & D Center
Gv@trace.wisc.edu, http://trace.wisc.edu/
FAX 608/262-8848
For a list of our listserves send "lists" to listproc@trace.wisc.edu


 -----Original Message-----
From: 	w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]  On
Behalf Of Graham Oliver
Sent:	Monday, February 12, 2001 2:56 PM
To:	w3c-wai-ig@w3.org
Subject:	Section 508 Question on Javascript - Section 1194.22,
Paragraph (l)

Hi
I have tried to get to some sort of understanding of
this on the Section 508 list at Trace, but am still in
the land of confusion!

The thread starts here
http://trace.wisc.edu:8080/guest/archives/SEC508/sec508.0102/msg00000.html

I have been asked to write an article on accessibility
which covers Section 508 so would like to give a
reasonable interpretation of this regulation.

Anyone care to have a go?

Cheers
Graham Oliver

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year!  http://personal.mail.yahoo.com/
Received on Wednesday, 14 February 2001 09:35:04 GMT

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