14:57:50 RRSAgent has joined #mobile-a11y 14:57:50 logging to http://www.w3.org/2016/09/29-mobile-a11y-irc 14:57:52 RRSAgent, make logs public 14:57:52 Zakim has joined #mobile-a11y 14:57:54 Zakim, this will be WAI_MATF 14:57:54 ok, trackbot 14:57:55 Meeting: Mobile Accessibility Task Force Teleconference 14:57:55 Date: 29 September 2016 14:58:04 zakim, this will be 6283 14:58:04 ok, Kathy 14:58:18 rrsagent, make log world 14:58:26 meeting: Mobile A11Y TF 14:58:38 chair: Kathy 15:01:14 Alan_Smith has joined #mobile-a11y 15:02:06 regrets: Kim, Jeanne, Patrick, Henny, Chris 15:02:17 Present+ Kathy 15:02:49 Present+ Alan 15:03:49 Present+ Detlev 15:04:59 Jatin has joined #mobile-a11y 15:05:25 jon_avila has joined #mobile-a11y 15:05:29 present+jon_avila 15:05:38 present+ Jatin 15:05:55 marcjohlic has joined #mobile-a11y 15:12:22 sounds great! 15:12:45 scribe: jon_avila 15:13:09 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/WCAG_2.1_Success_Criteria_Submission_Requirements 15:13:22 kw: were going to talk about m4 and m10 that patrick had finished more than others -- but since he can't make the call we will talk David's new one 15:13:28 https://github.com/w3c/wcag21/issues/2 15:13:46 kw: related to page titles -- good to review in this meeting and finalize David's 15:14:38 david__ has joined #mobile-a11y 15:15:22 dm: old problem that we didn't have a solution to and now we do 15:15:34 dm: would be change of content -- different from change in context 15:15:52 dm: want to notify users that there is a change 15:16:26 dm: need to notify blind users that changes occurred 15:16:54 dm: exceptions - if change immediately follows activating element 15:17:18 dm: exception for a programmatic relatinoshnip 15:17:55 q+ 15:18:39 dm: borrowed a lot of language from current WCAG 15:19:01 dm: whether or not triggered by the user. 15:19:50 ja: shouldn't apply when page is actually refreshed 15:20:31 q+ 15:21:24 Jon: can the scope be extended to users who are not blind (cognitive, low vision)? 15:21:34 ja: would like this apply in way to help users with low vision and users with cognitive disabilities 15:22:01 dm: coga has one that is similar and we could combine after this gets to the WG 15:22:43 q+ 15:23:00 dm: coga one calls for rapid feedback that indicates audio cues must be cues 15:23:13 dm: coga has post user action confirmation 15:23:58 jon: SC ON input allows that users are notified beforehand 15:24:41 Jon: exception "unless the user has been advised... 15:26:52 alan: gave example of filter that might reset fields above current control 15:27:12 q? 15:27:45 ack Detlev 15:27:49 q+ 15:28:08 detlev: in case of reset button there is an expectation. We need to take into context the element -- unnecessary to have a description of what the reset button does 15:28:48 detlev: wasn't sure if new SC applies to content changes that are user interactive or both? 15:28:52 both 15:29:26 detlev: sees them as different -- ARIA vs. user intiated are different as user has some expectation that something will happen. Maybe they should be different? 15:31:10 dm: have an exception for controls that follow in the programmatic reading order. Could be clear that this is the order that a screen reader follows such as if you move the focus. 15:32:29 q- 15:33:25 dm: adding focus managed by webpage 15:33:26 q? 15:34:29 mj: going back to exception #2 -- way I read it is provide programmatic notification -- which seems like it is already covered in the title of the best practices 15:35:44 ja: may be difference between programmatic notification and programmatic relatinoship such as ARIA live versus aria-cotnrols 15:36:27 q? 15:37:52 ack marc 15:37:58 q+ 15:40:34 kw: thinking about a couple of scenarios -- not sure if they fall under this. See with usability studies such as loading indicator -- maybe short or long depending on the users connection 15:40:44 kw: not just knowing something is loading but that something finished loading 15:40:52 https://github.com/w3c/wcag21/issues/3 15:41:30 dm: another proposed SC 15:41:44 kw: got some comments about page title and mobile specifically 15:42:05 kw: mobile apps dynamically change content and page title doesn't update and difficult to know what the page content is\ 15:42:37 kw: 2.4.2 might be missing - but doesn't say that it has to be unique or specific to the content on the page. 15:43:17 dm: doesn't require page title change but helps with change 15:43:20 q? 15:44:18 dm: topic or purpose is a very broad statement 15:45:29 Jon: title is preferable because users are sure to become aware of changes 15:46:31 kw: titles aren't as readily available on mobile 15:46:44 dm: is this close enough to submit from this group? 15:48:13 dm: what about a baseball game -- if there were too many updates it might be unusable 15:48:58 detlev: commenting on page loading, etc. 15:49:06 q? 15:50:45 kw: same thing with timed tests with count down 15:51:05 ja: need to find a way to allow for some countdown or animation or other content, etc. 15:51:11 q- 15:51:17 dm: may be able to characterize exceptions into groups 15:51:51 q+ 15:52:14 dm: may need to create a threshold number 15:52:38 kw: maybe put placeholder in for now 15:52:56 dm: want to be testable in placeholder 15:53:19 kw: unless notification would significantly interupt 15:54:44 q- 15:55:02 q+ 15:55:21 dm; notifications are more than x per minutes 15:56:08 detlev: couldn't make sense that this would hold up in all context such as games -- so times you may want the notifications and other you will not 15:57:13 dm: similar objections and use cases that were outliers 15:57:32 dm: not forbudding --- authors can have mroe 15:58:08 q? 15:58:21 q- 15:58:28 dm: how do you know what x per minute is? 15:59:28 ja: does this allow people to do nothing if it occurs to frequently or is variable? 16:00:49 kw: take a look at two SC that were in the agenda -- would like to finalize them next. We need to keep finalize them. 16:01:38 dm: do we want to take a resolution on this proposed SC? 16:01:53 kw: can unless there is an objection. 16:02:03 dm: that we will take this over and submit as MATF with adjustments 16:02:08 kw: any objections? 16:02:11 Alan + 16:02:12 kw: hearing none 16:02:41 RESOLUTION: will accept M15 Programmatic Notifications and submit to working group 16:03:05 dm: notification of busy signal we will take up on later date. 16:04:21 rrsagent make minutes 16:05:44 rrsagent end call 16:05:57 rrsagent, make minutes 16:05:57 I have made the request to generate http://www.w3.org/2016/09/29-mobile-a11y-minutes.html jon_avila 16:06:11 zakim, list attendees 16:06:11 As of this point the attendees have been Kathy, Alan, Detlev, jon_avila, Jatin 16:06:33 present+marcjohlic 16:06:48 present+david__ 16:06:56 trackbot, end meeting 16:06:56 Zakim, list attendees 16:06:56 As of this point the attendees have been Kathy, Alan, Detlev, jon_avila, Jatin, marcjohlic, david__ 16:07:04 RRSAgent, please draft minutes 16:07:04 I have made the request to generate http://www.w3.org/2016/09/29-mobile-a11y-minutes.html trackbot 16:07:05 RRSAgent, bye 16:07:05 I see no action items