W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2007

Re: User Agent Teleconference for May 10 2007

From: Jan Richards <jan.richards@utoronto.ca>
Date: Wed, 09 May 2007 11:22:18 -0400
Message-ID: <4641E72A.5010001@utoronto.ca>
To: Al Gilman <Alfred.S.Gilman@IEEE.org>
CC: David Poehlman <poehlman1@comcast.net>, WAU-ua <w3c-wai-ua@w3.org>, WAI-AUWG List <w3c-wai-au@w3.org>

Hi Al,

(I've cc'd the AUWG list as this discussion is relevant to them)

I may not understand exactly what you mean, but here's my thinking...

It's not the "content" that needs to be perceivable, it's the user 
interface of the software (sometimes augmented by an AT), some of which 
is independent of the "encoded content" (i.e. the software "chrome") and 
some of which is built from the "encoded content" (i.e. the "content 
display"). In either case, the concept of "perceivable" seems ok to me.

Cheers,
Jan


Al Gilman wrote:
> 
> At 8:42 AM -0500 9 05 2007, Jim Allan wrote:
>> David,
>> I would put the fuzzy ones in all appropriate categories. I am not 
>> sure what
>> you mean by "conforming to wcag 2.0."  One of our requirements is to 
>> align
>> UAAG with the broad concepts, set out by WCAG and ATAG, of perceivable,
>> operable, understandable, and AT friendly.
> 
> I suggest that the group consider the following issue with the 
> 'perceivable' notion.
> 
> The problem is that saying the 'content' must be 'perceivable'
> conflates two forms or representations of the content: the user
> experience or 'rendered content' and the wire format or 'encoded
> content.' The user agent requirements are all about managing the
> transformation between these two interfaces and the representations
> in each. So the 4-way split used by WCAG doesn't fit either ATAG or
> UAAG in this area. It hides the distinction from which UAAG and ATAG
> start.
> 
> Al
> 
>>
>> Jim
>>
>>>  -----Original Message-----
>>>  From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org]On
>>>  Behalf Of David Poehlman
>>>  Sent: Tuesday, May 08, 2007 10:31 AM
>>>  To: jimallan@tsbvi.edu; WAU-ua
>>>  Subject: Re: User Agent Teleconference for May 10 2007
>>>
>>>
>>>
>>>  Jim,
>>>
>>>  How we deal with the fuzzy ones?  some may cover more than one 
>>> catagory?
>>>
>>>  I guess the idea here is to confirm to wcag 2.0?  This makes sense 
>>> from a
>>>  pragmatic standpoint by may not work well in practical terms.
>>>
>>>  ----- Original Message -----
>>>  From: "Jim Allan" <allanj@tsbvi.edu>
>>>  To: "WAU-ua" <w3c-wai-ua@w3.org>
>>>  Sent: Monday, May 07, 2007 5:08 PM
>>>  Subject: User Agent Teleconference for May 10 2007
>>>
>>>
>>>
>>>  W3C User Agent Teleconference for May 10 2007
>>>  -------------------------------------------------------------
>>>  Chair: Jim Allan
>>>  Date: Thursday, May 10 2007
>>>  Time: 2:00-3:00 pm Boston Local Time, USA (19:00-20:00 UTC/GMT)
>>>  Call-in: Zakim bridge at: +1-617-761-6200, code 8294#
>>>  for UK use 44-117.270-6152
>>>  IRC: sever: irc.w3.org, port: 6665, channel: #ua.
>>>  -------------------------------------------------------------
>>>
>>>  1. Restructure current guidelines and provisions to fit new model
>>>
>>>  - Perceivable: able to be noticed by a user through one or more 
>>> renderings
>>>  provided by the base user agent, its extensions, or assistive 
>>> technologies
>>>
>>>  - Operable: able to be manipulated by a user through one or more input
>>>  devices recognized by the base user agent, its extensions, or assistive
>>>  technologies
>>>
>>>  - Understandable: able to be comprehended by a user through one or more
>>>  intelligible renderings provided by the base user agent, its
>>>  extensions, or
>>>  assistive technologies
>>>
>>>  - Access system friendly: able to be viewed and controlled
>>>  programmatically
>>>  by extensions to the base user agent and assistive technologies using
>>>  standard APIs (e.g. DOM, MSAA, Assistive Technology-Service Provider
>>>  Interface, UA, UIA)
>>>
>>>  2. Review ISO/IEC JTC 1 Special Working Group on Accessibility
>>>  (SWG-A) "User
>>>  Needs Summary (UNS)"
>>>  that lists different accessibility needs for people with disabilities.
>>>
>>>  - www.tsbvi.edu/technology/uawg/userneeds-mapping_UAAG.zip
>>>  This file already has a preliminary mapping and comments (Thanks Shadi)
>>>  - map UAAG checkpoints and guidelines to User Needs Summary
>>>  - use review and mapping to ensure UAAG Requirements document is 
>>> complete.
>>>
>>>
>>>  Please send RSVP or additional agenda items to the list.
>>>
>>>
>>>  Jim Allan, Webmaster & Statewide Technical Support Specialist
>>>  Texas School for the Blind and Visually Impaired
>>>  1100 W. 45th St., Austin, Texas 78756
>>>  voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
>>>  "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>>>
>>>
>>>
>>>
> 
> 
Received on Wednesday, 9 May 2007 15:22:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:35 UTC