Subject: | |
From: | |
Reply To: | * EASI: Equal Access to Software & Information |
Date: | Thu, 4 Jan 2001 10:18:37 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
----- Original Message -----
From: "Reidy Brown" <[log in to unmask]>
To: <[log in to unmask]>
Sent: January 04, 2001 9:56 AM
Subject: QUESTION: use of javascript to comply with Sect 508
Can anyone give a general explanation of the use of javascript as
defined by
section 508? As far as I can tell, it's not requiring the page to work
without javascript (like the WAIS), but simply requiring the content
that is
displayed with javascript to be readable with assistive technology.
Possible example? DHTML fly-out menu created with javascript provides
information (links). Those links must also be available to assistive
technology. Is this a reasonable interpretation?
What about things like javascript links or client-side validation
before
submitting a form? As far as I can tell, that's not disallowed by 508.
Unfortunately, the Access Board's site is down this morning, and I
didn't
download the docs to my hard drive, so I can't double check for an
explanation...
Here's the text:
(l) When pages utilize scripting languages to display content, or to
create
interface elements, the information provided by the script shall be
identified with functional text that can be read by assistive
technology.
Thanks,
Reidy
-------------------------------------------
Reidy Brown
Accessibility Coordinator/
Software Engineer
Blackboard, Inc.
1899 L. St., NW, 5th Floor
Washington, DC 20036
(202) 463-4860 x236
-------------------------------------------
|
|
|