14:57:49 RRSAgent has joined #mobile-a11y 14:57:49 logging to http://www.w3.org/2017/10/12-mobile-a11y-irc 14:57:51 RRSAgent, make logs public 14:57:51 Zakim has joined #mobile-a11y 14:57:53 Meeting: Mobile Accessibility Task Force Teleconference 14:57:53 Date: 12 October 2017 14:59:09 MelanieP has joined #mobile-a11y 15:00:50 marcjohlic has joined #mobile-a11y 15:00:55 Kathy has joined #mobile-a11y 15:01:13 Kim - i am having network issues. I am trying to join the webex 15:04:30 patrick_h_lauke has joined #mobile-a11y 15:05:00 present+ patrick_h_lauke 15:05:01 I am still trying to connect to WebEx 15:05:07 is anyone else having problems? 15:05:24 not here 15:05:35 working for me (using app directly, rather than phoning in) 15:06:05 Working for me, I phoned in 15:06:24 early warning: will need to leave around 20 minutes to the hour to go pick up my little one i'm afraid 15:06:57 Is Kim on 15:07:01 Please start without me 15:07:12 I am trying to get this to work but WebEx will not connect 15:07:32 I was able to get in.. no issues here 15:08:11 scribe: patrick_h_lauke 15:08:58 Kim: any questions on device sensors? 15:09:16 Melanie: updated based on last week's feedback, but need help with github 15:09:28 scribe: Kim 15:10:30 TOPIC: Device sensors 15:10:32 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Device_Sensors_Understanding#Understanding_Device_Sensors 15:11:39 present+ Kathy 15:11:52 Melanie: issue – scaling to motion – two bullets to leave out in github – Kathy will move to get from wiki 15:11:53 https://rawgit.com/patrickhlauke/wcag21/concurrent-input-mechanisms/understanding/21/concurrent-input-mechanisms.html 15:11:58 TOPIC: concurrent input mechanisms 15:12:12 https://rawgit.com/patrickhlauke/wcag21/concurrent-input-mechanisms/understanding/21/concurrent-input-mechanisms.html 15:12:47 Patrick: it would impact everybody the same way not necessarily folks with disabilities I'm kind of okay with that 15:13:21 Kathy: actually a lot of WCAG 2.0 impacts all users, but impacts people with disabilities more 15:13:27 JakeAbma has joined #mobile-a11y 15:13:28 Patrick: if we have good examples that would illustrate that 15:13:36 present+ JakeAbma 15:14:06 present+ marcjohlic 15:14:16 Patrick: will push to github 15:15:49 (just say when you're done reading the proposed text) 15:18:55 Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or respect user settings. 15:20:06 Kathy: I think we need to have something in there about security of the content or to respect user settings 15:20:50 Kathy: discussion about security was that if a certain input mechanism compromises the security aspect of what they're entering in you can block a particular input method – so if there's a security risk you don't need – if I have to enter it only using a keyboard for some security reason that's an exception 15:24:05 A speech input user has trouble using the mouse keyboard, so use in speech when possible, but when talking with a colleague intermittently switches speech off and uses the mouse. 15:25:41 Another example: A speech input user has trouble using the mouse and keyboard, so uses speech when possible, but when talking with a colleague intermittently switches speech off and uses the mouse. 15:26:36 Patrick: if someone relies on using a mouse or mouse like interface and can't use the touchscreen they'll be heavily impacted 15:26:57 Patrick: resources – I'm not sure what level we want to keep these 15:27:29 Kathy: we should keep those in there, including your article 15:28:28 Kathy: we need to have things published out there on these topics and there's not a whole lot out there. If anybody has an article for things on there that relate – we need these 15:28:38 Kathy: does anybody have anything else – I think this is good 15:28:57 Patrick: I'm assuming we don't have to have the techniques done 15:29:36 Kathy: correct – we don't need that right this moment. The next steps are that these are going to go to the other taskforces,they'll give feedback and then it goes to the working group. They can get other user examples or other nuances they can put into these 15:30:38 TOPIC: Orientation 15:30:40 https://rawgit.com/w3c/wcag21/orientation/understanding/21/orientation.html 15:31:02 Marc: added examples where orientation is not locked 15:31:42 Orientation SC: Content is not locked to a specific display orientation, and functionality of the content is operable in all display orientations, except where display orientation is essential for use of the content. 15:34:31 Marc: put NA in resources 15:34:42 Kathy: could link to the original document we did about how this applies to mobile 15:35:26 Marc: using the word mobile all the time – this can apply to nonmobile too 15:35:32 I suggest replacing "mobile application" with "web content" 15:36:14 Melanie: is this applicable outside of mobile apps – browsers don't care 15:36:27 Kathy: you can do CSS 15:37:27 Patrick: CSS device adaptation – no browser yet supports but you can say only lock the display to portrait or landscape. Also the cheap version of that is just check width and height of viewport and say please turn your device – don't display anything untiil you've turned the device. So it is applicable to web content as well 15:37:55 Patrick: not purely on mobile – also desktop depending on aspect ratio – it may trigger the same kind of problem 15:38:23 Patrick: another quick comment – YouTube videos I would generalize that, just say videos can be displayed 15:39:29 Kathy: example 3 title E reader app 15:39:40 Kathy: people will think of this as being an actual application – web app 15:40:17 patrick_h_lauke has left #mobile-a11y 15:40:49 Marc: mobile applications and web apps on first reference? 15:42:10 Melanie: can we say mobile and web-based applications? 15:42:47 Marc: I'll clean up the rest of the mobile applications references 15:43:19 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Accessible_Name_Understanding#Intent 15:43:25 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Character_Key_Shortcuts_Understanding#Resources 15:48:22 https://www.w3.org/TR/2011/WD-html5-20110525/editing.html#the-accesskey-attribute 15:55:03 https://cdn.rawgit.com/chriscm2006/wcag21/2f25bd2c13b16363b19a07796112bf3eda19d3cb/understanding/21/contextual-information.html 15:57:36 https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC 15:58:36 Kathy: will put Kim's, Melanie's, Patrick's on and update document. and I'll email Lisa and Jim to tell them those are ready to review. We'll be working on techniques next time for the mobile stuff. 15:59:09 we didn't look at change of content – if you have comments on that let me know 15:59:41 Jake – mobile applications – technology agnostic we also have hybrid – we should have some kind of clear definition starting wiith ourselves 16:00:18 Jake: when we talk about native apps, hybrid version, also for this understanding – what Marc is working on. Definition would be useful 16:00:57 Kathy: we are working with the education and outreach group writing more for mobile, define things for mobile on the EO side. I can bring up your concern and make sure that we've got covered 16:02:42 Jake: for myself I talk about native specifically iOS and android. Hybrid some web content in the native. Web application web document with some functionality. It stays somewhere in the gray area for different people 16:03:11 Kathy: will touch base with the EO on that 16:03:59 JakeAbma has left #mobile-a11y 16:14:16 Present + 16:14:27 zakim, list participants 16:14:27 As of this point the attendees have been patrick_h_lauke, Kathy, JakeAbma, marcjohlic 16:15:13 Present+ Melanie, Kim 16:15:21 zakim, list participants 16:15:21 As of this point the attendees have been patrick_h_lauke, Kathy, JakeAbma, marcjohlic, Melanie, Kim 16:15:36 chair: Kathleen_Wahlbin 16:16:35 rrsagent, make minutes 16:16:35 I have made the request to generate http://www.w3.org/2017/10/12-mobile-a11y-minutes.html Kim 16:19:10 rrsagent, bye 16:19:10 I see no action items