13:58:13 RRSAgent has joined #lvtf 13:58:13 logging to http://www.w3.org/2016/04/06-lvtf-irc 13:58:15 RRSAgent, make logs public 13:58:17 Zakim, this will be 13:58:17 I don't understand 'this will be', trackbot 13:58:18 Meeting: Low Vision Accessibility Task Force Teleconference 13:58:18 Date: 06 April 2016 13:58:29 agenda? 14:03:05 Chair: Jim 14:03:07 Present+ 14:03:12 rrsagent, draft minutes 14:03:12 I have made the request to generate http://www.w3.org/2016/04/06-lvtf-minutes.html shawn 14:06:43 agneda? 14:07:28 agenda? 14:08:27 Agenda+ Legibility and Readability and ??? 14:08:38 Agenda+ Issue 34: Scope question 14:08:50 Agenda+ Issue 38: re-word 3.1.1. 14:08:57 Agenda+ Issue 39: color wheel image locations 14:09:02 Agenda+ Issue 40: 3.3.2 fonts 14:09:08 Agenda+ Issue 41 3.3.3 - avoid italics 14:09:15 Agenda+ Issue 42 3.5.1 - poor example illustration 14:09:24 Agenda+ Issue 45 Note to tool developers not a user need - delete or edit? 14:09:30 Agenda+ Issue 43 figure descriptions 14:09:54 agenda 2 = Legibility and Readability and ??? Issue 37: https://github.com/w3c/low-vision-a11y-tf/issues/37 draft Note & paragraph https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#user-needs 14:25:36 Wayne has joined #lvtf 14:28:15 JohnRochford has joined #LVTF 14:29:29 ScottM has joined #lvtf 14:30:28 present+ Jim, Wayne, JohnRockford 14:30:34 zakim, who is on the phone? 14:30:34 Present: shawn, Jim, Wayne, JohnRockford 14:31:00 shawn has changed the topic to: WebEX https://mit.webex.com/mit/e.php?MTID=m865d07f18564023c0b100df85eb0a694 meeting number 649 045 716 password lvtfnow 14:31:06 Working on getting on the phone 14:31:32 AWK has joined #lvtf 14:31:52 present+AWK 14:31:59 s/Working on getting on the phone// 14:32:35 regrets: Jeanne 14:32:37 present+ScottMcCormack 14:33:15 present+ Alan 14:33:20 +AWK 14:33:24 zakim, who is on the phone? 14:33:24 Present: shawn, Jim, Wayne, JohnRockford, AWK, ScottMcCormack, Alan 14:34:11 present- JohnRockford 14:34:20 present+ JohnRochford 14:34:56 scribe: wayne 14:35:38 zakim, take up item 1 14:35:38 agendum 1. "Availability for Upcoming LVTF Teleconferences " taken up [from shawn-off] 14:36:07 laura has joined #lvtf 14:36:57 JohnRochford_ has joined #lvtf 14:38:50 + Laura 14:39:45 zakim, who is on the phone? 14:39:45 Present: shawn, Jim, Wayne, AWK, ScottMcCormack, Alan, JohnRochford, Laura 14:39:57 q+ 14:40:05 ack me 14:40:53 close item 1 14:41:15 zakim, take up item 2 14:41:15 agendum 2. "Legibility and Readability and ??? Issue 37: https://github.com/w3c/low-vision-a11y-tf/issues/37 draft Note & paragraph 14:41:17 ... https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#user-needs" taken up 14:41:31 topic: Legibility 14:41:55 scribe: allanj 14:42:33 wayne: legibility and navigation. Half of user requirements are legibility. 14:42:44 ... 4 points 14:43:00 ... 1 recognize something - eye test 14:43:21 ... 2 acuity limit - can read - lots of errors 14:43:49 ... 3 font - line spacing - read at max speed with few errors 14:45:21 ... 4 duration (fatigue) - read at speed, with few errors, for long time to get work done. 14:46:26 scribe: wayne 14:49:15 draft https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#user-needs 14:49:24 the Notes and the paragrpah under it 14:50:31 scott: folks have different triggers for fatigue. how do we provide technical guidance 14:50:38 scribe: allanj 14:50:51 long version: https://github.com/w3c/low-vision-a11y-tf/issues/37 14:50:55 shawn: see first paragraph 14:51:50 wayne: legibility based on vision issue and how individuals deal with it 14:52:31 shawn: refine long version as a separate piece. 14:52:54 ... is the note and paragraph sufficient in the requirements? 14:53:32 wayne: note and para are ok 14:54:19 https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#h-note1 14:56:14 scott: is distinguishing between similarly colored items covered 14:56:19 +1 to info in section "3. User Needs" being sufficient 14:56:45 wayne: that is covered under element level styling, so user can configure colors 14:57:39 +1 14:57:45 +1 14:57:48 +1 14:57:58 Scott: looks good to me 14:57:59 +1 14:58:01 +1 14:58:15 +1 (possibly with minor copy editing) 14:58:24 Alan: looks good to me 14:59:37 RESOLUTION: Note and para. after covering legibility approved https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#h-note1 14:59:45 scribe: wayne 14:59:58 zakim, close item 2 14:59:58 agendum 2, Legibility and Readability and ??? Issue 37: https://github.com/w3c/low-vision-a11y-tf/issues/37 draft Note & paragraph 15:00:00 ... https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#user-needs, closed 15:00:00 I see 8 items remaining on the agenda; the next one is 15:00:00 3. Issue 34: Scope question [from allanj] 15:00:06 https://github.com/w3c/low-vision-a11y-tf/issues/34 15:00:09 zakim, take up item 3 15:00:09 agendum 3. "Issue 34: Scope question" taken up [from allanj] 15:00:19 Topic: Scope Issue 34 15:01:29 q+ 15:01:45 allenj: There are many definitions of electronic content. Do we make one. 15:01:56 q+ 15:02:00 ack a 15:02:26 q+ to say web content, elec content, WCAg2ICT 15:02:30 AWK: every thing will be in the context of WCAG. We should take the WCAG definition. 15:02:35 ack me 15:02:35 shawn, you wanted to say web content, elec content, WCAg2ICT 15:03:17 Shawn: There is web content, electronic content (broader than web). We talked about broader than web content. 15:03:23 WCAG: content (Web content) defintion: https://www.w3.org/TR/WCAG20/#contentdef 15:03:24 +1 AWK 15:03:44 -1 to defining 'electronic content' 15:03:52 ... Do we need to define it. There are lots of reasons not too. Should we not define it. 15:04:32 WCAG2ICT "WCAG... can be applied to non-web Information and Communications Technologies (ICT)" 15:04:40 -1 to defining 'electronic content' 15:04:48 JohnR: Does it relate to the web of things. Can we define it in that way. it it is connected to the web. Yes/No 15:04:58 jon_avila has joined #lvtf 15:05:18 allenj: Do we not define electronic content and move on. 15:06:04 RESOLUTION: The group deciided not to define electronic content. 15:06:22 zakim, close item 3 15:06:22 agendum 3, Issue 34: Scope question, closed 15:06:23 I see 7 items remaining on the agenda; the next one is 15:06:23 4. Issue 38: re-word 3.1.1. [from allanj] 15:06:40 https://github.com/w3c/low-vision-a11y-tf/issues/38 15:06:43 present+jon_avila 15:07:05 zakim, who is on the phone? 15:07:05 Present: shawn, Jim, Wayne, AWK, ScottMcCormack, Alan, JohnRochford, Laura, jon_avila 15:08:25 topic: Issue 38 re-word 3.1.1 brightness vs. contrast 15:08:26 Shawn: Is being able to increase brightness over all a special low vision need. 15:08:54 jon_avila has joined #lvtf 15:09:03 Scott: We need to say both issues are possible within the spectrum. 15:09:57 AllenJ: Even when contrast is high, and then they set brightness up. There is a combination of the two. 15:10:40 +1 15:10:55 Scott: For me the brighter the better. 15:10:55 no objection to adding it 15:10:57 +1 15:11:00 +1 15:11:15 Wayne: For me the dimmer the better. 15:11:42 We want to drive home that there is a wide spectrum and flexibility is key' 15:11:48 RESOLUTION: Edit 3.1.1 to include brightness. 15:12:24 allanj has joined #lvtf 15:12:29 zakim, close item 4 15:12:29 agendum 4, Issue 38: re-word 3.1.1., closed 15:12:30 I see 6 items remaining on the agenda; the next one is 15:12:30 5. Issue 39: color wheel image locations [from allanj] 15:12:38 https://github.com/w3c/low-vision-a11y-tf/issues/39 15:13:12 AllanJ: The color wheel may be duplicated. 15:13:34 topic: Issue 39: color wheel images 15:13:35 ... Leave it as is. 15:14:11 RESOLUTION: Leave the color whels images as is. 15:14:35 zakim, close item 5 15:14:35 agendum 5, Issue 39: color wheel image locations, closed 15:14:36 I see 5 items remaining on the agenda; the next one is 15:14:36 6. Issue 40: 3.3.2 fonts [from allanj] 15:15:17 https://github.com/w3c/low-vision-a11y-tf/issues/40 15:16:09 AllenJ: Use of serif fonts and different font families. 15:16:14 +1 Shawn 15:19:50 q+ 15:19:59 s/Allenj/Allanj 15:20:00 q+ to say best practice & comic sans and that's the point 15:20:29 ack me 15:20:29 shawn, you wanted to say best practice & comic sans and that's the point 15:20:32 http://w3c.github.io/low-vision-a11y-tf/requirements.html#font 15:20:54 Discussion: Use clean fonts. This is similar contrast minimum. 15:21:52 +1 Shawn 15:22:08 Shawn: the user can choose for many fonts are variable. A single font might be a best practice. 15:22:10 +1 to Shawn's last commentary 15:22:35 Alan: This seems latin letter specific. 15:23:20 allanJ: I can ping about different alphabets. 15:23:45 +1 for putting in best practice 15:23:46 s/ the user can choose for many fonts are variable. A single font might be a best practice./The User Need is that people can pick a font that works for them. Making the default font a clean one is a best practice or technique 15:23:54 ... do we need to change our user needs? 15:24:30 +1 putting this issue in best practice document 15:24:34 +1 for putting in best practice 15:24:34 Alan: WCAG 2.0 many things aer tchniques etc. 15:24:54 s/aer/are 15:25:28 Entering Microsoft license keys 15:25:31 :) 15:25:45 +1 for putting in best practice 15:26:09 Gotta go, folks. Ciao. 15:27:05 RESOLUTION: Leave section 3.3.2 as it and cover specific fonts in best practice. 15:28:27 [Wayne presentation for CCLV used APH font - and a lot of people didn't like it. switch to verdana and was better.] 15:29:09 zakim, close item 6 15:29:09 agendum 6, Issue 40: 3.3.2 fonts, closed 15:29:10 I see 4 items remaining on the agenda; the next one is 15:29:10 7. Issue 41 3.3.3 - avoid italics [from allanj] 15:29:19 https://github.com/w3c/low-vision-a11y-tf/issues/41 15:29:37 Topic: 3.3.3 Avoid italics Issue 41 15:33:35 JonA: This should be two items: You should avoid italic and you need to be able to change font style semantically. 15:33:45 +1 JonA 15:34:07 ... Style should convey meaning instead of for semantic reasons. 15:35:25 q+ 15:36:40 q+ to say 1. comment resolution, 2. style (3.3.3) & element-level points need attention 15:36:42 ack me 15:36:42 shawn, you wanted to say 1. comment resolution, 2. style (3.3.3) & element-level points need attention 15:36:50 There are semantic meaning that are assigned to meeaning. italic emphasizes it and bold emphasizes it more. Using something for look alone is confusing and difficult. 15:37:19 Shawn: Avoind the use of italics when possible. 15:37:35 ... 3.3.3 needs work. 15:37:37 s/Avoind/Avoid 15:37:57 s/Avoind the use of italics when possible./ / 15:38:12 s/Avoid the use of italics when possible./ / 15:38:50 RESOLUTION: Leave 3.3.3. Cover italics in best practices. 15:38:53 ack me 15:40:22 q+ 15:40:50 wayne: italic for citation or book title. italic usage semantics 15:41:12 open issue for for LVTF comment https://github.com/w3c/low-vision-a11y-tf/labels/question 15:41:17 Shawn: List of open issues see above. 15:42:05 trackbot, end meeting 15:42:05 Zakim, list attendees 15:42:05 As of this point the attendees have been shawn, Jim, Wayne, JohnRockford, AWK, ScottMcCormack, Alan, JohnRochford, Laura, jon_avila 15:42:13 RRSAgent, please draft minutes 15:42:13 I have made the request to generate http://www.w3.org/2016/04/06-lvtf-minutes.html trackbot 15:42:14 RRSAgent, bye 15:42:14 I see no action items