WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: RE: Section 508 Standards Compliance and Scripts

for

Number of posts in this thread: 1 (In chronological order)

From: Jon Gunderson
Date: Thu, Sep 04 2003 3:06PM
Subject: RE: Section 508 Standards Compliance and Scripts
No previous message | No next message

Karl,
I think the issue in this case is that a particular developer has an
existing application that generates content using Javascript write
statements. It seems to be a common practice for some developers. They
are now trying to retrofit their application to be section 508 compliant
and current section 508 have a vague functional test for the accessibility
of this implementation technique.

Section 508 says
(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.

Section 508 does not say which assistive technologies, but I think the
flavor most people think of is screen readers. It is not clear how much
testing the author needs to do, but the most popular testing is with IE and
JAWS.

These developers are certainly not use accessible design practices, but are
trying to at least meet some level of accessibility through repair
techniques to meet section 508 requirements. Some people suggested that
the developers publish a compliance statement so that people know what type
of testing the developer did to test for section 508 compliance.

Jon



At 04:15 PM 9/4/2003 -0400, you wrote:
>Forgive me if I am off base. I am coming into this conversation late.
>IMO, a site is a complete accessibility failure if the content is not
>usable for persons with JavaScript off/ with browsers that do not
>recognize JavaScript.
>
>There should be no reason for important content to be reliant on
>client-side scripting.
>Think of it in these terms: is the content understandable to the same or
>reasonable level regardless of technology used to access it? If yes,
>then it is accessible. If no, then it is not.
>
>One should not think of accessibility in terms of "Am I satisfying _______
>guideline?", but rather "Can all people use this?"
>
>Karl L. Groves, Certified Master CIW Designer
>E-Commerce Manager
>NASA Federal Credit Union
>500 Prince Georges Blvd.
>Upper Marlboro, MD 20774
>
>301-249-1800 ext.497
>Fax: 301-390-4531
>
>Opinions expressed in this e-mail represent only myself and are not in any
>way to be taken as the words or opinions of my employer.
>
>
>
> >