W3C

- DRAFT -

UAWG conference call

19 Oct 2006

See also: IRC log

Attendees

Present
Jim_Allan, Jan_Richards, cklaws
Regrets
Chair
JAllan
Scribe
JR

Contents


 

 

<jallan> scribe: JR

9.2 Provide user interface focus (P1)

CL: IBM sees UI as diff from content.
... UI handled better by MSAA etc

JR: (pre-CL comments) read from email (http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0010.html)
... Might we split like ATAG?

JA: Like that

CL: Also split content into static and dynamic
... OS widget sets have solved many problems...
... But firefox diff because it is created by XUL...not OS widgets

JA: 7.1 covers a lot of this
... UI focus does seem visual to me.

JR: THat's also in 10.2

JA: Should we be bold and assume 9.2 is done.

JR: Maybe some things could be rolled together?

HR: e.g. "Provide a user-controlled (content|user interface) focus"

HR=JR

CL: Should add that if creating a CUSTOM UI you still need to satisfy.

<jallan> ACTION: ja add technique about if creating a CUSTOM UI you still need to provied a user interface focus [recorded in http://www.w3.org/2006/10/19-ua-minutes.html#action01]

CL: Also we talked last week about AJAX etc widgets...

JA: Might some of the UI be created with AJAX etc?

JR: Maybe if UA stuff added to content in a larger wrapper.

CL: Looked at that.

<jallan> JR: could a UA crate UI panes to provide addtional funtionality (history list) that was created in AJAX

JR: Maybe that would be considered content?

<jallan> CL: its a lot of work and it is very slow.

CL: Confusing since code may be on server.
... That's what Google is doing - eg office apps as web pages that edit other docs

<jallan> JR: go to a website, that provide a user interface to manipulate web content in novel ways, then this shell that renders in a client UA becomes a UA

CL: ALl controls in Web page, not in browser

JR: Is this USER AGENT content or CONTENT able to browse

CL: COmplicated when widgets pulled into content from elsewhere
... Complicates 9.2
... Flash is also like this.
... Flash player would have to implement MSAA
... Content layer is developer who doesn't need to know C++ etc, instead uses markup, scripting etc

JR: Had same plethora of tools in ATAG dev

<jallan> CL: UA is conveying information about widgets, tools, and functionality, CONTENT is more about the actual information being conveyed

CL: Long term gol to separate content from interaction from presentation

JA: Interested in CL's "layers diagram".

JR: Me too.

CL: Even more complicated when browser runs in Java or Eclipse - they write to Eclipse - then Eclipse writes to platform.access API

JA: So they have to trust Eclipse...

CL: Eclipse has own widgets paired to lower native widgets with written in accessibility...
... But custom widgets in eclipse requires the eclipse custom accessibility that then maps back to native platform
... And when use standard widget keyboard access is built in - but Firefox doesn't understand DOJO widget - so accesskeys used

Ended early

Summary of Action Items

[NEW] ACTION: ja add technique about if creating a CUSTOM UI you still need to provied a user interface focus [recorded in http://www.w3.org/2006/10/19-ua-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/10/19 18:51:31 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.127  of Date: 2005/08/16 15:12:03  
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, Jan_Richards, cklaws
Present: Jim_Allan Jan_Richards cklaws
Got date from IRC log name: 19 Oct 2006
Guessing minutes URL: http://www.w3.org/2006/10/19-ua-minutes.html
People with action items: ja

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


[End of scribe.perl diagnostic output]