14:43:19 RRSAgent has joined #mobile-a11y 14:43:19 logging to http://www.w3.org/2015/10/01-mobile-a11y-irc 14:43:21 RRSAgent, make logs public 14:43:21 Zakim has joined #mobile-a11y 14:43:23 Zakim, this will be WAI_MATF 14:43:23 I do not see a conference matching that name scheduled within the next hour, trackbot 14:43:24 Meeting: Mobile Accessibility Task Force Teleconference 14:43:24 Date: 01 October 2015 14:43:59 chair: Kathy Wahlbin 14:44:43 agenda? 14:45:00 agenda+ Mobile Techniques 14:45:40 agenda+ Discussion of Touch Proposal 14:45:54 agenda+ Wirting Assignments 14:46:00 agenda+ Next Steps 14:46:03 agenda? 14:55:41 jeanne has joined #mobile-a11y 15:00:48 David has joined #mobile-a11y 15:01:15 agarrison has joined #mobile-a11y 15:02:59 present+ Kathy 15:03:18 +agarrison 15:03:21 +jeanne 15:03:23 +David_MacDonald 15:03:35 rrsagent, make minutes 15:03:35 I have made the request to generate http://www.w3.org/2015/10/01-mobile-a11y-minutes.html jeanne 15:03:57 zakim, list attendees 15:03:57 As of this point the attendees have been Kathy, agarrison, jeanne, David_MacDonald 15:04:00 rrsagent, make logs public 15:04:48 zakim, pick a victim 15:04:48 Not knowing who is chairing or who scribed recently, I propose David_MacDonald 15:05:29 marcjohlic has joined #mobile-a11y 15:05:34 present+ jeanne, agarrison, David_MacDonald, Detlev 15:06:02 scribe:Detlev 15:06:05 rrsagent, make minutes 15:06:05 I have made the request to generate http://www.w3.org/2015/10/01-mobile-a11y-minutes.html jeanne 15:06:19 Zakim, take up first item 15:06:19 I don't understand 'take up first item', Detlev 15:06:29 Zakim, take up next 15:06:29 agendum 1. "Mobile Techniques" taken up [from Kathy] 15:06:46 https://w3c.github.io/Mobile-A11y-Extension/ 15:06:46 present+ marcjohlic 15:07:38 Kathy: Mobile-A11y-Extension is a sketch how the extension framework is going to play out 15:08:03 Kathy: SOme new mobile techniques, others go under existing techniques 15:08:56 Kathy: ..organised by guidelines. What's your thoughts? 15:09:10 jon_avila has joined #mobile-a11y 15:09:15 present+jon_avila 15:09:24 q+ 15:09:24 Henny has joined #mobile-a11y 15:09:47 Jeanne: Doc is in Respect to support automated publishing 15:10:04 So, is it like http://www.w3.org/TR/mobile-accessibility-mapping/ - just cut up into techniques? 15:10:33 q? 15:10:39 Jeanne: Changes only made via github pull requests - don't add anything to it directly, especially no J, may cause issues 15:11:34 q 15:11:41 q+ 15:12:00 David: 2.5.1 structure issue - CSS is not correct yet 15:12:21 David: 2.5.1 should not remain in here 15:12:57 Kathy: This is agreed stuff but not yet public 15:13:18 David: Should WCAG be in here and the new stuff added? 15:14:00 Kathy: Should help place new mobile techniques under the relevant success criteria - but it's open to discussion 15:14:27 David: Not clear what the proposal is - copying all of WCAG in here? 15:15:01 David: People shouldn't perceive this as the updated full WCAG 15:15:23 Kathy: How shall we otherwise present techniques 15:15:48 David: Maybe it is enough to reference the WCAG guideline /SC numbers to make the difference obvious 15:16:32 +1 to short handles of WCAG and adding it to the Status 15:16:37 Kathy: Status of the doc should clarify the difference to exisitng WCAG - that it is to be considered in addition to WCAG 15:16:47 q? 15:17:29 Alistair: mobile accessibility mapping is structured in a similar way (see URL above) 15:18:21 Kathy: this wasn't structured as extension - some are best practices - we started with touch accessibility and added necessary things 15:18:50 Kathy: Not xyet decided what will happen with the note - the extension is where things will go 15:18:54 http://davidmacd.com/blog/WCAG-extension-proposed-integration-into-WCAG.html 15:19:12 Kathy: WCAG WG is currently working out how the extension should work 15:20:08 Kathy: THis is an overview t facilitate a suggestion how the different reqs will fit into the extension (LV, cognitive, mobile) 15:20:31 Kathy: Intended as outline of normative extension 15:21:07 Kathy: Extension is supposed to just add to, not subtract from WCAG 2.0 15:22:10 Alistair: Maybe the text from WCAG should be brought over so people can see what gets extended where 15:22:35 AListair: Will provide more context - may be changed later 15:23:31 David: This has no educational purpose ATM - no changes to normative WCAG 2.0 expected , no crossing out 15:24:47 Jeanne: Stil early days in figuing out what the extension will mean - all thoughts are OK now, Mobile a11y TF is spearheading the process, so it is valuable to identify issues (like having to make changes to normative WCAG 2.0) 15:26:01 Kathy: End user aspect, like people creating responsive sites - would it make sense to have new mobile SC with different twechniques - the actual end user will know what is required for accessible development 15:26:32 Kathy: For them it will be easier to have all relevant info in one place rather than resort to different places 15:27:03 q+ 15:27:05 Kathy: We have to consider end user view and usability of this documentation 15:27:22 q? 15:27:29 q- 15:28:04 David: We need a view (quickref) to synthesize stuff, incl. mobile 15:28:35 q+ 15:28:50 David: Still early days - it may be more difficult to manage to include all, it's a working doc for us 15:29:08 David: Should be easy to aggregate for developers later 15:29:26 Kathy: Withing the Quickref there canbe new guidelines and SC 15:30:26 Kathy: UAAG and WCAG chairs need input on how we can bring together the different user needs and requirements 15:31:18 Alistair: Reading in different documents looks like a problem - easier to have one synthesized doc 15:31:35 Alistair: Looks different on a mobile browser 15:32:09 Kathy: Not sure how to bring in hybrid apps using web views 15:32:43 Kathy: muich of it is platform specific (iOS / ANdroid etc) 15:33:03 q+ 15:33:10 Kathy: Current focus is straight web sites 15:33:13 ack Dav 15:33:17 ack ag 15:33:30 Alistair: THe extensio bnmodel may also apply to techniques 15:34:02 Alan_smith has joined #mobile-a11y 15:34:08 + Alan 15:34:24 Jeanne: Whne req for updated Quickref were developed the need for a filter for 'mobile' was included 15:35:37 Jeann: we can be specific to the area the techniques apply to 15:35:51 David: We need mor techniques - including for hybrid 15:36:32 Jeanne: One topic is text-resizing which could be modified for different mobile paltforms 15:37:17 Kathy: will send out info on that 15:37:20 q- 15:37:30 ack jea 15:38:15 s/Jeanne: One topic is/Kathy: One topic is 15:38:38 Kathy: We should go back to see what is mobile specific, like 1.3.3 Sensory characteristics - but telling people where somethign is on the screen coan be really helpful, such things should be taken into account 15:38:55 Kathy: A technique just being one way to meet the criteria 15:39:42 Kathy: Lets put techniques out to get feedback on what will prove helpful for the new tocuh interaction paradigm 15:39:57 q+ 15:41:01 Alistair: 3D touch brings in new aspects, also time touch on Android 15:41:36 Alan: Things like duration can be very helpful for some users 15:43:12 David: We need to take into account the WCAG philosophy - there is a tension between actual use cases and the standard. There are sometimes new tech solutions which beg the question what should be required 15:43:18 q? 15:43:32 q- 15:43:56 http://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Touch_Accessibility_%28Guideline_2.5%29 15:43:58 Kathy: This doc is a snapshot of current agreements - we can countinue using Wiki 15:44:09 Zakim, take up next 15:44:09 agendum 2. "Discussion of Touch Proposal" taken up [from Kathy] 15:44:10 http://w3c.github.io/Mobile-A11y-TF-Note/TouchProposal_Discussion.html 15:44:59 Kathy: Davids wording solution - from equiring touch access to requiring that all touch access also works with AT turned on 15:45:24 David: Charter tells us we are authorized to develop extensions 15:45:57 David: There may be overlap between requirements, say of cognitive and moble, so we may wend up with just one extension 15:46:30 This would address concern about complexity of having several extensions 15:47:14 Input from different TFs could feed into one extension - the process should encourage discussion to combine SC whereever possible 15:47:34 The Quickref will then bring that together for the outside user 15:47:53 David: Diagram has gained traction lots of +1 15:48:23 Alistair: Do Working groups work to common time scales? 15:48:35 David: No real coordination so far 15:49:25 Kathy: A challenge is the coordination between what the different task forces are doing 15:50:01 The WG needs to look at that and define how the results are going to be combined - it's currently being worked out within WG 15:50:24 Kathy: This should not become a bottleneck but is a serious concern 15:51:17 Kathy: What are the basicv rules for extensions? It's likely that there will be several extensions, not one 15:51:37 David: should be one extension at the ens of the day 15:52:06 q? 15:52:07 David: the idea is to speed up the overall process - extensions will be easier 15:53:06 Kathy: The way the focus on the working group topic and interaction with others work is still not finalised 15:53:33 All functions available by touch (or button presses) are still available by touch (or button presses) after system assistive technology is turned on. 15:53:34 Kathy: Point about 2.5.4 Proposal 15:54:20 Kathy: The general gist was that everything that is offered for touch should also work with AT turned on - has anyone worked on the SC text? 15:54:45 2.5.4 Modified Touch (5th draft): All functions available by touch (or button presses) are still available by touch (or button presses) after system assistive technology is turned on. 15:55:18 q+ 15:55:44 Suggested Modification: 2.5.4 Modified Touch (5th draft): All functions available by touch (or button presses) are available by touch (or button presses) with system assistive technology. 15:56:04 David: pointing to the latest draft of 2.5.4 - focus ios that everything has to work for people using AT - there is no pass-through gesture on Android - most is already available after pass-throuigh gesture. Not so on Android 15:56:14 In my experience on iOS the pass through gesture doesn't allow you to lift your first -- I wonder if that could an issue. 15:56:35 David: Good wording for SC 15:57:22 Alistair: Impact on AT, example on date picker. AT can have big impact on a11y 15:58:04 What assistive technology? If it works with Assistive Touch but not with VO -- it's available with AT but not with all. 15:58:15 Alistair: There may be unwanted interactions between different gestures for touch 15:59:12 q- 15:59:19 David: In theory the pass-through gesture (on iOS) should enable other gestures 15:59:41 Jon: Pass through gesture may not work in some cases 16:00:11 Jon: Some gestures may work with some AT (assistive touch) but not with VoiceOver 16:00:38 Jon: The wording is a challenge, may not be specific enough yet 16:00:53 David: We cannot enumerate all potential AT 16:01:26 Jon: We don't have a standard interface to work with like on the desktop. lots of inconsistency 16:02:25 David: The intention was that with any AT needed touch would work - focusing on the system level 16:02:50 Kathy: Please think about wording, make suggestions for changes 16:03:02 My technique m23 is in draft form and ready for a review. It is on github. 16:03:18 Kathy: Lets pick up discussion next week 16:03:47 M007 was updated from my github version 16:03:51 Kathy: Kim and Jeanne won't be around for next few meetings 16:04:28 Zakim. list attendees 16:04:37 Zakim, list attendees 16:04:37 As of this point the attendees have been Kathy, agarrison, jeanne, David_MacDonald, Detlev, marcjohlic, jon_avila, Alan 16:04:52 rssagent, make minutes 16:05:12 rrsagent, make logs public 16:05:23 rrsagent, make minutes 16:05:23 I have made the request to generate http://www.w3.org/2015/10/01-mobile-a11y-minutes.html Kathy