17:00:31 RRSAgent has joined #aria-apg 17:00:31 logging to http://www.w3.org/2017/05/01-aria-apg-irc 17:00:37 rrsagent, make log world 17:00:45 Meeting: ARIA APG TF 17:00:53 present+ 17:01:11 present+ AnnAbbott 17:01:45 jemma has joined #aria-apg 17:03:15 Agenda+ Carolyn MacLeod's questions about menubar mouse behavior 17:03:27 Agenda+ Modal Dialog 17:03:34 Agenda+ Treeview 17:03:42 Agenda+ Menu Button 17:03:49 present+ 17:03:49 Agenda+ Issue 380: Place examples after the introduction text 17:04:30 present+ MattKing 17:04:30 mck has joined #aria-apg 17:04:35 present+ JaEunJemmaKu 17:05:28 sirib has joined #aria-apg 17:06:15 https://www.paciellogroup.com/blog/2017/05/the-paciello-group-joins-vfo/ 17:07:37 zakim, pick a victim 17:07:37 Not knowing who is chairing or who scribed recently, I propose MattKing 17:07:58 scribe:Jemma 17:08:22 chair: MattKing 17:08:25 zakim, topic 17:08:25 I don't understand 'topic', jemma 17:08:31 zakim, next item 17:08:31 agendum 1. "Carolyn MacLeod's questions about menubar mouse behavior" taken up [from jamesn] 17:08:34 https://github.com/w3c/aria-practices/issues/144#issuecomment-298280680 17:08:41 present+shirishaBalusani 17:08:45 https://github.com/w3c/aria-practices/issues/144#issuecomment-298280680 17:08:52 rrsagent, make minutes 17:08:52 I have made the request to generate http://www.w3.org/2017/05/01-aria-apg-minutes.html jamesn 17:09:27 bgaraventa1979 has joined #aria-apg 17:09:39 mck: Carolyn will fix the comment 17:09:50 s/comment/problem 17:10:02 present+ Bryan_Garaventa 17:11:11 s/comment/problem/ 17:11:56 +1 to car’s point 17:12:15 mck: matt, Michiel and James agree with Carolyn's suggestion 17:12:52 carolyn's comment -" So, if you agree that instead of closing on timeout, we should close on click, then that is what I will implement. " 17:14:00 james: mouse over will close previous menu 17:14:16 s/mouse over/mouse out 17:18:16 MB: I would argue that menu’s shouldn’t open on hover, unless, you’ve already activated an option in the menubar. 17:18:55 MB: To clarify, once you open a menu option and move your mouse to another option in the menubar, the previous menu option should close and the one you moved to should open. 17:23:43 james:Discussed 5/1/2017 in APG meeting. We agree with the substance of @carmacleod comments. 2 additional clarifications. we would argue that menu’s shouldn’t open on hover, unless, you’ve already activated an option in the menubar. To clarify, once you open a menu option and move your mouse to another option in the menubar, the previous menu option should close immediately and the one you moved to should open 17:24:17 zakim, next item 17:24:17 agendum 2. "Modal Dialog" taken up [from jamesn] 17:24:24 http://w3c.github.io/aria-practices/#dialog_modal 17:25:26 https://github.com/w3c/aria-practices/issues/325 17:26:07 I put my comments for 325 17:26:46 by bda it meant 321 17:26:57 My bad I meant 321 17:27:00 Because marking a dialog modal by setting aria-modal to true can prevent users of some assistive technologies from perceiving content outside the dialog, users of those technologies will experience severe negative ramifications if a dialog is marked modal but does not behave as a modal for other users. So, mark a dialog modal only when: Application code prevents all users from interacting in any way with content outside of it. Visual styling obscures the co[CUT] 17:30:39 s/out/ \outside of it. 17:30:44 s/out/outside of it. 17:31:43 jemma: I copied both edits for comparison. Original When a dialog closes, focus typically returns to the element that had focus before the dialog was invoked. This is often the control that opened the dialog. In circumstances where that element no longer exists, focus is set on an element that supports a logical work flow. Revised edit: When a dialog closes, focus is set on an element that supports a logical work flow. If the element that had focus befor[CUT] 17:32:38 s/out/outside of it/ 17:33:13 original: When a dialog closes, focus typically returns to the element that had focus before the dialog was invoked. This is often the control that opened the dialog. In circumstances where that element no longer exists, focus is set on an element that supports a logical work flow. 17:33:42 revised:When a dialog closes, focus is set on an element that supports a logical work flow. If the element that had focus before the dialog was invoked still exists, that element is usually the most appropriate choice. 17:35:14 ann: I like original the better. 17:35:54 I like original one too 17:36:30 i am ok with the original too 17:42:42 https://github.com/w3c/aria-practices/issues/321 17:44:34 http://w3c.github.io/aria-practices/examples/dialog-modal/dialog.html 17:48:01 michiel: I am working on revising css for example pages 17:48:34 micheil: i am rewriting the code for modal from bottom up. 17:49:31 For example: http://w3c.github.io/aria-practices/examples/button/button.html 17:51:26 https://moiety.me/research/dialog-modal/dialog.html 17:52:04 michiel: I can be done by next Monday 17:55:53 group discussion: there will be comment on small device view in coding example css file 17:56:36 in regards to modal dialog example 17:57:26 zakim, next item 17:57:26 agendum 3. "Treeview" taken up [from jamesn] 17:57:32 issue #? 17:57:49 zakim, next item 17:57:49 agendum 3 was just opened, jemma 17:57:57 zakim, take up item 5 17:57:57 agendum 5. "Issue 380: Place examples after the introduction text" taken up [from jamesn] 17:58:05 https://github.com/w3c/aria-practices/issues/380 18:03:46 http://w3c.github.io/aria-practices/#keyboard-interaction-5 18:04:39 mck: I support this proposal 18:05:33 michiel: proposal was putting the coding example link under pattern intero 18:05:52 s/intero/intro 18:08:21 me too 18:08:45 jamesn has left #aria-apg 18:10:16 mck: we can coordinate this work. 18:10:27 rrsagents, make minutes 18:11:13 rrsagent, make minutes 18:11:13 I have made the request to generate http://www.w3.org/2017/05/01-aria-apg-minutes.html jemma 18:11:40 rrsagent, make log public