- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Thu, 03 May 2007 13:28:24 -0400
- To: WAU-ua <w3c-wai-ua@w3.org>
My preliminary thoughts on the split: PERCEIVABLE: 1.3 2.1 2.2 2.3 2.4 (parts of) 2.5 2.6 2.7 2.9 2.10 3.1 3.2 3.3 3.4 3.5 3.6 4.1 4.2 4.3 4.6-4.14 12.1 OPERABLE: 1.1 1.2 2.4 (parts of) 5.1 5.2 5.3 5.4 7.1 7.2 7.4 9.1-9.10 10.1-10.7 11.1-11.7 12.3 UNDERSTANDABLE: 2.8 4.4 (could also be considered PERCEIVABLE) 4.5 (could also be considered PERCEIVABLE) 5.5 7.3 12.2 12.4 12.5 ASSISTIVE TECH FRIENDLY: 6.1-6.10 8.1 8.2 Cheers, Jan Jim Allan wrote: > The Meeting is actually today, Thursday May 3 > >> -----Original Message----- >> From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org]On >> Behalf Of Jim Allan >> Sent: Wednesday, May 02, 2007 5:14 PM >> To: WAU-ua >> Subject: User Agent Teleconference for May 2 2007 >> >> >> >> W3C User Agent Teleconference for May 2 2007 >> ------------------------------------------------------------- >> Chair: Jim Allan >> Date: Thursday, May 2 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. >> >> - http://www.jtc1access.org/documents/swga_212.zip >> - 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 Thursday, 3 May 2007 17:28:27 UTC