16:59:02 RRSAgent has joined #aria-apg 16:59:02 logging to http://www.w3.org/2017/04/24-aria-apg-irc 16:59:08 Meeting: ARIA APG TF 16:59:19 Agenda+ Matt: Update on long description disclosure example review 16:59:24 scribe: Jemma 16:59:25 Agenda+ Matt: Update on editor menubar example review 16:59:29 Agenda+ Matt: Update on issue 326: Why does the ARIA Menu Button pattern not say to use aria-expanded=true/false but the actual demo examples do use aria-expanded? Seems confusing. 16:59:34 Agenda+ Matt: Update on treeview review; 3 critical bugs found. 16:59:38 present+ JaEunJemmaKu 16:59:38 Agenda+ James: Update on modal dialog pattern revisions 16:59:48 Agenda+ Matt: Update on fixes to modal dialog example 16:59:53 Agenda+ Aaron: Update on issue 132: Changes to treegrid example code 17:00:00 present+ JamesNurthen 17:01:44 rrsagent, make log world 17:02:18 AnnAbbott has joined #aria-apg 17:03:06 presesnt+ AnnAbbott 17:03:21 present+ AaronLeventhal 17:03:43 present+ ShirishaBalusani 17:03:43 present+ AnnAbbott 17:03:45 mck has joined #aria-apg 17:04:15 present+ matt_king 17:05:01 agenda? 17:05:19 present+ JaEunJemmaKu 17:05:35 take up item 1 17:06:26 can you put the link to the issue? 17:07:36 matt: thanks everyone for working on this. this can be closed. 17:07:54 next item 17:08:09 https://github.com/w3c/aria-practices/issues/144 17:09:49 jongund has joined #aria-apg 17:10:36 There are 2 more issues that I have noticed. (I realize that these are visual issues, however I think it's important to fix them because we need sighted devs to want to use these accessible controls). Issue 1 When moving a mouse horizontally across a menubar, hovering over each menu button to see what is in its menu, each newly-opened menu appears instantly (good) but the previously-open menu hesitates before closing, which looks like both menus are open [CUT] 17:11:29 for a while, which feels really odd. This odd behavior does not happen when I use right/left arrow keys to traverse through the menus. I looked at the code to see what could be causing this, and I found this code in MenubarItemLinks.js: 17:11:42 I don't know why there's a timeout here - is it necessary? If it does need to be kept for some reason, then 300 ms is way too long to wait before closing the previous menu, so we need to determine what minimum value it can be set to. 17:11:52 Issue 2 Using either keyboard or mouse, when the user opens a menu and then traverses to a menu item inside that menu, the menu button in the menubar no longer looks selected. For example, open the Font menu, and arrow down to the Serif menu item. The selected look of the Font menu button disappears. This is different from the look of a desktop menubar, which would show the Font menu button as "pushed in" (for Windows menubars) or "blue" (for Mac menubars)[CUT] 17:12:10 present+ jongund 17:13:07 bgaraventa1979 has joined #aria-apg 17:13:15 http://w3c.github.io/aria-practices/examples/menubar/menubar-2/menubar-2.html 17:13:43 present+ Bryan_Garaventa 17:13:48 here is the example: 17:13:50 http://w3c.github.io/aria-practices/examples/menubar/menubar-2/menubar-2.html 17:15:08 jon: if there is no delay, mouse user will be frustrated 17:15:22 jon: but i can remove it 17:15:56 jon: change it to 100? 17:18:14 james: the problem is existing menu still stays open when new menu is opened 17:18:57 jon: I can look into the issue 17:20:29 matt: we can ask Carolyn MacLeod to fix this problem 17:20:47 matt: can anyone add comments to the issue and assign this to her? 17:21:00 jon: she can contact me any time for any questions. 17:22:30 next item 17:22:43 https://github.com/w3c/aria-practices/issues/326 17:22:53 zakim take up agendum 3 17:22:59 zakim, take up agendum 3 17:22:59 agendum 3. "Matt: Update on issue 326: Why does the ARIA Menu Button pattern not say to use aria-expanded=true/false but the actual demo examples do use aria-expanded? Seems 17:23:02 ... confusing." taken up [from jamesn] 17:25:01 matt: aria expanded can be optional as it was stated in the spec 17:26:01 matt: jon has already submitted pull request for this change 17:26:22 jon: student is doing an example with active decendants 17:27:33 jon: I would like to finish all the examples before I move away from ARIA-APG including html 5 menu example 17:27:48 matt: I also need to make some editorial changes 17:28:22 matt: we would be able to finish this in the current milestone. 17:28:38 https://github.com/w3c/aria-practices/issues?utf8=%E2%9C%93&q=is%3Aopen%20is%3Aissue%20milestone%3A%22Jan%202017%20Clean%20Up%22%20sort%3Aupdated-desc%20%20label%3Abug%20tree 17:28:38 zakim, next item 17:28:38 agendum 4. "Matt: Update on treeview review; 3 critical bugs found." taken up [from jamesn] 17:28:46 https://github.com/w3c/aria-practices/issues?utf8=%E2%9C%93&q=is%3Aopen%20is%3Aissue%20milestone%3A%22Jan%202017%20Clean%20Up%22%20sort%3Aupdated-desc%20%20label%3Abug%20tree 17:29:55 matt: It seems that left arrow behavior and modifier issue are all fixed. 17:31:53 matt: browser default action can be applied here. 17:32:10 matt: enter key does not work for me 17:32:21 i have the mac info 17:33:14 cmd+enter opens link in new background tab, and cmd+shift+enter opens in new foreground tab 17:33:41 matt: control +enter and shift + enter key activate links and open the links 17:35:23 matt: I raised aria current issue but it can be dealt at next milestone. 17:36:38 zakim, next item 17:36:38 agendum 5. "James: Update on modal dialog pattern revisions" taken up [from jamesn] 17:36:43 https://github.com/w3c/aria-practices/issues/325 17:36:53 james: I made a quick change to it 17:37:34 james: added one sentence to clarify that the interface can only be controlled by elements that are descendents of the dialog 17:37:50 james: I changed master 17:38:39 https://rawgit.com/w3c/aria-practices/master/aria-practices.html 17:39:14 https://rawgit.com/w3c/aria-practices/master/aria-practices.html#dialog_modal 17:39:37 For all dialogs, all controls required to operate the dialog are child nodes of the element which has role set to dialog. 17:41:30 jon: if we put role tree item to a link, it does not work 17:42:14 s/it/ keyboard 17:42:44 in particular, chrome browsser 17:42:53 s/browsser/browser 17:43:40 matt: jame's edit can go to under state, property section 17:44:04 james: I can move it to state property section as one of list item 17:44:11 s/item/items 17:45:41 zakim, next item 17:45:41 agendum 6. "Matt: Update on fixes to modal dialog example" taken up [from jamesn] 17:46:04 https://github.com/w3c/aria-practices/commit/aaa85366e3516be91da4dc5c50027553b3995d8e 17:46:43 this is the change james made, All controls required to operate the dialog are child nodes of the element which has role set to dialog 17:47:03 https://github.com/w3c/aria-practices/issues/321 17:47:16 zakim, next item 17:47:16 agendum 7. "Aaron: Update on issue 132: Changes to treegrid example code" taken up [from jamesn] 17:47:33 zakim, previous item 17:47:33 I don't understand 'previous item', AnnAbbott 17:48:19 matt: issue we are taking now is "we cannot scroll all the way to the bottom in order to press the buttons. It bounces back and I cannot activate them." 17:49:13 matt: as a solution, we made Modal Dialog to Make Full Screen on Small Devices 17:49:40 matt: let me know what you think - it works on ipad and more. 17:50:36 matt: I did 1. Add momentum scrolling. 2. Make dialog layer same height as main window. 17:50:58 Group to review issue 321 this week. https://github.com/w3c/aria-practices/issues/321 17:51:05 matt: James, please provide feedback on this. 17:51:18 jame: yes, I will 17:51:36 zakim, next item 17:51:36 I do not see any more non-closed or non-skipped agenda items, jemma 17:51:53 topic: aaron's update 17:52:13 this is part of next milestone 17:52:26 https://github.com/w3c/aria-practices/issues/132 17:53:16 aaron: how different tree grid from tree is the starting point for the work this week 17:53:37 aaron: different from grid 17:54:52 If the treegrid is configured so that rows can not be focused, then the first cell controls the expand/collapse behavior. In this case, aria-expanded will be on the first cell in each row instead of on the row. 17:55:34 Current work on this example is now in the treegrid branch of w3c/aria-practices at: https://rawgit.com/w3c/aria-practices/treegrid/examples/treegrid/treegrid-row-nav-primary-1.html 17:56:29 Group to review above rawgit link above this week. 17:56:50 aaron: This same example can be used in three ways. Rows are focused first, but cells can be focused: Useful when we want to present the treegrid to act primarily like a tree. Cells are focused first, but rows can also be focused: Useful when we want to present the treegrid to act primarily like a grid. Only cells can be focused: Useful when we we are primarily a grid, and we want to simplify the user experience by removing row navigation options. 17:57:44 aaron:if whole row is focused, it acts like tree 17:59:07 aaron: when only cells are focused, it is like a grid. 18:01:25 jon:by the way, it was a false alarm in regard to tree role to a link. 18:03:25 aaron: I appreciate the feedback from the group. 18:03:55 Now it is working with enter when cell is focused 18:05:47 Feedback requested on interaction mode. 18:06:08 rrsagent, make minutes 18:06:08 I have made the request to generate http://www.w3.org/2017/04/24-aria-apg-minutes.html jemma 18:07:07 siri: why is there aria-readonly="true"? 18:07:17 aaron: I added note about that 18:08:36 aaron:note is in the example page. aria-readonly: in ARIA 1.0, a grid/treegrid is editable by default. However, there is no default in ARIA 1.1. Firefox currently implements the ARIA 1.0 concept for this, which means that "editable" is read for every cell unless aria-readonly="true" is used on the treegrid. There needs to be some follow up with user agent developers on this, as ARIA 1.1 seems to be treating it more a tristate (don't care, false, true). In a[CUT] 18:10:33 aaron:a bug was filed on the spec regarding aria-readonly but it is possibly invalid. 18:10:43 rrsgent, make minutes 18:11:02 rrsagent, make minutes 18:11:02 I have made the request to generate http://www.w3.org/2017/04/24-aria-apg-minutes.html jemma 19:11:57 jongund has joined #aria-apg 20:37:06 jongund has joined #aria-apg 20:42:58 jongund has joined #aria-apg