16:54:22 RRSAgent has joined #aria-apg 16:54:22 logging to http://www.w3.org/2016/05/02-aria-apg-irc 16:54:34 agenda? 16:54:41 zakim, clear agenda 16:54:41 agenda cleared 16:55:44 Agenda+ Review updated section 3.17 Listbox https://rawgit.com/w3c/aria-practices/listbox/aria-practices.html#Listbox 16:55:44 Updates resolve bugs: 16:55:44 28085 https://www.w3.org/Bugs/Public/show_bug.cgi?id=28085 16:55:44 29469 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29469 16:55:44 Agenda+ Review updated section 3.35 Window Splitter https://rawgit.com/w3c/aria-practices/WindowSplitter/aria-practices.html#windowsplitter 16:55:47 Agenda+ Review resolution of issue 25 "Rename tab panel design pattern" https://github.com/w3c/aria-practices/issues/25 16:55:50 https://rawgit.com/w3c/aria-practices/master/aria-practices.html#tabpanel 16:55:52 Agenda+ Review current revision of section 3.10 Dialog (Modal) https://rawgit.com/w3c/aria-practices/master/aria-practices.html#dialog_modal 16:55:55 Updates resolve bug 29303 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29303#c0 16:55:57 Agenda+ Review status of current example development work https://github.com/w3c/aria-practices/wiki/Design-Patterns-Status 16:57:10 zakim, who is on the call? 16:57:10 Present: jaeunjemmaku, JamesNurthen, Michiel_Bijl 16:58:36 rrsagent, make log world 16:58:43 meeting: ARIA APG TF 16:59:38 Birkir has joined #aria-apg 17:00:25 LJWatson has joined #aria-apg 17:00:41 annabbott has joined #aria-apg 17:01:00 regrets+ Leonie 17:01:37 TeresaBoers has joined #aria-apg 17:01:37 mck has joined #aria-apg 17:06:06 jongund has joined #aria-apg 17:07:13 agenda? 17:07:18 what is our host room ID? 17:07:37 646 444 732 17:08:16 jamesn has changed the topic to: https://mit.webex.com/mit/e.php?MTID=mb37eefe6ee01f16437b083a4018efedd 17:08:28 what is the password 17:08:58 scribe: Birkir 17:10:29 JN: Never put our sacred password in a comment, us /me space to do it via a comment. 17:10:37 present+ jongund 17:11:19 zakim, next item 17:11:19 agendum 1. "Review updated section 3.17 Listbox https://rawgit.com/w3c/aria-practices/listbox/aria-practices.html#Listbox" taken up [from jamesn] 17:11:47 bgaraventa1979 has joined #aria-apg 17:12:11 present+ Bryan_Garaventa 17:12:43 jemma_ has joined #aria-apg 17:14:14 Updates resolve bugs: 17:14:14 28085 https://www.w3.org/Bugs/Public/show_bug.cgi?id=28085 17:14:14 29469 https://www.w3.org/Bugs/Public/show_bug.cgi?id=29469 17:15:02 MK: A lot of changes were made, we need to go through this top to bottom. 17:15:46 present+ JaEunKu 17:16:06 MK *grumbles about Jaws* 17:16:47 q+ 17:17:11 MK: Looking at the second paragraph, need to look at whether children presentational is still in ARIA 1.1 draft. 17:17:41 MK: We aim for simpler language in this paragraph. 17:17:57 JN: How are paragraphs 2 and 3 different? 17:18:45 MK: 2nd paragraph talks about loss of structure, the third talks about not having long text in options (we may apply this best practice to other widgets e.g. menu). 17:19:30 MK: We might want to create a separate general best practices section that we could link to, for future. 17:21:13 AA: How does the browser treat images in options, since it treats the option as flat text. 17:21:53 MK: Treats image text alternative as part of the option string, without announcing the role. 17:22:43 ack me 17:22:45 q+ 17:23:45 JN: Should we remove the first sentence from paragraph 2 (we don't need the term "static" introduced). 17:24:15 MK: The concept "static" is not dfined in the spec. 17:25:54 MK/JN: start paragraph with "the contents of option elements..." 17:26:19 AA: Mention the things with images in options? 17:26:58 JN: Generally I find taht if you have more than two children of an element like optoin, you might as well put an aria-label on it to control how it is read. 17:29:15 BG: Should we change the language of paragraphs 3 and 4 to 'authors should" rather than "should not". 17:29:40 MK: Dificult to phrase it in an 'authors should" way. 17:30:18 MK: Perhaps change it in paragraph 4. 17:31:25 Joint decision to leave paragraphs 3 and 4 as is. 17:32:40 annabbott_ has joined #aria-apg 17:32:52 MK: Deleted bullet about tab key in keybord interaction, we should avoid talking about the tab key unless it does something inside the widget. 17:33:55 mck_ has joined #aria-apg 17:34:15 AA: Changet he sub tbllet of list one "optionally an option" ? REmvoe the word "optionally"? 17:34:33 LJWatson_ has joined #aria-apg 17:35:28 JN: The (optional) keyword may be confusing e.g. the "home and end" key section (are both optional, or just the end key)? 17:38:50 MK: Changed sentence to "author may choose to have the first option selected". 17:39:11 JN: Who is the mystery call-in user. 17:39:28 BG2: It is Bryan. 17:39:50 incognito 17:40:55 MK: Discuss combining the multiple selection models. Hard to write it in a way that came across clerly. 17:41:29 MK: Changed the headings to "recommended model" and "alterantive model". 17:42:18 MK: Tried to order keyboard shortcuts from most important to less important. 17:43:12 JN: "unselect all" keystroke missing for multiple select mode. 17:43:53 MK: WAs told to remove it, we may want to provie a link or button to achieve that purpose. 17:44:34 AA: Under recommended selection model, the o in "optional" should be capitalized. 17:45:04 http://www.oracle.com/webfolder/technetwork/jet/uiComponents-select-multi.html 17:45:53 After checking other entries we collective decide to capitalize the "o" in "Optional". 17:48:51 MK: Should we add a note at the end? 17:48:58 Consensus, yes. 17:49:34 Birkir: Why do we have the alterantive select model. 17:50:31 MK: Firefox implements this keybaord behavior automatically for a multi-select listbox. 17:51:48 MK: Item for self, make a note about difference between focus and selection. Ditto about active descandants. 17:54:06 MK: Add a note to the end of this section saying something along the lines of: "Authors should provide a control that allows user to de-select all options in a multi-select listbox). 17:55:10 AA: Make ti a third bullet, after alterantive selection model. 17:56:54 Birkir: Should we add a note about only doing this for large listboxes, (clutters up the UI by adding two focusble controls, select and de-select, for each listbox element). 17:59:03 is this the link? https://www.w3.org/TR/wai-aria-practices-1.1/#Listbox 17:59:18 refreshed doc 18:00:00 sakim, next item 18:00:16 https://rawgit.com/w3c/aria-practices/listbox/aria-practices.html#Listbox 18:00:23 zakim, next item 18:00:23 I see a speaker queue remaining and respectfully decline to close this agendum, Birkir 18:00:35 ack me 18:01:06 zakim, next item 18:01:06 agendum 3. "Review resolution of issue 25 "Rename tab panel design pattern" https://github.com/w3c/aria-practices/issues/25" taken up [from jamesn] 18:01:20 zakim, take up item 2 18:01:20 agendum 2. "Review updated section 3.35 Window Splitter https://rawgit.com/w3c/aria-practices/WindowSplitter/aria-practices.html#windowsplitter" taken up [from jamesn] 18:03:56 MK: Changed first sentence to inclue a link. Used the word "boundry" to avoid repetition. 18:05:04 MK: Editorial item, include a sentence that explains what a window splitter does. 18:05:37 JN: Jaws/NVDA do not switch modes when tabbing to a separator. 18:06:18 MK: What does a separator map to, horizontal rule? 18:07:00 MK: Does anything in html map to the separator role?
maps to separator. 18:07:53 MK: So what do we do with a window splitter? 18:08:02 JG: Is it a slider? 18:08:40 MK: What we could do (do not puke) is to use the application role .... 18:09:30 'JN: A popular way around this is a splitter with a child button. 18:09:41 MK: Button does not trigger interactive mode. 18:09:48 +q 18:10:24 JN: Do screen readers need window splitter? 18:10:50 MK: In some cases yes, e.g. when maximizing a window. 18:11:44 Bryan: I have never seen display none applied to content.this type of collapsed 18:12:47 JN: Looks like we don't have a good role for this, separator is static. 18:13:46 MK: Use combination of application and role description role. Would be a sensible use of the application role (note from scribe, the first?) 18:14:06 Bryan: It is not going to work on touch-screen devices. 18:15:37 Birkir: Isn't touch-screen APG primarily an ARIA 2.0 item? 18:16:09 MK: It kind of is, e.g. hard to describe touch-screen interaction for listboxes and trees. 18:16:30 JG: Do we really need this section? 18:17:02 MK: We could, but if we are going to reserve it, we need to come up with a solution. 18:17:42 +q 18:17:43 MK: Important for sighted screen reader users. 18:19:13 MK: Need to be able to press arrow key until content is expanded or collapsed. Screen reader only users may not need to know this at all. 18:19:21 vote for drop 18:21:55 http://jdevadf.oracle.com/adf-richclient-demo/faces/index.jspx;jsessionid=E7NytAxS1G9DZ1He0hcnWBcpX0Lywjs311Uz4RZIRQ0n0i_iPoPM!-389778909 18:22:03 http://jdevadf.oracle.com/adf-richclient-demo/faces/index.jspx 18:22:13 JN: Goes looking for an example. 18:22:16 https://jsfiddle.net/ 18:23:05 JG: Fiddle.net has it (code in one payne, results in another). 18:24:12 https://rawgit.com/jongund/oaa-examples/master/examples/treeview/treeview-1.html 18:24:20 MK: The fact we quickly found a few examples shows us this is used. This is a prime candidate for a creating a custom widget using ARIA. 18:24:42 Jemma: Want to ask a question about trees. 18:25:07 MK/JN: Work on a better window splitter example, take it back to the group. 18:26:37 AA: Spec discusses a visible separator, e.g. between groups of menu items or as a movable separator between two regions in a split payne. This indicates a spec problem. A static element should not be an operable element. 18:27:51 rsagent, make minutes 18:28:08 rrsagent make minutes 18:28:43 rrsagent, make minutes 18:28:43 I have made the request to generate http://www.w3.org/2016/05/02-aria-apg-minutes.html Birkir