13:44:37 RRSAgent has joined #lvtf 13:44:37 logging to http://www.w3.org/2016/04/13-lvtf-irc 13:44:39 RRSAgent, make logs public 13:44:39 Zakim has joined #lvtf 13:44:41 Zakim, this will be 13:44:41 I don't understand 'this will be', trackbot 13:44:42 Meeting: Low Vision Accessibility Task Force Teleconference 13:44:42 Date: 13 April 2016 13:46:13 rrsagent, make minutes 13:46:13 I have made the request to generate http://www.w3.org/2016/04/13-lvtf-minutes.html allanj 13:46:31 Chair: Jim and Andrew 13:46:40 present+ 13:46:46 zakim, who is here 13:46:46 allanj, you need to end that query with '?' 13:46:51 zakim, who is here? 13:46:51 Present: allanj 13:46:53 On IRC I see RRSAgent, allanj, shawn, trackbot 14:00:04 Agenda+ Issue 35 Update information on acuity 14:00:05 Agenda+ Issue 42 3.5.1 - poor example illustration 14:00:07 Agenda+ Issue 43 figure descriptions 14:00:08 Agenda+ Issue 45 Note to tool developers not a user need - delete or edit? 14:00:10 Agenda+ Issue 46 color vision tweaks to match others 14:00:11 Agenda+ Issue 49 2.1 Scope - cognitive disabilities 14:00:13 Agenda+ Issue 50 Italics, bold, underline 14:23:24 shawn has changed the topic to: See e-mail for call-in info 14:26:58 JohnRochford has joined #lvtf 14:27:50 Wayne has joined #lvtf 14:28:10 present+ 14:28:36 present+ JohnRochford 14:28:47 ScottMcCormack has joined #lvtf 14:29:16 laura has joined #lvtf 14:31:52 jeanne has joined #lvtf 14:32:18 [ when you send requests for comments, you can list it here so we have a record of it ] 14:32:24 [ ... https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Comments ] 14:32:55 present+ Wayne, Scott, Laura 14:33:06 Scribe List: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Scribe_List 14:33:20 zakim, agenda 14:33:20 I don't understand 'agenda', allanj 14:33:25 zakim, agenda? 14:33:25 I see 7 items remaining on the agenda: 14:33:26 present+ Laura 14:33:27 1. Issue 35 Update information on acuity [from allanj] 14:33:27 2. Issue 42 3.5.1 - poor example illustration [from allanj] 14:33:27 3. Issue 43 figure descriptions [from allanj] 14:33:27 4. Issue 45 Note to tool developers not a user need - delete or edit? [from allanj] 14:33:27 5. Issue 46 color vision tweaks to match others [from allanj] 14:33:28 6. Issue 49 2.1 Scope - cognitive disabilities [from allanj] 14:33:28 7. Issue 50 Italics, bold, underline [from allanj] 14:33:57 Scribe: Laura 14:33:58 present+ Jeanne 14:34:04 zakim, who is on the phone? 14:34:04 Present: allanj, shawn, JohnRochford, Wayne, Scott, Laura, Jeanne 14:34:11 Zakim, next item 14:34:11 agendum 1. "Issue 35 Update information on acuity" taken up [from allanj] 14:34:17 topic: Issue 35 Update information on acuity 14:34:24 https://github.com/w3c/low-vision-a11y-tf/issues/35 14:35:41 proposed edit:Some low visual acuity can be corrected with glasses, contact lenses, or surgery – and some cannot. Therefore, some people will not see small text or fine details no matter what. 14:36:11 s/proposed edit:/straw proposal: 14:36:18 I like it 14:36:21 Jim: Some discussion on the topic. Shawn has a proposed edit. 14:36:37 s/proposed edit/straw proposal 14:36:40 I suggest "at all" rather than "no matter what". 14:36:48 …any thoughts? 14:37:24 Some low visual acuity can be corrected with glasses, contact lenses, or surgery – and some cannot. Therefore, some people will not see small text or fine details at all. 14:37:29 +1 at all 14:38:19 RESOLUTION: Change intro to: Some low visual acuity can be corrected with glasses, contact lenses, or surgery – and some cannot. Therefore, some people will not see small text or fine details at all. 14:38:24 +1 14:39:34 Zakim, next item 14:39:34 agendum 2. "Issue 42 3.5.1 - poor example illustration" taken up [from allanj] 14:39:39 topic: Issue 42 3.5.1 - poor example illustration 14:39:47 https://github.com/w3c/low-vision-a11y-tf/issues/42 14:40:58 +1 to that response 14:41:18 + 14:41:21 +1 14:41:30 Jim: Comment on contrast of illustration of Wayne’s style sheet. It is a real style sheet. He needs it to read. 14:42:11 Shawn: maybe change the figcaption? 14:42:18 does this figure meet color contrast requirements? 14:42:58 wayne: it is a little above minimum. 14:43:58 note that a user’s custom style may not meet color contrast 14:44:13 +1 14:44:16 +1 14:44:30 Jim: preface with it with “This a real style sheet ueed by a person with low vision.” 14:45:07 A user’s style sheet meets the user’s need and does not need to meet WCAG requirements 14:45:45 +1 14:45:59 maybe include a couple user examples to show some wide variations 14:47:33 action: Jim to respond to commenter on Issue 42 14:47:33 Created ACTION-46 - Respond to commenter on issue 42 [on Jim Allan - due 2016-04-20]. 14:48:29 RESOLUTION: Will preface with something to the affect that “This a real style sheet used by a person with low vision.” 14:48:43 Zakim, next item 14:48:43 agendum 3. "Issue 43 figure descriptions" taken up [from allanj] 14:48:51 https://github.com/w3c/low-vision-a11y-tf/issues/43 14:48:57 topic: Issue 43 figure descriptions 14:50:22 Jim: Jim stated on writing long descriptions. Laura added some. 14:51:25 present+ AWK(second_part) 14:51:28 would our audiance need such long descriptions? 14:51:33 laura and wayne think they are useful 14:51:50 +1 to Scott 14:52:14 Jim: Useful and they are already done. 14:52:15 -1 to Scott 14:53:52 shawn: what is the use case? would someone need the details? 14:54:12 wayne: when they cant see them. 14:54:43 awk: this section is to explain the issue, not to get into details. 14:55:24 ... all see color differently. these are simulations. 14:55:52 ... perhaps a couple of examples - yellow, pale yellow, pink, light gray. 14:56:29 ... point is ... people see colors differently, and need to able to adjust colors to meet needs. 14:57:05 laura: information is useful...for those who don't have full color perception. 14:57:23 awk: make simpler color wheels. 14:57:49 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Color-Blindness-Table 14:57:58 ... rainbow ROYGBIV 14:58:23 Color names are not always meaningful to people. Describe the key differences such as reds or blues are missing 14:58:33 ... worry about descriptions. what do those words mean? 14:58:52 AWK has joined #lvtf 14:58:54 laura: perhaps we take them out. 14:59:10 js: think they are useful. 14:59:50 jr: these are user needs. should provide information.; 15:01:01 jon: why are we referencing color wheels at all? 15:01:55 q+ 15:02:04 ack me 15:02:12 jim: we have the info. What do we do? 15:02:54 Shawn: If we had something simpler? 15:03:17 Give details about what changes for each simulated wheel 15:03:24 RGB 15:03:32 …maybe do the same with fewer colors. 15:04:35 s/If we had something simpler?/If we had something simpler? Would 3 colors get across the point? 15:05:05 wayne: if we think it is important. why not describe ot to all? 15:05:15 Fig5: “Shows red-green color blindness- Reds and greens are missing replaced by shades of yellow with green and dark red being the same shade of yellow" 15:05:26 something like that 15:06:30 JS: We lose the impact by simplfying it. 15:06:50 q+ 15:07:25 ack me 15:07:48 +1 for not being in the main document - a link to an appendix is good. 15:08:03 shawn: I won't object to it being not in the main doc (appendix or something) 15:09:05 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Color-Blindness-Table 15:09:35 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Color-Blindness-Table 15:09:47 add clock positions 15:10:11 q+ 15:11:22 ack s 15:11:35 Scott: very educational 15:12:05 …information may get lost. 15:12:41 ACTION: Shawn tweak color wheel alts - see Scott's suggestion in minutes 15:12:41 Created ACTION-47 - Tweak color wheel alts - see scott's suggestion in minutes [on Shawn Henry - due 2016-04-20]. 15:12:59 +1 wayne to intro sentence 15:13:09 wayne: maybe add a sentence. 15:13:13 +1 wayne 15:13:24 +1 15:13:31 +1 wayne's intro sentence 15:13:47 +1 to sentence Wayne is trying to recall 15:13:48 ACTION Shawn before color wheel examples, add an intro sentence about this is what people see (see minutes with Wayne's idea) 15:13:48 Created ACTION-48 - Before color wheel examples, add an intro sentence about this is what people see (see minutes with wayne's idea) [on Shawn Henry - due 2016-04-20]. 15:14:24 Colors that are different for people with full color perception are the same for different types of color blindness. 15:15:23 action: Jeanne will add the gray percentage instead of the hex values. And the clock positions. 15:15:23 Created ACTION-49 - Will add the gray percentage instead of the hex values. and the clock positions. [on Jeanne F Spellman - due 2016-04-20]. 15:17:31 RESOLUTION: Will update table, alts and images descriptions. 15:17:49 Zakim, next item 15:17:49 agendum 4. "Issue 45 Note to tool developers not a user need - delete or edit?" taken up [from allanj] 15:17:51 https://github.com/w3c/low-vision-a11y-tf/issues/45 15:17:54 Action: Jim create appendix for detailed image descriptions from issue 43, and action-49 15:17:54 Created ACTION-50 - Create appendix for detailed image descriptions from issue 43, and action-49 [on Jim Allan - due 2016-04-20]. 15:18:05 topic: Issue 45 Note to tool developers not a user need - delete or edit? 15:18:26 s/Will update table, alts and images descriptions/Will update table, alts and images descriptions - and add appendix with detailed image descriptions 15:19:45 +1 for edit 15:20:12 Jim: perhaps an edit “It is easier to pick more readable fonts if each font name in the list is in its font — e.g., Times, Veranda, Courier (these should be in their font to illustrate) — so users can see how each font looks before choosing it.” 15:20:31 I really like being able to preview fonts before I pick something I can’t see 15:20:42 AWK: would vote for throwing it out. 15:21:14 …worries that it is a distraction. 15:21:23 Font names don’t convey information about how the font looks 15:21:53 [ /me waffling back and forth on this one! ] 15:22:14 and one could end up with an unreadable page and limited ability to switch out 15:22:29 Gotta go folks. Until next week... 15:22:30 yes 15:22:33 shawn: is this more of an issue for people with low vision? 15:23:18 JS: Choice is important to someone with albinism. 15:24:44 Scott: has been in situations where font choice it is important. 15:25:33 AWK: where does that actually happen? maybe have another preview. What is the need? 15:25:43 Scott: if change the font to an unreadable one, then maybe can't even read it enough to change it back 15:25:46 +q 15:26:05 q+ 15:26:06 http://w3c.github.io/low-vision-a11y-tf/requirements.html#font 15:26:12 ack scott 15:27:01 q+ to propose "see font before making selection" (rather than specific in font) -- keep as note but not specific user need? 15:27:02 ack me 15:27:02 shawn, you wanted to propose "see font before making selection" (rather than specific in font) -- keep as note but not specific user need? 15:27:09 Scott: we don’t want to restrict people to 1 solution but a preview is a possible solution. 15:28:23 shawn: maybe change what we have to be more generic. Not prescriptive. 15:28:26 +1 to shawn 15:29:53 AWK: can live with it. 15:30:40 …maybe we are describing a different user need. 15:31:58 Wayne: maybe we need to think about the big user need. 15:32:22 Jim: propose we make an issue 15:32:52 +! 15:33:13 s/+!/ 15:33:44 RESOLUTION: Will make the editorial change on issue 45 per minutes. 15:33:47 q+ 15:34:04 ack me 15:35:38 Jim: Let’s work in Github and try to get work done prior to call. 15:36:20 rrsagent, make minutes 15:36:20 I have made the request to generate http://www.w3.org/2016/04/13-lvtf-minutes.html laura 15:36:36 trackbot, end meeting 15:36:36 Zakim, list attendees 15:36:36 As of this point the attendees have been allanj, shawn, JohnRochford, Wayne, Scott, Laura, Jeanne, AWK(second_part), ! 15:36:44 RRSAgent, please draft minutes 15:36:44 I have made the request to generate http://www.w3.org/2016/04/13-lvtf-minutes.html trackbot 15:36:45 RRSAgent, bye 15:36:45 I see 4 open action items saved in http://www.w3.org/2016/04/13-lvtf-actions.rdf : 15:36:45 ACTION: Jim to respond to commenter on Issue 42 [1] 15:36:45 recorded in http://www.w3.org/2016/04/13-lvtf-irc#T14-47-33 15:36:45 ACTION: Shawn tweak color wheel alts - see Scott's suggestion in minutes [2] 15:36:45 recorded in http://www.w3.org/2016/04/13-lvtf-irc#T15-12-41 15:36:45 ACTION: Jeanne will add the gray percentage instead of the hex values. And the clock positions. [3] 15:36:45 recorded in http://www.w3.org/2016/04/13-lvtf-irc#T15-15-23 15:36:45 ACTION: Jim create appendix for detailed image descriptions from issue 43, and action-49 [4] 15:36:45 recorded in http://www.w3.org/2016/04/13-lvtf-irc#T15-17-54