15:51:12 RRSAgent has joined #mobile-a11y 15:51:12 logging to http://www.w3.org/2015/02/26-mobile-a11y-irc 15:51:14 RRSAgent, make logs public 15:51:14 Zakim has joined #mobile-a11y 15:51:16 Zakim, this will be WAI_MATF 15:51:16 ok, trackbot; I see WAI_MATF()11:00AM scheduled to start in 9 minutes 15:51:17 Meeting: Mobile Accessibility Task Force Teleconference 15:51:17 Date: 26 February 2015 15:52:39 chair: jeanne 15:56:02 agenda+ Comments received (changes will be included in a future version of 15:56:02 the note) 15:56:14 agenda+ New techniques 15:56:40 agenda+ Next Steps face-to-face Tuesday 2-4 Pacific time 15:58:50 WAI_MATF()11:00AM has now started 15:58:57 +Jeanne 15:59:30 HennySwan has joined #mobile-a11y 16:01:24 Jan has joined #mobile-a11y 16:01:33 +[IPcaller] 16:01:57 +[IPcaller.a] 16:02:04 +Alan_Smith 16:02:15 zakim, IPcaller is Henny 16:02:18 +Henny; got it 16:02:28 zakim, IPcaller.a is Jan 16:02:28 +Jan; got it 16:02:58 Alan_Smith has joined #mobile-a11y 16:03:00 marcjohlic has joined #mobile-a11y 16:03:11 +TomB 16:04:21 jon_avila has joined #mobile-a11y 16:05:30 Scribe: Jan 16:05:43 zakim, agenda? 16:05:43 I see 3 items remaining on the agenda: 16:05:44 1. Comments received (changes will be included in a future version of [from jeanne] 16:05:44 2. New techniques [from jeanne] 16:05:44 3. Next Steps face-to-face Tuesday 2-4 Pacific time [from jeanne] 16:06:20 +[IPcaller] 16:06:29 zakim, I am IPcaller 16:06:29 ok, jon_avila, I now associate you with [IPcaller] 16:06:32 JS: The first public WD of the Note is ALMOST published 16:06:55 JS: Thanks to everyone for your help 16:08:30 Zakim, take up agendum 1 16:08:30 agendum 1. "Comments received (changes will be included in a future version of" taken up [from jeanne] 16:08:41 https://www.w3.org/WAI/EO/wiki/Mobile_Accessibility_Note_-_EOWG_Review_Feb_2015 16:09:19 JS: Where did we leave off? 16:09:27 AS: I think we finished Melody's 16:09:30 http://www.w3.org/2015/02/19-mobile-a11y-minutes.html#item02 16:10:29 JS: So we are at 1.2.2 16:10:41 [Comment: Give an example of what an authoring tool is, similar to the examples in the UAAG section.] 16:11:07 JR: I Can help Jeanne 16:11:19 action: Find examples of authoring tools for 1.2.2 16:11:19 Error finding 'Find'. You can review and register nicknames at . 16:11:46 2.1 Small Screen Size 16:11:47 -TomB 16:11:50 [Comment: What is considered small screen size vs medium vs large? Screen sizes are generally blurring across the spectrum. http://www.fastcodesign.com/1673162/the-disintegration-of-android-visualized#1] 16:12:39 +TomB 16:13:16 -Jan 16:13:25 +[IPcaller.a] 16:13:38 zakim, [IPcaller.a] is Jan 16:13:38 +Jan; got it 16:17:08 http://w3c.github.io/Mobile-A11y-TF-Note/ 16:17:49 http://www.w3.org/WAI/GL/mobile-a11y-tf/WD-mobile-accessibility-mapping-20150224/ 16:18:18 JR: Don't think we should be defining screen size ranges 16:18:25 JA: Why not just mobile screen sizes 16:18:49 Small screen size is one of the most common characteristics of mobile devices. While the exceptional resolution of these screens theoretically enables large amounts of information to be rendered, the small size of the screen places practical limits on how much information people can actually view at one time, especially when magnification is used by people with low vision. 16:19:10 +??P7 16:19:36 -Henny 16:20:28 JR: Maybe the group needs an FAQ somewhere? 16:20:41 + Ala 16:21:13 +[IPcaller.a] 16:21:25 Resolution: We keep the term "small screen size" and add FAQ somewhere to answer question such as related to screen size and resolution 16:22:12 While the exceptional resolution of these screens theoretically enables large amounts of information to be rendered," [Comment: Not sure what this actually means in terms of large amounts of information. High resolution screen size has little to do with screen real estate for content. Other advantages and problems result from variance in screen resolution. Also, a small screen size, 16:22:12 doesn’t equal better resolution. A 15” retina MacBook pro has better resolution than an iPhone 4. Therefore, I don’t think this sentence is needed here.] 16:25:27 JA: Lets try to remove the term resolution. 16:25:57 While the current mobile screen technology theoretically enables large amounts of information to be rendered, 16:25:58 +Marc_Johlic 16:26:36 JR: Or just switch exceptional->high 16:26:58 JR: In case they think we are claiming mobile devices always have higher res 16:27:44 Small screen size is one of the most common characteristics of mobile devices. While the current mobile screen technology theoretically enables large amounts of information to be rendered, the small size of the screen places practical limits on how much information people can actually view at one time, especially when magnification is used by people with low vision. 16:28:05 Small screen size is one of the most common characteristics of mobile devices. While mobile screen technology theoretically enables large amounts of information to be rendered, the small size of the screen places practical limits on how much information people can actually view at one time, especially when magnification is used by people with low vision. 16:28:52 Alan + 16:29:00 +1 16:29:23 Resolution: REWORD paragraph as "Small screen size is one of the most common characteristics of mobile devices. While mobile screen technology theoretically enables large amounts of information to be rendered, the small size of the screen places practical limits on how much information people can actually view at one time, especially when magnification is used by people with low vision." 16:30:01 action: jeanne to update Note with Marc's comment from 19 Feb minutes and Resolution from 26 February 16:30:01 Created ACTION-20 - Update note with marc's comment from 19 feb minutes and resolution from 26 february [on Jeanne F Spellman - due 2015-03-05]. 16:32:19 Minimizing the amount of information that is put on each page compared to desktop/laptop versions by providing a dedicated mobile version or a responsive design:" 16:32:19 [Comment: From a good user experience and user interface perspective, you want to provide consistent user experience regardless of screen sizes yet tailored to use case for the device (i.e. using a site on a wearable vs. mobile phone vs. desktop may have different use cases). However, that doesn't mean that you should reduce amount of information. A best practice is to design sites with 16:32:19 mobile in mind first and rethinking the content layout and relevancy of content rather than “amount of information”. Take Instagram for example, the content on their mobile app is richer than the content on desktop. Therefore, this statement is already nullified.] 16:34:42 MJ: "extraneous" information 16:34:56 JR: Maybe also add a mobile-first bullet 16:35:26 JS: Maybe also put "a responsive design"bullet first 16:35:50 JA: Maybe tailor, adapt, customize rather than minimize 16:36:48 Kim has joined #mobile-a11y 16:37:00 -[IPcaller.a] 16:37:07 JS: Prioritize? 16:37:20 JA: Not write word 16:37:33 +Kim_Patch 16:37:37 JA: Craft? 16:38:21 +[IPcaller.a] 16:40:25 Where necessary, reducing the amount of extraneous information that is put on each page compared to desktop/laptop versions by providing a dedicated mobile version or a responsive design: 16:41:01 marcjohlic_ has joined #mobile-a11y 16:42:01 Where necessary, reduce extraneous information that is put on each page compared to desktop/laptop versions by providing a dedicated mobile version or a responsive design: 16:42:54 Where necessary, adapt the relevant material in a manner that adapts to different screen size 16:43:07 Where necessary, adapt the information that is put on each page compared to desktop/laptop versions by providing a dedicated mobile version or a responsive design: 16:44:06 Where necessary, adapt the information provided by on mobile compared to desktop/laptop versions by providing a dedicated mobile version or a responsive design: 16:44:24 Where necessary, adapt the information provided by on mobile compared to desktop/laptop versions with a dedicated mobile version or a responsive design: 16:44:44 Where necessary, adapt the information provided on mobile compared to desktop/laptop versions with a dedicated mobile version or a responsive design: 16:47:07 JA: Also mobile-first? 16:47:36 JR: Yes, as top level bullet above the "Where necessary one..." 16:48:25 Design sites with mobile in mind first and rethink the content layout and relevancy of content. 16:48:34 action: jeanne to change first bullet in 2.1 to "Where necessary, adapt the information provided on mobile compared to desktop/laptop versions with a dedicated mobile version or a responsive design:" 16:48:35 Created ACTION-21 - Change first bullet in 2.1 to "where necessary, adapt the information provided on mobile compared to desktop/laptop versions with a dedicated mobile version or a responsive design:" [on Jeanne F Spellman - due 2015-03-05]. 16:49:37 should we put responsive design before dedicated mobile version? 16:49:53 Consider mobile when initially designing sites and rethink the content layout and relevancy of content. 16:50:05 I agree with Alan to switch the order of the sub-bullets 16:50:34 I agree with Alan re: the 2 sub bullets 16:51:23 Consider mobile when initially designing sites and rethink the layout and relevancy of content. 16:51:39 Alan + 16:52:21 Consider mobile when initially designing the layout and relevancy of content. 16:52:36 +1 16:52:53 JS: +1 16:52:54 +1 16:52:59 JR: +1 16:52:59 action: Jeanne to add new bullet as the first major bullet in 2.1 to say "Consider mobile when initially designing the layout and relevancy of content." 16:52:59 Created ACTION-22 - Add new bullet as the first major bullet in 2.1 to say "consider mobile when initially designing the layout and relevancy of content." [on Jeanne F Spellman - due 2015-03-05]. 16:54:56 ack me 16:57:26 Seaport B-IBM 16:57:27 2nd Floor 16:57:28 Next meeting on Mar 12 16:57:29 Seaport Tower 16:58:00 -Alan_Smith 16:58:01 -[IPcaller.a] 16:58:01 -Kim_Patch 16:58:04 -TomB 16:58:05 -Marc_Johlic 16:58:05 -[IPcaller] 16:58:06 -Jan 16:58:08 -Jeanne 16:58:09 WAI_MATF()11:00AM has ended 16:58:09 Attendees were Jeanne, Alan_Smith, Henny, Jan, TomB, [IPcaller], Michael_Cooper, Marc_Johlic, Kim_Patch 16:58:46 RRSAgent, make minutes 16:58:46 I have made the request to generate http://www.w3.org/2015/02/26-mobile-a11y-minutes.html Jan 16:58:52 RRSAgent, set logs public 16:58:57 Zakim, bye 16:58:58 Zakim has left #mobile-a11y 16:59:02 RRSAgent, bye 16:59:02 I see 4 open action items saved in http://www.w3.org/2015/02/26-mobile-a11y-actions.rdf : 16:59:02 ACTION: Find examples of authoring tools for 1.2.2 [1] 16:59:02 recorded in http://www.w3.org/2015/02/26-mobile-a11y-irc#T16-11-19 16:59:02 ACTION: jeanne to update Note with Marc's comment from 19 Feb minutes and Resolution from 26 February [2] 16:59:02 recorded in http://www.w3.org/2015/02/26-mobile-a11y-irc#T16-30-01 16:59:02 ACTION: jeanne to change first bullet in 2.1 to "Where necessary, adapt the information provided on mobile compared to desktop/laptop versions with a dedicated mobile version or a responsive design:" [3] 16:59:02 recorded in http://www.w3.org/2015/02/26-mobile-a11y-irc#T16-48-34 16:59:02 ACTION: Jeanne to add new bullet as the first major bullet in 2.1 to say "Consider mobile when initially designing the layout and relevancy of content." [4] 16:59:02 recorded in http://www.w3.org/2015/02/26-mobile-a11y-irc#T16-52-59-1