14:52:45 RRSAgent has joined #mobile-a11y 14:52:45 logging to http://www.w3.org/2016/10/06-mobile-a11y-irc 14:52:47 RRSAgent, make logs public 14:52:47 Zakim has joined #mobile-a11y 14:52:49 Zakim, this will be WAI_MATF 14:52:49 ok, trackbot 14:52:50 Meeting: Mobile Accessibility Task Force Teleconference 14:52:50 Date: 06 October 2016 14:53:00 chair: Kimberly_Patch 14:53:34 Agenda + Continuation of SC review - https://github.com/w3c/Mobile-A11y-Extension/tree/gh-pages/SCs , https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/WCAG_2.1_Success_Criteria_Submission_Requirements 14:53:36 M4 - https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m4.md 14:53:37 M10 - https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m10.md 14:53:39 Agenda + Next steps and schedule 14:59:19 regrets+ jeanne 14:59:23 Regrets+ Henny, Chris 14:59:56 laura has joined #mobile-a11y 15:02:54 Detlev has joined #mobile-a11y 15:07:02 scribe: Detlev 15:07:21 patrick_h_lauke has joined #mobile-a11y 15:07:28 Zakim, take up next 15:07:28 agendum 1. "Continuation of SC review - https://github.com/w3c/Mobile-A11y-Extension/tree/gh-pages/SCs , 15:07:30 present+ patrick_h_lauke 15:07:31 ... https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/WCAG_2.1_Success_Criteria_Submission_Requirements" taken up [from Kim] 15:07:42 marcjohlic has joined #mobile-a11y 15:07:51 present+ Detlev 15:08:04 M4 - https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m4.md 15:08:05 https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m4.md 15:09:13 Kim; lets continue work on M4 15:10:46 Patrick: M4 SC plugs hole in current WCAG SC - covers situation where kb-operated environments may have problem when AT 'steals' keyboard events 15:11:15 ...AT may intercept keystrokes and not let it get to JS 15:12:01 ...Keyboard with AT (that remaps key input) 15:12:35 Patrick: (reads / presents contents of proposed SC 15:13:54 Patrick: Manual test using KB with AT on and see if everything works 15:14:01 q+ 15:14:30 Kim: Can text be simplified? 15:15:14 Patrick: makes note 15:15:16 Kim: what is the solution? 15:16:05 Patrick: work with focusable controls, use events like blur 15:16:28 Patrick: Avoid general keyboard commands 15:18:22 Patrick: Will look at adding to the description to make it clearer 15:23:37 Patrick: Other issues with keyboard commands fall within other proposed SCs so it is better to keep it specific - the WG may merge it wqith others and that could change the name 15:24:23 Kim: Are there more techniques related to this? 15:24:46 Patrick: A failure technique could be appropriate, with remedies / alternatives 15:25:46 Marc: Likes SC 15:26:30 Zakim, take up next 15:26:30 I see a speaker queue remaining and respectfully decline to close this agendum, Detlev 15:26:45 M10 - https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m10.md 15:26:53 q- 15:26:56 Zakim, take up next 15:26:56 agendum 2. "Next steps and schedule" taken up [from Kim] 15:27:27 Kim: Discussing sensors SC (M10) 15:28:46 Patrick: covers specific sensor inputs like tilt, orientation, pressure, shake 15:29:24 Patrick: This is about active inputs 15:29:46 KIM. so functionality should be provided also in some other way 15:30:44 Patrick: Ability of users to make use of sensors may be limite so functionality should be triggerable by some other method 15:31:27 Patrick: Use cases: mounted tablet, mobile in hands-free cradle, etc 15:32:12 Kim: We should have an example also in M4 15:33:05 Marc: Examples wil be important to make that easy to grasp - maybe already i the description section 15:34:00 Marc: what sensores are covered? 15:34:15 Patrick: Fairly open - others may arrive 15:34:27 Marc: is proximity included 15:35:09 Patrick: Sensing that phone is close to your head would be an example for proximity 15:35:36 Marc: Looking to include sensore / applications that are yet to be developed 15:36:11 Patrick: Lighr sensor might work to cover proximitiy 15:36:47 Shadi: My phone changes brightness acc. to ambient light 15:37:16 Patrick: That's probably not an active input 15:37:48 Patrick: But enabling user to overwrite sensor could still be useful 15:38:06 Kim: Suggest editorial change 15:39:26 Patrick: Testability is difficult - discovering if any additional sensors do something 15:40:27 Kim: The author would know if sensors do things, the auditor may be made aware of it 15:41:04 q+ 15:41:35 [[without relying on the sensors alone]] 15:43:59 Detlev: any limits on what counts as alternative 15:44:44 Kim: Finding a deleted item in a file system would not quailfy as the shake undo 15:45:29 Kim: Undo is a discrete one stop action - so wouldn't a button that does the same thing be the equivalen`? 15:45:44 Patrick: Shake is a shortcut 15:46:13 Kim: No it is a speciifc function not a shortcut 15:47:18 David: entering call 15:47:26 David_ has joined #mobile-a11y 15:47:33 test 15:47:39 M10 - https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m10.md 15:48:21 Patrick: arguing that the discussion we're having is "does iOS mail's undo function pass this SC we're proposing" which is a slightly separate discussion to the actual merits of this SC 15:49:48 Patrick: Alternative could be button, menu option or control - no hard technique thart should be required 15:50:40 David: Reminds of language of 2.1.1 All functionality can be operated... 15:52:22 David: would we describe change of orientation of page as 'function'? 15:53:07 Patrick: Example like shooting by tilting, changing orientation to trigger something 15:53:27 functionality processes and outcomes achievable through user action 15:53:39 that is the WCAG definition 15:53:44 Kim: Another use case might be putting device upside down to change position of mic 15:53:57 https://www.w3.org/TR/WCAG20/#functiondef 15:55:32 All functionality of the content is operable without requiring specific device sensor information. 15:55:39 Kim: Screen orientation - a recorder might change if you turn it upside down (so it corrects) 15:56:15 Patrick : A functional change would be changing recording functionality if you change orientation 15:56:51 Patrick: There wil be grey areas - we should be fine for now 15:57:48 David: Suggests wording "All functionality of the content is operable without requiring specific device sensor information." 15:59:03 Patrick: Might be confusing to talk about functionality of content - is there other functionality? 15:59:13 Kim: Keept it short and snappy 16:00:10 Patrick: Will leave wording detaisl to larger WG 16:00:16 +1 16:00:36 David: Boneyard needed? 16:00:43 Patrick: Minutes 16:00:59 Kim: Closes meeting 16:03:07 Note: Patrick will email the links to M4 and M10 to the list after he makes today's changes. 16:03:31 patrick_h_lauke has left #mobile-a11y 16:03:55 Regrets + Allen, Jatiin 16:04:21 Present+ Kim, Detlev, Patrick, David, Marc 16:06:27 rrsagent, make minutes 16:06:27 I have made the request to generate http://www.w3.org/2016/10/06-mobile-a11y-minutes.html Kim 16:10:51 Regrets- Allen, Jatiin 16:16:17 rrsagent, bye 16:16:17 I see no action items