Thread Subject: Re: 22(l) and 22(m) Scripts, applets,and plug-ins

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: Gregg Vanderheiden
Date: Tue, Feb 20 2007 9:35 AM

Did you mean both as requirements or "do one or the other"

Or did you mean "if A do B. if C do D"


???


Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.



> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi Snow-Weaver
> Sent: Tuesday, February 20, 2007 9:30 AM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] 22(l) and 22(m) Scripts,
> applets, and plug-ins
>
> But the "functional text" requirement is not good enough for
> the new W3C ARIA standard. For that you need WCAG 4.1.2. What
> if we kept the current
> 508 script provision requiring funcitonal text and added in
> the WCAG 4.1.2 provision?
>
> Andi
>
>
>
>
>
> "Hoffman, Allen"
>
> <Allen.Hoffman@dh
>
> s.gov>
> To
> Sent by: "TEITAC Web/Software
> Subcommittee"
> teitac-websoftwar
> < = EMAIL ADDRESS REMOVED =
> = EMAIL ADDRESS REMOVED = >
>
> itac.org
> cc
>
>
>
> Subject
> 02/20/2007 08:39 Re:
> [teitac-websoftware] 22(l) and
> AM 22(m) Scripts,
> applets, and
> plug-ins
>
>
>
> Please respond
>
> to
> Web/Software
>
> Subcommittee
>
> <teitac-websoftwa
>
> = EMAIL ADDRESS REMOVED =
>
> g>
>
>
>
>
>
>
>
>
>
> I agree with Don's assessment, but what will help is a clear
> definition "scripts" "applets", and "plug-ins". All of these
> are platform think.
>
>
>
>
> Allen Hoffman -- 202-447-0303
> Technology
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Don Subcommittee applets,and concern over the homogenious
> act like has are are with
>
> Applets and plug-ins, on the other hand, are software, and
> must meet a different test.
> successful in our
> by requiring
> the
> event
> encountered
> AT have
> and
> testability will go away, and any developer worth to explain
> how their scripts satisfy the in some theoretically plausible
> have had all along for functional text was applicability.
> The notion web developers win-win must
>
> Concepts such as "programmatically determined and
> programmatically set,"
> "notification of changes to these items is available to user
> more intellectually satisfying because they have global
> theoretically cover more scenarios. But 508 is only as good
> testable; take away its testability for the sake of
> theoretical the 508 the the Federal level is designed to
> support the assumption of unless someone can clearly show
> that a given product standards. If we make it hard to prove
> will always be assumed.
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Andi = EMAIL ADDRESS REMOVED =
> 22(m) Scripts, applets, and
> recommendation for 22(l) scripts and 22 (m) applets and plug-ins.
> and for applets and
> In contrast,
> is static
> must
> discussed
> with a
> of
> order to determine whether this is the case, Jim Thatcher and
> Earl created a mapping of all of the 1194.21 requirements to WCAG [1].
> for
>
> 21(b) Applications shall not disrupt or disable activated
> features of products that are identified as accessibility
> features, where are developed and documented according to
> industry also shall not disrupt or disable activated features
> of any that are identified as accessibility features where
> the programming interface for those accessibility features
> has by the manufacturer of the operating system and is developer.
> applications
> mean we
> plug-ins
> plug-ins?
>
> 1194.21(c) A well-defined on-screen indication of the current
> focus provided that moves among interactive interface
> elements as the changes. The focus shall be programmatically
> exposed so that technology can track focus and focus changes.
> ourselves. Some feel that this is a user types of content,
> like Flash, provide this. We have a not reach consensus on
>
> 1194.21(f) Textual information shall be provided through
> operating functions for displaying text. The minimum
> information that shall available is text content, text input
> caret location, and text Is this really an issue for applets
> and plug-ins? If so, then we need making a proposal for an
> additional requirement in WCAG 2.0.
> Applications shall not override user selected contrast and
> and other individual display attributes.
> to these features of the operating
> with the current 508 standard
> [3]
>
> We also have the issue user agent issue of keyboard operation
> with entering and exiting applet or plug-in content with the
> few other issues, as identified in the mapping table, most
> already working on proposals to address. But we can't go
> 508 refresh. So, if we want to recommend that 508 take WCAG
> 2.0 for scripts, applets, and plug-ins, we issues and also
> recommend adding the
> 508:
> be
> be
> programmatically
> available to user
>
> Comments?
>
> [1] http://teitac.org/wiki/Web_and_Software:_mapping
> [2] http://teitac.org/wiki/Web_and_Software:_Web_Gaps#Focus_Indicator
> [3]
> http://teitac.org/wiki/Web_and_Software:_Web_provisions#22.28l
> .29_.26_22
> .28m.29
> mailing list
> http://list.teitac.org/mailman/listinfo/teitac-websoftware
>

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University