<scribe> Scribe: JR

CL: Discussed with Rich
... How do you maintain UI consistency with different embedded objects...
... plus if its seamless user might not realize they are in a differnt type.

JA: SVG viewer experience, viewer couldn't be scaled
... Even though what's in the view can be expanded.
... Assume everyhting will generate DOM nodes?

CL: Is it one DOM or multiple?
... So far concentrated on keyboard issues.
... Also talked with Rich about how to expose info in SVG and MathML.

JR: The dream seems to be one harmonized experience

<jallan> cl: how is keyboard interaction harmonized between different tools

CL: But in my experience each part is made by someone different, so harmonization is difficult..

<jallan> accesskey conflict, are a problem.

<jallan> User agent or AT must negotiate keybindings

CL: Early cases of Flash+HTML showed problems.

JR: These docs seemed to assume very strong UA support or highly harmonized UA+plugins

JA: UA guidelines assumed one UA (or very tightled harmonized)

CL: Another issue...voiceXML...related to interaction between voiceXML author's expectations and AT running on top.

JA: Also WebAPI group looking at conflicting API's. "Web-API" working group

CL: Considering accessibility API's?

JA: Prob. not.

CL: DO group used to look at things at lower level.

<jallan> DOm issues: all document types have different DOM. In unix world us using the accessibility api to harmonize doms

<jallan> through ATK and ATSPI

<jallan> there is a bridge that bridges these 2 apis together to share information.

I'm back.

<jallan> Linux world is working on building this harmonization.

JR: comments on these docs can be sent back as just a list of comments

JA: Which are our (UA) probs, which are "their" probs.
... e.g. security...

JR: Is there an accessibility angle to that?

JA: In reference framework, 2.3 Link Activation, behaviour of nested hyperlinks...
... in an SVG there could be links nested inside each other.
... What's the keyboard nav for that scenario?

CL: It's a bit like a map...
... There's a default link, but how do you get ot the others?

JR: I also think 6.3.1 Two Dimensional Focus Navigation (Flat, Graphical, Joystick) is an important area to look at

<scribe> ACTION: CL to Will ask Aaron to look through this from Firefox perspecitve [recorded in http://www.w3.org/2006/01/19-ua-minutes.html#action01]

<scribe> ACTION: JA to Will come up with a list of issues for discussion on list. [recorded in http://www.w3.org/2006/01/19-ua-minutes.html#action02]

JR: Interactivity should be common throughout (ui of all containers should be the same)

JA: Object element in HTML is an example of uneven interactivity.

CL: root problem is the API's.
... Maybe one day W3C stuff will harmonize but external formats always a problem.

JR: Browsers are building in more native support...

CL: Still long way to go. But then again maybe SVG will be as full-featured as Flash someday.

<jallan> cl: java embedded within an html page, with accessibility API, then need Java Access bridge to share information. too many layers.

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

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: CL IBM JA JR Jim_Allan cklaws jallan
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Regrets: David P.
Got date from IRC log name: 19 Jan 2006
Guessing minutes URL: http://www.w3.org/2006/01/19-ua-minutes.html
People with action items: cl ja

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report