W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2008

User Agent Teleconference for 24 July 2008

From: Jim Allan <jimallan@tsbvi.edu>
Date: Wed, 23 Jul 2008 12:55:14 -0500
To: <w3c-wai-ua@w3.org>
Message-ID: <007d01c8eced$4249b470$c6dd1d50$@edu>

Chair: Judy Brewer & Jim Allan
Date: Thursday, 24 July 2008
Time: 2:00-3:30 pm Boston Local Time, USA (19:00-20:00 UTC/GMT)
Call-in: Zakim bridge at: +1-617-761-6200, code 82941# for UK use
IRC: sever: irc.w3.org, port: 6665, channel: #ua.
Scribe schedule and scribing help: http://www.w3.org/WAI/UA/scribing.html 

1. Regrets, agenda requests, comments?  

2. Participant schedule for remainder of July, August 

3. Schedule for Publication of next draft (and related Charter issues)
4. Keyboarding refocus: 
In UAAG20 there are 8 guidelines (4.1 - 4.8) related to operation of the
user agent. We are currently working on 4.1. It is the most general of the
guidelines related to Principle 4 - Ensure that the user interface is
operable. Please pay close attention to the references to UAAG10. They can
provide insight and orientation as to how these Success Criteria were
generated. Keyboard operation is a non-trivial topic. We have put much
effort into getting things right. Thank-you.

UAAG20 is a major overhaul of UAAG10. As such, the working group decided to
follow and extend the structure established by WCAG and ATAG. We have
reorganized all UAAG10 checkpoints into UAAG20's 5 principles
    * PRINCIPLE 1. Follow applicable specifications and conventions
    * PRINCIPLE 2. Facilitate access by assistive technologies
    * PRINCIPLE 3: Ensure that the user interface is perceivable
    * PRINCIPLE 4. Ensure that the user interface is operable
    * PRINCIPLE 5: Ensure that the user interface is understandable 

We have many new people on the group. We have also been extremely focused on
one narrow topic. It seems we were stuck. Last week, Jan, Kelly, Jeanne, and
Jim took an action item to spend some time reviewing the current keyboard
work and come up with some 

Basic Keyboard Principles for use as a foundation. They are listed below. 

A. you can navigate to, operate and activate every function from the
keyboard - move/jump, select (any/all) 

B. you can activate certain important functions with simple actions. 

C. you and your AT knows what keys (functions) work in the given
viewport/interface - there are meta content available (visually and
programmatically) to let you know what keys are available - under line
characters on menus and buttons, grayed out items, links are
blue/underlined/mouse_cursor_changes, short-cut keys delineated 

D. user can change keys used to perform functions 

E. user controls activation of any actionable items

>From the above we created a New Success Criteria list -
In the process we discovered that some Success Criteria are already in place
elsewhere in UAAG20.

It was time to back up a bit and look at the forest. I reviewed UAAG10 and
UAAG20 in relation to our current work. The results can be seen at

I suggest the working group review the Thrashing document. Let us focus our
attention on the 6 remaining Success criteria, agree on wording, levels, and
Move On.

For review:
Old success criteria list

UAAG20 keyboard guideline


Jim Allan, Webmaster & Accessibility Coordinator
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, 23 July 2008 18:00:39 UTC

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