<scribe> Scribe: Andi

bug 7101 http://www.w3.org/Bugs/Public/show_bug.cgi?id=7101

DB: aria-owns created so that complex grids could be supported which need to be able to specify more than one parent.

<scribe> ACTION: Cynthia to look at how complex grids work in IE. It may have another way of handling the issue of multiple parents. [recorded in http://www.w3.org/2010/03/30-aapi-minutes.html#action01]

DB: Another option is to deprecate aria-owns but it's already deployed in widget sets. Existing implementations could be made to work like aria-controls or aria-flowto.

<scribe> ACTION: Cynthia and David to follow up via e-mail and include Rich. [recorded in http://www.w3.org/2010/03/30-aapi-minutes.html#action02]

<scribe> ACTION: Cynthia to check with IE team to see if they would be opposed to removing aria-owns. [recorded in http://www.w3.org/2010/03/30-aapi-minutes.html#action03]

DB: Is there another way aria-owns could be exposed via MSAA and UIA? Cynthia doesn't think UIA has anything that is like relationships but will check again.
... AT's could use the DOM but we want to discourage that. They should be using the APIs.

CS: these scenarios don't occur very often

<davidb> so a remaining subtlety is how to word what to do with aria-owns when

will just live with differing implementations

<davidb> the application supports only API that doesn't have support for relationships

<davidb> vs ones that support both for e.g. MSAA+IA2

once we merge change the columns, there will be a separate column for IAccessible2 with MSAA implementations so there won't be an issue

<davidb> application == browser

<davidb> so in FF we want to do what the MSAA col has, plus the IA2 col

<davidb> but in this case we wouldn't want to do the MSAA way for aria-owns as written

CS: for HTML, there is a similar table being written that will have an MSAA-only column
... it will just have a lot of things that don't get mapped.
... thinks the merged columns make sense for ARIA, just may be confusing because the HTML table will be different
... keep MSAA-only column, and have MSAA plus UIA Express, and IAccessible2 plus MSAA column
... different idea - in MSAA column, "if MSAA-only, modify the tree. If MSAA plus an API that supports relationships, don't modify the tree"

forget the previously recorded actions on this topic and just do this fix

<davidb> http://www.w3.org/WAI/PF/aria-implementation/

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9363

topics for next week - discuss section 5 now that we have answers to many of our questions.

This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Andi
Inferring ScribeNick: Andi
Default Present: Andi_Snow_Weaver, Cynthia_Shelly, [Mozilla]
Present: Andi_Snow_Weaver Cynthia_Shelly [Mozilla]
Got date from IRC log name: 30 Mar 2010
Guessing minutes URL: http://www.w3.org/2010/03/30-aapi-minutes.html
People with action items: cynthia david

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