Thread Subject: Re: 1194.22(l) scripting

From: Barrett, Don
Date: Wed, Jun 06 2007 10:50 AM

• Return to this mailing list's archives
• View all messages in this thread
• Next message in thread: None
• Previous message in thread: Peter Korn: "Re: 1194.22(l) scripting"
• Messages sorted by: Author | Thread | Date

I would be happy with that.


Don Barrett
Section 508 Coordinator
U.S. Department of Education
(202)-205-8245
= EMAIL ADDRESS REMOVED =

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
Hoffman, Allen
Sent: Wednesday, June 06, 2007 8:09 AM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] 1194.22(l) scripting

Don and Peter:

I agree on both sides here.

Don is probably correct that some may feel they don't need to meet
provisions because they don't see the word scripting, but Peter is right
that we have defined the responsibility clearly no matter how the
functionality is implemented. So, we may be able to tweak the language
to just include, "including but not limited to scripting languages", and
make us all feel happy?



Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
Barrett, Don
Sent: Tuesday, June 05, 2007 5:30 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] 1194.22(l) scripting

I am worried that if scripts are not specifically mentioned, vendors who
are looking for a way out due to time and budget constraints will argue
that they are not covered. Perhaps I should review the standards you
mention, but I really want an ironclad assurance that scripts are
included in what is already there if we leave them out of the proposals
Andy cited.


Don Barrett
Section 508 Coordinator
U.S. Department of Education
(202)-205-8245
= EMAIL ADDRESS REMOVED =

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter
Korn
Sent: Tuesday, June 05, 2007 5:25 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] 1194.22(l) scripting

Hi Don,

We have a general provision on applications, and another on content,
that I think together cover this scenario. It doesn't matter whether
the (web) content was created by a script or not.

As to this example you propose, as it only singles out one aspect of
what needs to be provided (the functional text) I think it muddies the
water rather than helping things.


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.

> I would support adding the scripting requirement as stated in the
cited
> examples.
>
> "Proposal to add: For example, when pages utilize scripting languages
> to display content, or to create interface elements, the interactive
> functionality is operable using only the keyboard.
>
> Proposal to add another example after the frames example: 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."
>

• Next message in Thread: None
• Previous message in Thread: Peter Korn: "Re: 1194.22(l) scripting"