17:01:48 <RRSAgent> RRSAgent has joined #aria-apg
17:01:48 <RRSAgent> logging to http://www.w3.org/2016/04/25-aria-apg-irc
17:01:55 <jamesn> rrsagent, make log world
17:02:00 <jamesn> regrets+ Michiel
17:02:00 <eli> eli has joined #aria-apg
17:02:19 <eli> Hey everyone! First timer here. What is the meeting pw?
17:03:59 <mck> Agenda+ Review status of current example development work https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status
17:04:00 <mck> Agenda+ Review section 2.8 Combo Box http://w3c.github.io/aria/practices/aria-practices.html#combobox
17:04:02 <mck> Agenda+ Review section 2.5 Auto Complete http://w3c.github.io/aria/practices/aria-practices.html#autocomplete
17:04:10 <eli> Thanks!
17:05:25 <jamesn> eli: who are you by the way
17:06:10 <jamesn> welcome
17:07:26 <jemma_> present+ jaeunjemmaku
17:08:25 <jamesn> present+ JamesNurthen
17:10:02 <jemma_> scribe:JemmaJaeun
17:10:36 <jemma_> agenda 1
17:11:30 <jemma_> next item
17:12:07 <annabbott> Jemma is working on tree example, Jon is traveling
17:12:31 <annabbott> Jemma will try to have tree example ready for next week
17:12:47 <jemma_> *thanks ann
17:13:12 <jemma_> matt is working on dialog
17:13:37 <jemma_> mk: to show support on combo box
17:13:58 <jemma_> mk: we don't reviewed the text yet though
17:14:22 <jemma_> mk: need help on css
17:14:47 <jemma_> mk: I will work on dialog modal
17:15:09 <jemma_> mk: also work on non modal
17:15:17 <jemma_> s/work/will work
17:15:42 <jemma_> jn: matt, will you work on combo box?
17:16:00 <jemma_> mk: need to 2 combo box example
17:16:12 <jemma_> s/example/examples
17:17:20 <jemma_> ann: how about dialog tool tip?
17:17:39 <jemma_> mk: about to rewrite dialog tool tip from ground
17:17:59 <MichielBijl> Agenda+ Discuss possible issues with splitting APG to separate repository.
17:19:43 <jemma_> mk: bascially decide to rewrite dialog tool tip section later
17:20:39 <mck> Agenda+ Review status of current example development work https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status
17:20:41 <mck> Agenda+ Review section 2.8 Combo Box http://w3c.github.io/aria/practices/aria-practices.html#combobox
17:20:43 <mck> Agenda+ Review section 2.5 Auto Complete http://w3c.github.io/aria/practices/aria-practices.html#autocomplete
17:20:45 <eli> https://www.w3.org/Bugs/Public/show_bug.cgi?id=29327
17:21:30 <boerst> boerst has joined #aria-apg
17:21:38 <jamesn> agenda?
17:21:46 <MichielBijl> Regrets- Michiel
17:21:55 <jemma_> next item
17:21:57 <MichielBijl> present+ Michiel_Bijl
17:22:47 <jamesn> zakim, drop agendum 5
17:22:47 <Zakim> agendum 5, Review status of current example development work https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status, dropped
17:22:54 <jamesn> zakim, drop agendum 6
17:22:54 <Zakim> agendum 6, Review section 2.8 Combo Box http://w3c.github.io/aria/practices/aria-practices.html#combobox, dropped
17:22:59 <jamesn> zakim, drop agendum 7
17:22:59 <Zakim> agendum 7, Review section 2.5 Auto Complete http://w3c.github.io/aria/practices/aria-practices.html#autocomplete, dropped
17:23:03 <jamesn> agenda?
17:24:13 <jemma_> take up agendum 4
17:24:59 <jamesn> zakim, take up item 2
17:24:59 <Zakim> agendum 2. "Review section 2.8 Combo Box http://w3c.github.io/aria/practices/aria-practices.html#combobox" taken up [from mck]
17:26:02 <jemma_> mk: description of combo box here is interestingly terse
17:26:15 <jemma_> ann: interestingly feminize
17:26:53 <mck> http://rawgit.com/w3c/aria/action1490-combobox/aria/aria.html#combobox
17:27:17 <jemma_> mk: linked to spec
17:27:44 <jemma_> mk:using description, first paragraph from here
17:28:20 <jemma_> mk: trying to help user which role is need to be used.
17:28:53 <jemma_> mk:explicit description from outset needed.
17:29:26 <jemma_> ann: dialog in combo box?
17:29:32 <jemma_> mk: like a datepicker
17:29:45 <mck_> mck_ has joined #aria-apg
17:30:37 <jemma_> jn:do we want to keep autocomplete together in the section?
17:31:17 <jemma_> jn: it makes hard to implement combo box with auto complete
17:32:50 <jemma_> jn: combobox and autocomplete are separate for design pattern example for now
17:33:20 <jemma_> mk: talk combox as simple as like replicating html select
17:33:36 <jemma_> s/combox/combobox
17:34:22 <jemma_> jn: keyboard changes significantly between two, combo box and autocomplete combo box
17:34:58 <jemma_> jn: common stuff first, (easiest thing first) and different thing later such as keyboard
17:35:23 <jemma_> jn: in regards to combo box and autocomplete example
17:35:45 <jemma_> mk:aria-multiline is relevant to text
17:36:03 <jemma_> s/text/text input method
17:36:29 <jemma_> mk: how we address this, aria-multiline with autocomplete
17:37:08 <eli> forgive me, but what is an example where a user would encounter a combobox?
17:37:39 <jemma_> jn; multi line text is not necessarily text editor, it could be just one word, single line text box
17:38:14 <jemma_> mk: for now autocomplete does not describe this case.
17:38:34 <jemma_> s/jn;/jn:
17:39:18 <eli> http://w3c.github.io/aria/practices/aria-practices.html#combobox
17:39:31 <jemma_> ann: description will be rewritten?
17:39:35 <jemma_> mk: yes
17:40:13 <jemma_> mk:download arrow usually open the combo box rather than alt+download arrow.
17:41:55 <jemma_> s/download/down
17:42:27 <jemma_> jn:down arrow move focus to first item
17:43:53 <jemma_>  mk: native element for combo box with autocomplete is html select
17:44:14 <jemma_> s/is/is similar to
17:44:36 <jemma_> ann: more explanation for html select?
17:45:01 <jemma_> bryan: select element with down arrow, automatically trigger on change event
17:45:12 <jemma_> , not with down arrow with alt
17:45:31 <jemma_> s/,/bryan:
17:46:29 <jemma_> jn:space key does not make sense for combo box
17:47:01 <jemma_> mk: do we want to have the same behavior with html select then?
17:48:01 <jemma_> mk: listbox I worked on is not incorporated here yet.
17:48:26 <jemma_> mk: didnot write about expanding/ collapsing the list box
17:49:33 <jemma_> mk: should we incorporate list box pattern to combo box pattern?
17:50:14 <jemma_> mk: what about combo box which has only read only text field?
17:51:01 <jemma_> mk: I think read only text does not make sense for combo box.
17:52:00 <jemma_> mk: considering copy and paste function, it could be a valid reason to have combo box as read only item.
17:52:54 <jemma_> mk: if readonly, using space bar and opening the list make sense.
17:54:06 <jemma_> brayan: divide keyboard sections for two, one for read only text, the other one for non read only?
17:54:21 <jemma_> s/brayan/mk
17:54:26 <jemma_> bryan: yes
17:55:44 <jemma_> jn: let's make this option - ua implementation
17:55:50 <jemma_> s/option/optional
17:56:27 <jemma_> mk:enter key does not expand the list
17:56:42 <jemma_> mk: space is the same as alt+down arrow
17:57:02 <jemma_> *thanks james
17:59:09 <jemma_> jn: creating a bug with discussion summary
18:00:41 <jemma_> eli:esc key fall back to default status
18:04:11 <jemma_> teresa: are we talking about jaws?
18:04:17 <jemma_> mK:no
18:04:53 <jemma_> mk: jaws behavior is only reading cursor is active
18:05:05 <jemma_> s/only/only for
18:05:42 <jemma_> mk: this is for widget section
18:07:27 <jemma_> mk: we are working on aria 1.1 apg, not 1.o
18:07:36 <jemma_> s/1.o/1.0
18:08:16 <jemma_> bryan: wouldn't be a good idea to separate them out?
18:08:52 <jemma_> mk: there was a discussion separating labels
18:10:53 <mck_> • The next element is an html <button>, or another element with a role of button. This element is used to toggle the display of the combobox's drop down list.
18:11:44 <jemma_> s/wouldn't be a good idea to separate them out?/wouldn't be a good idea to separate design patterns out for each aria 1.0 and 1.1?
18:14:48 <jemma_> brayn: when edit field is spoken, dropdown trigger is button
18:16:40 <jemma_> bryan:when there is role=combo box, image is outside of list and it uses aria control
18:17:08 <jemma_> mk: 1.0 pattern still requires to have aria-own
18:17:59 <jemma_> s/aria control/aria-control
18:19:02 <jemma_> bryan: button is not part of combo box, it is trigger device to invoke the combo box
18:21:03 <jemma_> mk: you may use text box, aria equal to list box, aria controls on it as alternative and it is also relevant to descendants discussion.
18:21:28 <jemma_> s/descendants/aria-descendants
18:21:55 <jemma_> mk: not sure yet about "image" part in the section
18:22:19 <jemma_> s/section/combo box section
18:24:19 <jemma_> ann: mouse way and keyboard way are different
18:24:54 <jamesn> https://github.com/w3c/aria/issues/349
18:25:03 <jemma_> ann: that is why we are talking about this section
18:25:19 <jemma_> next ite
18:25:33 <jemma_> s/next ite/next item
18:26:07 <mck_> • Provide a label for the combobox by referencing the text field in the combobox. You can use an
18:26:09 <mck_> aria-label
18:26:10 <mck_>  to associate this label with the combobox or you may use the HTML <label> element and its for attribute to reference the text field.
18:31:04 <jemma_> mk: need to have some discussions with screen reader guy about label
18:31:45 <jemma_> summary about combo box pattern: Keys: Space and Alt+Down expand list without changing the value (both optional) Down (change the selected displayed in the list) and optionally expand the list.
18:32:02 <jamesn> rrsagent, make minutes
18:32:02 <RRSAgent> I have made the request to generate http://www.w3.org/2016/04/25-aria-apg-minutes.html jamesn
18:36:55 <eli> Hey, guys. I had to jump off the call. Thanks for being gentle for my first time :)
18:46:00 <MichielBijl> Nice to meet you Eli!