RE: User Agent Teleconference for May 10 2007

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.

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 13:41:52 UTC