<scribe> Scribe: Andi_Snow-Weaver

<scribe> ScribeNick: Andi

Issues and Actions: https://www.w3.org/WAI/PF/Group/track/products/10

ACTION-979

https://www.w3.org/WAI/PF/Group/track/actions/979

https://www.w3.org/WAI/PF/Group/track/actions/979

http://www.w3.org/WAI/PF/aria-implementation/#mapping_conflicts

add note to 5.4 to refer back to section 5.2 for the rules where there are conflicts with native semantics

ACTION-981 https://www.w3.org/WAI/PF/Group/track/actions/981

ACTION-990 https://www.w3.org/WAI/PF/Group/track/actions/990

Subtree: An object in a heirarchical object tree and all of it's descendants. In the case of accessibility APIs, this refers to an accessible object in the accessibility API tree, and it's descendants in that tree. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via aria-owns [@@need IA2 name for this]

unless those objects are also descendants in the accessibility API tree.

Subtree: An object in a heirarchical object tree and all of it's descendants. In the case of accessibility APIs, this refers to an accessible object in the accessibility API tree, and it's descendants in that tree. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via aria-owns [@@need IA2 name for this]

unless those objects are also descendants in the accessibility API tree.

"subtree" is used in name calculation text in 5.6.1.3 and in 5.8.2

CS: can't use aria-owns because IE modifies the accessibility tree per aria-owns relationships

RS: may need two separate definitions then

Accessibility Subtree: In the case of accessibility APIs, this refers to an accessible object in the accessibility API tree, and it's descendants in that tree. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via aria-flowto [@@need IA2 name for this] unless those objects are also descendants in the

accessibility API tree.

Accessibility Subtree: In the case of accessibility APIs, this refers to an accessible object in the accessibility tree, and it's descendants in that tree. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via aria-flowto [@@need IA2 name for this] unless those objects are also descendants in the accessibility

API tree.

Accessibility Subtree: This refers to an accessible object in the accessibility API tree and its descendants in that tree. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via aria-flowto [@@need IA2 name for this] unless those objects are also descendants in the accessibility API tree.

Accessibility Subtree: An accessible object in the accessibility API tree and its descendants in that tree. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via aria-flowto [@@need IA2 name for this] unless those objects are also descendants in the accessibility API tree.

Accessibility Subtree: An accessible object in the accessibility tree and its descendants in that tree. It does not include objects which have relationships other than parent-child in that tree. For example, it does not include objects linked via aria-flowto [@@need IA2 name for this] unless those objects are also descendants in the accessibility tree.

ISSUE-490: https://www.w3.org/WAI/PF/Group/track/issues/490

make an action item for Michael to change the testable statements to include both the MSAA and the IA2 roles for implementations that use IA2 (Firefox)

IE implementations will only have the MSAA role

testable statements should actually just refer to the mapping table - so IE testers will look at the MSAA column, FF testers will look at the IA2 column, etc.

ISSUE-492: https://www.w3.org/WAI/PF/Group/track/issues/492

CS: either of these will work

make an action for Cynthia to review tabpanel mapping against IE implementation

RS: need the IA2 role for tabpanel

Andi to find out if there is an object attribute for tabpanel

ISSUE-486: https://www.w3.org/WAI/PF/Group/track/issues/496

AS: bullet 3 in section 4.2
... Isn't this requirement a MUST even for HTML 4 implementations?

CS: WAI-ARIA is completely untestable unless tabindex is allowed on any element
... isn't there a modified HTML 4 DTD that allows tabindex on all elements?

RS: browsers all allow it but it's not in the DTD
... have to see if there is a modified HTML 4 DTD that includes tabindex

give Rich an action item to research this

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Remove "ROLE_SYSTEM_RADIOBUTTON or ROLE_SYSTEM_MENUITEM" from IA2 column//
Succeeded: s/Remove "ROLE_SYSTEM_CHECKBUTTON or ROLE_SYSTEM_MENUITEM" from IA2 column//
Succeeded: s/[Microsoft]/Cynthia_Shelly/
Succeeded: s/unless those objects are also descendants in the accessibility API tree/unless those objects are also descendants in the accessibility tree/
Succeeded: s/make and action for Cynthia/make an action for Cynthia/
Found Scribe: Andi_Snow-Weaver
Found ScribeNick: Andi
Default Present: Andi_Snow-Weaver, Cynthia_Shelly, Rich
Present: Andi_Snow-Weaver Cynthia_Shelly Rich
Regrets: David_Bolter
Got date from IRC log name: 25 Apr 2012
Guessing minutes URL: http://www.w3.org/2012/04/25-aapi-minutes.html
People with action items: 

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