15:54:54 <RRSAgent> RRSAgent has joined #aapi
15:54:54 <RRSAgent> logging to http://www.w3.org/2011/10/18-aapi-irc
15:55:01 <AndiSnow> rrsagent, make logs public
15:55:07 <AndiSnow> rrsagent, make log world
15:55:14 <AndiSnow> Scribe: Andi_Snow-Weaver
15:55:22 <AndiSnow> ScribeNick: AndiSnow
15:55:28 <AndiSnow> Meeting: AAPI 
15:55:34 <AndiSnow> Chair: Andi_Snow-Weaver
15:55:44 <AndiSnow> Regrets: Cynthia_Shelly
15:55:49 <AndiSnow> rrsagent, off
15:58:47 <AndiSnow> topic: bug 13214 http://www.w3.org/Bugs/Public/show_bug.cgi?id=13214
15:59:55 <AndiSnow> AS: see proposed text in comment 7. MUST or SHOULD?
16:00:11 <AndiSnow> DB: think we want everyone to do this the same way but we may not be able to make that happen
16:01:56 <AndiSnow> DB: when you have <strong> within a sentence, the accessibility tree might just have only the text element, not an element for strong with a child text element for the part that is strong
16:03:21 <AndiSnow> DB: text that is marked as strong would be a sibling of the other text in the accessibility tree
16:04:55 <AndiSnow> DB: a browser developer may feel strongly that an element with strong has an element in the accessibility tree
16:05:21 <AndiSnow> DB: if they do include it in the accessibility tree, wouldn't want to make it a strong requirement that they fire the text change events
16:08:56 <AndiSnow> DB: common example in Firefox - don't have an accessible object for <span> elements
16:15:19 <AndiSnow> "
16:15:19 <AndiSnow> For text within a paragraph marked in HTML as <strong>, the <strong> element has its own node in the DOM tree but may not have its own element in the accessibility tree.
16:21:41 <AndiSnow> rrsagent, stop
16:26:16 <AndiSnow> DB: suppose you have "the quick brown fox" - if "brown" is removed, you have to fire an event
16:26:31 <AndiSnow> AS: so that's covered in the first table in 5.8.2
16:26:59 <AndiSnow> DB: example of something that is not covered by the first table is formatting or style changes?
16:29:51 <AndiSnow> AS: but how do we quantify it? We can't just say that in some cases you fire the events when the element is not in the accessibilty tree without describing how to determine when you need to do that
16:33:10 <AndiSnow> DB: (thinking out loud) for changes to content that are not captured by structural changes to the accessibility tree, alternate events should be fired such as: (strong element example)
16:33:59 <AndiSnow> DB: the accessibility API may or may not provide the events you need
16:43:33 <AndiSnow> topic: bug 13258
16:43:45 <AndiSnow> http://www.w3.org/Bugs/Public/show_bug.cgi?id=13258
16:47:48 <AndiSnow> DB: table 4.1 should go somewhere later in the document
16:48:05 <AndiSnow> that's the table of mapping of focus states and events to APIs
16:48:22 <AndiSnow> DB: we may or may not want to absorb it into the other tables
16:48:47 <AndiSnow> DB: could have a 5.8.x on focus events
16:49:30 <AndiSnow> DB: 4.2 talking about HTML right? hard to keep them separate.
16:49:59 <AndiSnow> DB: changing my mind - 4.1 table may be okay here
17:00:13 <AndiSnow> Remove the text about tablist from the Selection section. This is covered in the "tab" role row of the role mapping table
17:00:34 <AndiSnow> change "SELECTED state" to STATE_SYSTEM_SELECTED state" for MSAA columns
17:01:56 <AndiSnow> change "SELECTED state" to "STATE_SELECTED state" for ATK column
17:04:47 <AndiSnow> rrsagent, make minutes
17:04:47 <RRSAgent> I have made the request to generate http://www.w3.org/2011/10/18-aapi-minutes.html AndiSnow
17:05:07 <Zakim> -Andi_Snow-Weaver
17:05:08 <Zakim> -David_Bolter
17:05:08 <Zakim> WAI_PFWG(AAPI)12:00PM has ended
17:05:09 <Zakim> Attendees were David_Bolter, Andi_Snow-Weaver
17:05:33 <AndiSnow> zakim, bye
17:05:33 <Zakim> Zakim has left #aapi
18:58:52 <AndiSnow> present: Andi_Snow-Weaver, David_Bolter
18:59:05 <AndiSnow> regrets: Cynthia_Shelly, Tim_Boland
18:59:12 <AndiSnow> rrsagent, make minutes
18:59:12 <RRSAgent> I have made the request to generate http://www.w3.org/2011/10/18-aapi-minutes.html AndiSnow