W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2005

RE: Techniques for GL 4.2 L1 SC6

From: Loretta Guarino Reid <lguarino@adobe.com>
Date: Fri, 28 Oct 2005 17:20:44 -0700
Message-ID: <0DAF2B31FBCEB6439F63FA7F91601F7434E3AC@namail3.corp.adobe.com>
To: "Michael Cooper" <michaelc@watchfire.com>, "WAI GL \(E-mail\)" <w3c-wai-gl@w3.org>

This seems to me to be very similar to the issues for GL 4.1 L1 SC3.

The only techniques that make sense to me are 
1) the user agent takes care of this for some technologies, and the
author just needs to use that technology properly
2) program-like technologies (Windows applets, Java applets, Flash) need
to use the accessibility API to provide the notification

Loretta Guarino Reid
lguarino@adobe.com
Adobe Systems, Acrobat Engineering 

> -----Original Message-----
> From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
> Behalf Of Michael Cooper
> Sent: Wednesday, October 26, 2005 9:51 AM
> To: WAI GL (E-mail)
> Subject: Techniques for GL 4.2 L1 SC6
> 
> 
> At the Face to Face last week we decided to go to the list about
> techniques for Guideline 4.2 Level 1 Success Criterion 6 [1]: Changes
to
> content, structure, selection, focus, attributes, values, state, and
> relationships within the content can be  programmatically determined.
> 
> What we have for techniques is the following:
> 
> * Providing an event whenever a change to structure, selection, focus,
> attributes, values,
>   state, or relationships occur.
> 
>   als: Is "event" a platform-independent term?
> 
> * Pointing to external documentation that explains/shows
> 
>   Redundant with using accessibility conventions? No - if use
> accessibility features, get for free.
>   If not, need to do the things in L1 SC6
> 
>   issues: needs cleanup, needs to include info about the DOM, not
ready
> for public release
> 
>   proposed: using accessibility API of a programming language that
>   provides this functionality
> 
>   proposed: providing an event in a form that AT expects for the
> platform
>   whenever a change of structure...
> 
> 
> Please suggest techniques or ways to resolve the issues with the
> existing techniques.
> 
> Michael
> 
> [1]
http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_4.2_L1_SC_6
> 
> --- Signature ---
> 
> Michael Cooper
> Accessibility Product Manager, Watchfire
> 1 Hines Rd Suite 200, Kanata, ON  K2K 3C7  Canada
> Tel: +1 (613) 599-3888 x4019
> Fax: +1 (613) 599-4661
> Email: michaelc@watchfire.com
> Web: http://www.watchfire.com/
Received on Saturday, 29 October 2005 01:11:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:40 GMT