E-mail List Archives

RE: Section 508 Standards Compliance and Scripts

for

From: Bryce.Fields@kyvu.org
Date: Sep 5, 2003 1:41PM


Almost correct. We have an application we are now using that claims to be
Section 508 compliant. The Commonwealth of Kentucky has recently mandated
that software should be WCAG 1.0 Priority 1 compliant by Jan 1, 2004. I was
curious about two things: 1) WAS this software (and others we were looking
at) truly compliant under 508 (and apparently they are, even w/ the shady
wording...God bless loopholes, I suppose) and 2) can this software also be
considered compliant under the more clear cut Priority 1 criteria. And from
what I gather of readers opinions, clearly it fails when it comes to item 2.

Bryce Fields
Web Developer
Kentucky Virtual University
http://www.kyvu.org/

1-877-740-4357
1-502-573-1555 ext 288

"Do or do not. There is no try." -- Yoda

-----Original Message-----
From: Jon Gunderson [mailto: <EMAIL REMOVED> ]
Sent: Thursday, September 04, 2003 5:02 PM
To: <EMAIL REMOVED>
Subject: RE: Section 508 Standards Compliance and Scripts

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.
>
>
>
> > -----Original Message-----
> > From: <EMAIL REMOVED>
> > [mailto: <EMAIL REMOVED> ]
> > Sent: Thursday, September 04, 2003 3:15 PM
> > To: <EMAIL REMOVED>
> > Subject: RE: Section 508 Standards Compliance and Scripts
> >
> >
> > Section 508 is based on WAI but scattered a bit in terms of
> > Priority levels.
> > With regard to the JavaScript question, I believe that WAI is
> > a bit more
> > strict and would be more likely to reject some claims of compliance as
> > compared with Section 508. If you can achieve compliance with
> > WAI Priority
> > 2, you will be in good standing for Section 508.
> >
> > > -----Original Message-----
> > > From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ]
> > > Sent: Thursday, September 04, 2003 2:16 PM
> > > To: <EMAIL REMOVED>
> > > Subject: RE: Section 508 Standards Compliance and Scripts
> > >
> > >
> > > [from my previous post under this subject]
> > > "KYVU currently uses a CMS that makes a similar claim about
> > > its product
> > > ("content written to the screen before the page loads"). Disabling
> > > JavaScript while using that platform makes course material
> > > inaccessible.
> > > All an end user receives is a one sentence message stating
> > > that the page
> > > won't work w/ JavaScript disabled, and no other means to
> > > access the course
> > > is provided. How can this be considered compliance...???"
> > >
> > > Thanks to all for the very useful feedback to date.
> > >
> > > But...how about this question, but in regards to WCAG 1.0,
> > > priority 1. This
> > > is the standard to which the Commonwealth of Kentucky is
> > > probably going to
> > > hold their sites accountable. Would a course management
> > > system that did not
> > > display course material when JavaScript was disabled be considered
> > > compliant?
> > >
> > > Bryce Fields
> > > Web Developer
> > > Kentucky Virtual University
> > > http://www.kyvu.org/
> > >
> > > 1-877-740-4357
> > > 1-502-573-1555 ext 288
> > >
> > > "Do or do not. There is no try." -- Yoda
> > >
> > >
> > >
> > > ----
> > > To subscribe, unsubscribe, suspend, or view list archives,
> > > visit http://www.webaim.org/discussion/
> > >
> >
> >
> > ----
> > To subscribe, unsubscribe, suspend, or view list archives,
> > visit http://www.webaim.org/discussion/
> >
> >
>
>
>----
>To subscribe, unsubscribe, suspend, or view list archives,
>visit http://www.webaim.org/discussion/

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL 61820

Voice: (217) 244-5870
Fax: (217) 333-0248

E-mail: <EMAIL REMOVED>

WWW: http://cita.rehab.uiuc.edu/
WWW: http://www.staff.uiuc.edu/~jongund



----
To subscribe, unsubscribe, suspend, or view list archives,
visit http://www.webaim.org/discussion/


----
To subscribe, unsubscribe, suspend, or view list archives,
visit http://www.webaim.org/discussion/