15:50:06 RRSAgent has joined #aapi 15:50:06 logging to http://www.w3.org/2011/10/11-aapi-irc 15:50:14 rrsagent, make logs public 15:50:25 rrsagent, make log world 15:50:32 Scribe: Andi_Snow-Weaver 15:50:39 ScribeNick: Andi 15:50:46 Meeting: AAPI 15:50:55 Chair: Andi_Snow-Weaver 15:51:58 rrsagent, stop 16:06:46 topic: bug 11811 16:06:48 http://www.w3.org/WAI/PF/aria-implementation/#document-handling_frames 16:08:30 AS: First sentence, change "contained document" to "sub-document" 16:09:55 AS: Second sentence starts out talking about frame elements and ends up talking about iframe elements 16:10:04 AS: change all to "frame or iframe" 16:11:27 maybe: "For example, in a mashup scenario, it is usually the nearest parent container with aria-live, aria-atomic, aria-relevant, and aria-busy (state) that decides what gets mapped through accessibility API" 16:12:08 AS: "it is usually the nearest parent container with aria-live, aria-atomic, aria-relevant, and aria-busy (state) that decides what appears on the child for the corresponding attributes in the Accessibility API." 16:14:30 AS: Remove sentence that starts out "for example, in a mashup scenario..." 16:17:26 CS: "This allows the author of the parent or containing document to control the assertiveness of the sub-document." 16:19:20 action: Andi to work on language to make it normative - these are SHOULDs, not MUSTs 16:20:29 CS: in the table, for UIA, it goes into AriaProperties 16:21:17 cyns has joined #aapi 16:21:18 Remove bullets 2 and 3 from the list. 16:21:39 http://www.w3.org/WAI/PF/aria-implementation/#document-handling_frames 16:24:02 AS: bullets after the table 16:24:27 DB: reads definiton of root WAI-ARIA node 16:24:56 CS: think it would mean the not the in this case 16:25:13 CS: suggest frameset or iframe 16:25:57 DB: might be talking about a body element of a frame 16:26:50 CS: bullet 1 sounds like an author error 16:27:01 DB: or somebody trying to dup somebody 16:27:16 CS: is it a valid way to group controls in a single place? 16:28:58 CS: need to ask ARIA TF for the use case for these bullets 16:29:09 DB: think 4 bullets could be collapsed into one idea 16:29:42 CS: when there are properties on the frame, use them. If not, look to the body of the contained document 16:30:16 DB: Aaron's idea was to always use the properties on the body of the contained document except in the case of -live, -atomic, -relevant, and -busy 16:30:42 DB: not sure why aria-selected, aria-valuenow, aria-valuetext, aria-activedescendant are called out 16:31:17 CS: suggest deleting these 4 bullets and saying "except for a-live, -atomic, -relevant, and -busy, use the attributes on the body of the contained document" 16:31:34 s/a-live/-live/ 16:32:25 AS: Note contains normative language 16:32:35 CS: should be a must 16:32:40 DB: security issue 16:34:46 -Andi_Snow-Weaver 16:34:47 -Cynthia_Shelly 16:34:49 -David_Bolter 16:34:49 WAI_PFWG(AAPI)12:00PM has ended 16:34:50 Attendees were David_Bolter, Andi_Snow-Weaver, Cynthia_Shelly 16:34:51 rrsagent, make minutes 16:34:51 I have made the request to generate http://www.w3.org/2011/10/11-aapi-minutes.html Andi 16:34:58 zakim, bye 16:34:58 Zakim has left #aapi