<scribe> Scribe: JR

All: Welcome back to Jim.

Review Acton items

JA: Still working on them.
... Aout use cases - did some reading - KF seemed interesting - CL and PP seemed cool to idea of putting use cases in req doc
... Some other req docs have them and some don't
... But didn't make much headway

CL: Can be helpful in specific domains (e.g. rich document naviagation) but takes time to think through
... Seems we are going backwards to do use cases after decide what we are doing...
... Maybe do use cases for things people would have a hard time with

http://www.tsbvi.edu/technology/uawg/UA_requirements-22feb07.html

<AllanJ> JR: question. anything in requirements document that is confusing?

<scribe> ACTION: All to Look at requirements document to see if anything needs a use-case type example as a justification. [recorded in http://www.w3.org/2007/04/05-ua-minutes.html#action01]

Define "core" or "base" user agent functionality.

JA: Do we have enough in the requirements doc?...

CL: Still going to be gray areas - eg. keyboard navigation
... Can be author, browser, plugin.

JA: what about alt from keyboard.

<AllanJ> CL: dojo work now have interactive tooltips

<AllanJ> PP: is a dynamic tooltip still a tooltip

<AllanJ> CL: they function more like a dialog box, but there is naming confusion

All: Discussion of tooltips

CL: Lots of problems figuring out focus

<AllanJ> CL: keyboard focus in AJAX, is it the same kind of focus event as a mouse

<AllanJ> CL: how to communicate to the user that something popped up

<AllanJ> JR: user agent provides access to tooltip (alt, title) from the mouse but not keyboard

<AllanJ> ...but new widgets (ajax) have problems

<AllanJ> CL: working on this from the mouse, keyboard access is addition issue

PP: Problem whenever algorithms, controls are rebuilt over and over

JR: Getting philosophical...

CL: Keystrokes being competed for with ATs

PP: In Linux, Desktop, keyboard manager etc can eat certain strokes

<AllanJ> CL: web applications are apps within apps, the UA will grab keys first, or screen reader will get first, OS may also grab key before it gets to webapp

JA: Back to core stuff...
... Just leave open for now and hash it out later.

?

JA: We talk about modularization...
... Browsers, extensions, ATs

CL: Some things in base uaag won't be done by base browsers - e.g. keyboard nav to mouseovers will never be adopted

JA: CSS stuff up to author
... Maybe leave to authors
... DOJO etc removes control from browsers
... Hearing we should leave generic statement for later

CL: Yes
... But still thing it will be tricky without relying more on ATs, extensions
... When author we have to rely on WCAG

JA: Think they have lots in there

<scribe> ACTION: All to Review www.tsbvi.edu/technology/uawg/UA_requirements-22feb07.html [recorded in http://www.w3.org/2007/04/05-ua-minutes.html#action02]

<AllanJ> ACTION: JA ping JB Charter [recorded in http://www.w3.org/2007/04/05-ua-minutes.html#action03]

JA: Next week will get new version out - let's try to get this polished and out by end of April
... THen I will find out about making a recruitment announcement

This is scribe.perl Revision: 1.128  of Date: 2007/02/23 21:38:13  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: JR
Inferring ScribeNick: JR
Default Present: Jim_Allan, JR, cklaws, parente
Present: Jim_Allan JR cklaws parente
Got date from IRC log name: 5 Apr 2007
Guessing minutes URL: http://www.w3.org/2007/04/05-ua-minutes.html
People with action items: all ja

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.