14:41:22 RRSAgent has joined #lvtf 14:41:22 logging to http://www.w3.org/2016/01/20-lvtf-irc 14:41:24 RRSAgent, make logs public 14:41:26 Zakim, this will be 14:41:26 I don't understand 'this will be', trackbot 14:41:27 Meeting: Low Vision Accessibility Task Force Teleconference 14:41:27 Date: 20 January 2016 14:43:38 title: Low Vision Accessibility Task Force Teleconference 14:44:01 rrsagent, set logs public 14:45:07 rrsagent, make minutes 14:45:07 I have made the request to generate http://www.w3.org/2016/01/20-lvtf-minutes.html allanj 14:47:09 Chair: Andrew and Jim 14:47:29 jim+ 14:47:33 rrsagent, make minutes 14:47:33 I have made the request to generate http://www.w3.org/2016/01/20-lvtf-minutes.html allanj 14:47:53 present+ 14:47:58 rrsagent, make minutes 14:47:58 I have made the request to generate http://www.w3.org/2016/01/20-lvtf-minutes.html allanj 14:49:01 agenda+ scribe 14:49:03 agenda+ survey User Requirements 14:49:05 https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/ 14:49:15 zakim, clear agenda 14:49:15 agenda cleared 14:49:32 agenda+ survey User Requirementshttps://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/ 14:57:12 zakim, who is on the phone? 14:57:12 Present: jim, AWK, Shawn, JohnRochford, Wayne, Laura, allanj 14:57:16 present: 14:57:20 zakim, who is on the phone? 14:57:20 Present: (no one) 15:00:01 agenda? 15:00:39 agenda 1 = survey User Requirementsh https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results 15:00:48 agenda 1 = survey User Requirements https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results 15:05:05 laura has joined #lvtf 15:07:35 My pleasure, Shawn. 15:23:26 Shawn fixes typos Laura noted in https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results 15:25:45 JohnRochford has joined #lvtf 15:25:59 present+ 15:26:58 Srini has joined #lvtf 15:28:49 AWK has joined #lvtf 15:29:35 present+ Jim, Andrew, Srini 15:30:09 On conference line, got automated message that the access code is invalis. Entered it again, and now on phone, but I don't hear anyone else. 15:30:36 I will hang up and try again. 15:30:56 s/ On conference line, got automated message that the access code is invalis. Entered it again, and now on phone, but I don't hear anyone else./ 15:31:02 s/I will hang up and try again./ 15:31:41 Wayne has joined #LVTF 15:32:10 present+ Laura 15:32:19 Am trying to join by phone, not by WebEx 15:33:21 Trying WebEx now 15:34:13 "Join" button is uninvokable 15:34:48 Jim/Andrew, does survey requires me to login using username / password? never got to see for WCAG survey... or am I on a wrong link? I just clicked in Jim's email 15:35:28 Okay. let me try. thanks, 15:35:49 present+ Wayne 15:36:01 zakim, who is on the phone? 15:36:01 Present: shawn, Jim, Andrew, Srini, Laura, Wayne 15:36:18 I'll be sure for next week. 15:36:48 Scribe: Laura 15:37:22 Open item 1 15:37:40 Topic: 1. Size of All Elements 15:37:42 present+JohnR 15:37:46 present+ Laura 15:39:16 Jim: Good comment on ig list: https://lists.w3.org/Archives/Public/w3c-wai-ig/2016JanMar/0081.html 15:39:26 +1 to you Andrew. Seperating would be useful. 15:40:09 jon_avila_ has joined #lvtf 15:40:20 q+ 15:40:23 Jim: Keeping separate makes sense. different responsibilities. 15:41:11 Shawn: This doc user needs. 15:41:37 ack awk 15:41:53 AWK: We are just focusing on requirement. 15:42:13 ... reminder that for this doc, we just focus on user needs. in separate doc we will look at responsibilities of OS, UA, content, etc. 15:42:41 present+ JonA 15:42:41 Jim: any objections for keeping together? 15:42:47 none 15:43:27 [ Shawn has her text cursor bigger from OS setting ] 15:43:52 +1 for keeping these user requirements in one point 15:43:55 Wayne: leave this group together. 15:44:27 Topic: 2. Seeing All Interface Elements 15:45:51 RESOLUTION: Size of All Elements Keep Together 15:46:52 +1 to being broad for flexible text area 15:47:26 Shawn: I fixed the typos. 15:48:50 AWK: How to determine what users are to see? 15:49:22 Shawn: overlapping content. 15:49:48 AWK: Feels like a different problem. 15:50:50 AWK: may be a tracking issue. 15:51:30 John: Thinks of it at a recognition issue. 15:51:39 https://www.w3.org/WAI/images/easychecks/zoom-overlap.png 15:52:36 Shawn: screenshot is beyond tracking. 15:52:52 AWK: Not a perfect fit. 15:54:12 AWK: Likes that it is included in user settings. 15:54:18 seems to be a definition issue. Seeing yes you can see it. But is it understandable. Perhaps define seeing as ability to perceive and comprehend 15:54:31 content adapat in a non-desctrtive way VS. interface elements are available 15:54:47 q+ 15:55:09 poor adaptabii;lity 15:55:22 ack w 15:55:36 WK: Maybe change the title of the section to Adaptability 15:55:42 s/adaptabii;lity/adaptability 15:56:25 Clarification: JohnR (not necessarily JohnA) thinks of it as a recognition issue 15:56:39 s/WK: Maybe / AWK: Maybe 15:56:39 * Can someone post a link to the content we are discussing? Thanks 15:56:58 https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results#xseeall 15:57:52 s/* Can someone post a link to the content we are discussing? Thanks/ 15:57:58 Shawn: user need is that they can see everything. 15:58:21 http://w3c.github.io/low-vision-a11y-tf/requirements.html#seeing-all-interface-elements 15:58:24 Shawn: happy to think about it more 15:58:36 * thanks 15:58:58 Wayne: Have to be careful of using the word “Zoom” 15:59:12 +1 15:59:20 Wayne: Enlarging text is something else. 15:59:28 +1 16:00:10 action: Shawn think about 3.7.1 Seeing All Interface Elements with Andrew and others input from 20 Jan telecon 16:00:10 Created ACTION-25 - Think about 3.7.1 seeing all interface elements with andrew and others input from 20 jan telecon [on Shawn Henry - due 2016-01-27]. 16:00:21 Wayne: People are very confused about it. 16:00:50 Jim: Maybe we should define terms. 16:01:03 action: jim to create list of other definitions we might need/use 16:01:03 Created ACTION-26 - Create list of other definitions we might need/use [on Jim Allan - due 2016-01-27]. 16:01:32 ACTION: Shawn think about explaining zoom verses increase text (e-mail thread) 16:01:32 Created ACTION-27 - Think about explaining zoom verses increase text (e-mail thread) [on Shawn Henry - due 2016-01-27]. 16:01:56 Topic: 3. Proportional text increase 16:02:10 http://w3c.github.io/low-vision-a11y-tf/requirements.html#proportional-text-increase 16:02:19 https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results#xproprtnl 16:03:29 [ I also have examples of this at http://www.tader.info/element-level.html :-] 16:03:49 Jim: I thought of it as a combination. 16:04:17 …everything should zoom the way it needs too. 16:04:48 Wayne: I think we need to call that out. 16:06:15 q+ 16:06:36 Shawn: Would some users not want to increase proportionately? 16:07:00 q+ 16:07:16 John: A better example would be 4 times the size. 16:07:57 Laura, I suggest you use JohnR and JohnA. 16:08:31 Sorry, just noticed spelling difference 16:08:49 AWK: can achieve with personal perference 16:09:09 Shawn: Don’t think we need this separate point. 16:09:11 ack w 16:10:14 +1 to not needing 3.5.2 Proportional text increase because the user need is adequately covered by 3.5.1 Element-level customization and Zoom would provide proportional zoom. and Text size lets the user text an overall text size. 16:10:20 Wayne: not just headings need adjustments. Spacings zoom. 16:10:46 action: Shawn think about spacing resizing, e.g., ems for spacing 16:10:50 Created ACTION-28 - Think about spacing resizing, e.g., ems for spacing [on Shawn Henry - due 2016-01-27]. 16:11:30 Wayne: okay to combine 3.5.2 and 3.5.1 16:12:07 No other comments 16:13:05 RESOLUTION: 352 is adequately covered. Don’t need separate point. 16:13:13 topic: 4. Margins and Borders 16:13:28 http://w3c.github.io/low-vision-a11y-tf/requirements.html#margins-and-borders 16:13:29 https://www.w3.org/2002/09/wbs/81151/LVTF18Jan2016/results#xmrgnbrdr 16:14:10 +1 keep together 16:14:15 Jim: Keeping together makes sense. 16:14:44 JonA: seems separate. 16:15:25 Shawn reads test. 16:15:33 q+ 16:16:09 ack a 16:16:12 q+ 16:16:15 s/reads test/reads text 16:16:58 AWK: Did you move these around? 16:17:08 Shawn: yes. 16:17:28 AWK: Hard to split them out. 16:17:58 Shawn: good point. 16:19:05 awk: sees margins and borders as element identification, rather than spacing for reading. 16:19:21 JonA: separate one block of text from another. Usability issue. 16:19:40 Shawn: overlap 16:20:03 Shawn: more of a readability issue. 16:21:20 AWK: Should these 2 things be combined? 16:21:25 q+ 16:21:30 …As long as the 2 things exist we should be okay. 16:21:42 ack wayne 16:21:57 Wayne: does fall under element level. 16:22:38 …2 people may want to call things out in different ways. 16:22:40 q+ 16:23:42 ack j 16:23:48 ack allanj 16:23:53 Jim: 3.4 is a result of 3.5 16:23:56 ack shawn 16:25:09 q+ 16:25:13 Shawn: Question in an ideal world should ewe be able to say to 3em around all blocks of text? 16:25:44 JonA: thinks it falls under both. 16:25:57 q+ say that's the issue - readability VS identifying elements 16:25:58 3.4 could have easier user interface, where 3.5.1 could be editing css. ease of use issue. 16:26:04 q+ to say that's the issue - readability VS identifying elements 16:26:20 ack w 16:27:04 Wayne: Problem today, we can’t write the AT. 16:27:48 …Wayne: target is to hare to hit. 16:28:10 [ Wayne : took me 2 weeks to get a gmail style sheet ] 16:28:12 ack shawn 16:28:12 shawn, you wanted to say that's the issue - readability VS identifying elements 16:28:19 s/to hare/to hard 16:28:30 Shawn: 2 different issues. 16:29:29 readability vs identifying elements, could be both 16:30:21 action: Shawn 3.4.5 Margins and Borders - clarify readability issue (John's point in 20 Jan telecon) 16:30:22 Created ACTION-29 - 3.4.5 margins and borders - clarify readability issue (john's point in 20 jan telecon) [on Shawn Henry - due 2016-01-27]. 16:31:29 AWK: adjust the language and leave in the same place. 16:31:57 +1 for leaving it as a separate point in readbility section (and leaving it as subpoint in identifying elements) and making more clear how it relates to readability 16:32:15 Jim: belongs in both places. 16:33:27 Jim: More questions in the survey. 16:33:37 …will bring to the list. 16:34:01 Shawn: maybe leave the survey open. 16:34:31 Jim: Okay. Thant works. 16:34:56 thanks, all -- good discussion!!! 16:35:11 rrsagent, make minutes 16:35:11 I have made the request to generate http://www.w3.org/2016/01/20-lvtf-minutes.html laura 16:35:17 Wayne has left #lvtf 18:01:49 allanj has joined #lvtf