16:53:10 <RRSAgent> RRSAgent has joined #aria-apg
16:53:10 <RRSAgent> logging to http://www.w3.org/2016/03/14-aria-apg-irc
16:53:15 <MichielBijl> 11 is?
16:53:15 <Zakim> Zakim has joined #aria-apg
16:53:39 <jamesn> rrsagent, make log world
16:54:59 <jamesn> Agenda+ Example reviews and update pattern work assignments https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status
16:54:59 <jamesn> Agenda+ Bug 28914 – pattern-alert clarify that alerts must be added dynamically and not at page load https://www.w3.org/Bugs/Public/show_bug.cgi?id=28914#c0
16:54:59 <jamesn> Agenda+ Bug 29327 – pattern-dialog (tooltip) Gut and start over https://www.w3.org/Bugs/Public/show_bug.cgi?id=29327
16:54:59 <jamesn> Agenda+ Review fixes to Section 2.30 Tabpanel https://rawgit.com/w3c/aria/master/practices/aria-practices.html#tabpanel
16:55:02 <jamesn> Agenda+ review fixes to section 2.31 Toolbar https://rawgit.com/w3c/aria/master/practices/aria-practices.html#toolbar
16:55:05 <jamesn> Agenda+ Review fixes to section 2.34 Tree view https://rawgit.com/w3c/aria/master/practices/aria-practices.html#TreeView
16:55:08 <jamesn> Agenda+ Review section 2.13 Grid (Simple Data Tables) https://rawgit.com/w3c/aria/master/practices/aria-practices.html#grid
16:55:13 <jamesn> agenda?
16:57:17 <jamesn> present+ JamesNurthen
16:57:25 <jamesn> meeting: WAI-PF ARIA Authoring Practices Guide Taskforce
16:58:46 <MichielBijl> present+ MichielBijl
16:58:52 <MichielBijl> regrets+ LéonieWatson
17:01:33 <boerst> boerst has joined #aria-apg
17:02:00 <mck> mck has joined #aria-apg
17:03:55 <jamesn> regrets+ JonGunderson
17:04:16 <mck> agenda ?
17:08:05 <IanPouncey> Present+ IanPouncey
17:08:43 <jamesn> 1)     For example, source code link name in button example page should be button.css and button.js NOT link.css and link.js
17:09:03 <jamesn>    The same for the example, checkbox-2
17:09:03 <jamesn> 
17:09:03 <jamesn> https://rawgit.com/w3c/aria/Mar_2016_Heartbeats/practices/examples/checkbox/checkbox-2.html
17:09:03 <jamesn> They should be checkbox-3.css and checkbox-3.js
17:09:14 <jamesn> 3)     Menu example was not updated in the publication yet.
17:09:14 <jamesn> 4)     Radio example was not updated yet
17:11:03 <jamesn> mck: the example page, the code refers to the correct thing but the file name on the page is incorrect
17:11:26 <jamesn> mck: for (3) and (4) you are saying that the entire sub directory are not merged
17:11:46 <jamesn> mck: would also mean editing practices to create a link to them
17:12:49 <jamesn> mb: can a mail be sent for how to use github to do this kind of thing
17:13:05 <jamesn> mk: we can discuss later.
17:13:42 <jamesn> mb: branched would solve this
17:14:38 <jemma> jemma has joined #aria-apg
17:15:50 <jamesn> scribe: jamesn
17:16:18 <jamesn> mck: Jemma to create a PR ASAP for this
17:17:50 <jamesn> https://github.com/w3c/aria/tree/Mar_2016_Heartbeats
17:20:11 <jamesn> agenda?
17:20:17 <jamesn> zakim, take up item 1
17:20:18 <Zakim> agendum 1. "Example reviews and update pattern work assignments https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status" taken up [from jamesn]
17:20:27 <jemma> present+ JaeunJemmaKu
17:21:24 <jamesn> mk: want to make sure that not missing anything. got more patterns ready for examples
17:21:36 <jamesn> setting aside until get aria 1.1 combo box text final
17:21:51 <jamesn> I think we will want an ARIA 1.0 combo box and a 1.1 combo box
17:22:12 <jamesn> other than that are there any other examples that youy know of which are done but have not been reviewed
17:22:27 <jamesn> JK: Jon is working on toolbar and tabpanel
17:22:37 <jamesn> MB: tabpanel was assigned to me
17:24:07 <jamesn> MB: want to look at issues - going to be looking at this at CSUN
17:24:21 <jamesn> MK: were we going to look at what was going to be shown at cSUN here
17:24:27 <jamesn> IP: indedpendent work
17:24:38 <jamesn> MK: what is being done at CSUN
17:25:13 <jamesn> IP: MB and IP have created 2 versions of tabpanel and accordion. we have patterns.
17:25:22 <jamesn> at csun will also do some f2f tests
17:26:32 <jamesn> MK: 2 different tab panels
17:26:53 <jamesn> IP: for accordion 2 versions - discolsure vs what is currently documented
17:27:07 <jamesn> MK: do either have tab versions
17:27:27 <jamesn> MK: what are the differences for the tab panel?
17:28:13 <jamesn> MB: 2 examples. 1 a simple tab panel example, the 2nd is a simplified version of the APG version where you can only tab to the active tab
17:29:49 <jamesn> JN: concerned as to how the results get interpreted based on the context
17:30:15 <jamesn> MK: curious to understand the context of the example where all of the tabs are in the tab order
17:30:51 <jamesn> MB: want to see if people associate a tab with disclousre buttons etc.
17:31:03 <jamesn> IP: questions are straightforward
17:37:16 <jamesn> present+ Bryan
17:45:59 <jemma> jemma has joined #aria-apg
17:46:02 <MichielBijl> scribe: jemma
17:46:21 <jemma> take up item 2
17:47:50 <mck>  is an element that displays a brief, important message in a way that attracts the user's attention without interrupting the user's task. Dynamically rendered alerts are automatically announced by most screen readers, and in some operating systems, they may trigger an alert sound. It is important to note that, at this time, screen readers do not inform users of alerts that are present on the...
17:47:52 <mck> ...page before page load completes.
17:48:43 <jemma> mk: does the address the intent of this bug?
17:49:11 <jemma> mb: I think so
17:50:01 <jemma> mk:what do you think about "at this time"
17:50:22 <jemma> mk: which screen reader do  not inform?
17:50:43 <jemma> s/the/this
17:51:48 <MichielBijl> mkc:  It is important to note that not all screen readers inform users of alerts that are present on the...
17:55:41 <jemma> bb: there is confusion about when alert added.
17:56:17 <jemma> take up item 3
17:58:47 <jemma> mk: we have dialog and non dialog which is clear
17:59:31 <jemma> mk: if it is focusable tooltip should not it be a dialog?
18:00:34 <jemma> bb:aria-own is rearranged a11y tree in new release in chrome and firefox
18:02:24 <jemma> bb: now we can manupulate the dom order
18:03:38 <jemma> mk: I am still thinking what dialog tooltip should be.  if tooltip has a link it is focusable. there is no standardized key to operate the tool tip
18:04:02 <jemma> BB: tooltip is usually overlay icon
18:04:11 <jemma> BB: to get help something
18:04:27 <jemma> mk: point of aria is on interaction
18:05:08 <jemma> BB: it is not desirable or necessary to trap the focus in the tooltip
18:05:24 <jemma> mk: what do you mean by "trapping"?
18:07:08 <jemma> MK: it sounds that it act like a dialog, you open and close it
18:07:21 <jemma> BB: tooltip is more of giving the contextual infor
18:07:43 <jemma> BB: not trapping user actions in the tooltip
18:09:53 <jemma> BB:quick thought,  would it be similar to footnote?
18:10:04 <jemma> s/bb/mb
18:11:13 <jemma> mk:dialog requires mechanism to open and close.
18:12:34 <jnurthen> jnurthen has joined #aria-apg
18:13:02 <jemma> mk: we are talking about Hover help
18:13:23 <jemma> mk:there is not standardized keyboard for tooltip
18:13:58 <jemma> BB: this involves lots of things, marking up correctly and more...
18:14:55 <jemma> mk: there should be a realistic example since people will learn from the example.
18:15:36 <jemma> mk: main thing is alerting screen user about presence of tooltip and enable keyboard users to get into it.
18:16:46 <jemma> BB: focus management and mousein/out problem in tooltip
18:18:55 <jemma> mk: short key for element can be used but short cut key is adjacent to overlay. how would you say to screen readers that this short key is related to tooltip?
18:19:30 <jemma> mk: some ui do not use separate icon and it is not in the tab order
18:19:56 <jemma> if tooltip has separate focusable icon, then it is easy
18:20:49 <jemma> mk: in that case, we may just refer back to dialog pattern.
18:21:26 <jemma> take up item 4
18:22:35 <jemma> mk: we wanted to tap panel as tap
18:22:44 <jemma> s/tap/tab
18:23:28 <jemma> mk: will create a bug for this
18:24:08 <mck> the label/title area of the tab panel. This is where you click to activate a tab panel
18:25:24 <mck> The element in a tablist that serves as the title for one of the tabpanels
18:26:42 <mck> The element in a tablist that serves as the title for one of the tabpanels. Activating a tab displays a tabpanel.
18:29:30 <jemma> mk: the way we address orientation in ARIA - like in tool bar should be used here too?
18:32:27 <jemma> mk: see the example, https://rawgit.com/w3c/aria/master/practices/aria-practices.html#toolbar
18:32:43 <jemma> for vertical orientation
18:33:16 <jemma> mk: we should be consistent in the pattern
18:34:11 <jemma> mk: will create a bug about tab panel including orientation.
18:35:53 <jemma> rrsagent, make log world
18:36:13 <jemma> rrsagent, generate minutes
18:36:13 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/14-aria-apg-minutes.html jemma
18:42:51 <jemma> chair:Matt_King
18:43:06 <jemma> rrsagent, generate minutes
18:43:06 <RRSAgent> I have made the request to generate http://www.w3.org/2016/03/14-aria-apg-minutes.html jemma
19:44:54 <jamesn> jamesn has joined #aria-apg
23:00:39 <IanPouncey> IanPouncey has joined #aria-apg