Thread Subject: Re: 1194.22(l) scripting
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Peter Korn
Date: Tue, Jun 05 2007 3:30 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Barrett, Don: "Re: 1194.22(l) scripting"
- Previous message in thread: Barrett, Don: "Re: 1194.22(l) scripting"
- Messages sorted by: Author | Thread | Date
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: Barrett, Don: "Re: 1194.22(l) scripting"
- Previous message in Thread: Barrett, Don: "Re: 1194.22(l) scripting"
WebAIM is an initiative of:
