13:57:43 RRSAgent has joined #lvtf 13:57:43 logging to http://www.w3.org/2016/11/03-lvtf-irc 13:57:45 RRSAgent, make logs public 13:57:45 Zakim has joined #lvtf 13:57:47 Zakim, this will be 13:57:47 I don't understand 'this will be', trackbot 13:57:48 Meeting: Low Vision Accessibility Task Force Teleconference 13:57:48 Date: 03 November 2016 13:57:56 chair: jim 13:58:08 rrsagent, set logs public 13:58:17 rrsagent, make minutes 13:58:17 I have made the request to generate http://www.w3.org/2016/11/03-lvtf-minutes.html allanj 13:58:47 rrsagent, set logs public 14:02:16 MichaelC_ has joined #lvtf 14:12:12 Agenda+ Prioritization of what we can do in 4 meetings 14:37:18 laura has joined #lvtf 14:53:28 JohnRochford has joined #lvtf 14:58:13 erich_manser has joined #LVTF 14:58:38 ScottM has joined #lvtf 14:59:24 welcome back jim! 15:01:25 alastairc has joined #lvtf 15:01:40 Happy to scribe today :) 15:02:12 Glenda has joined #lvtf 15:03:32 present+ alastairc 15:03:58 present+ Laura 15:03:58 agenda? 15:03:59 zakim, who is on the phone? 15:04:00 Present: alastairc, Laura 15:04:16 present+ Erich 15:04:18 present+Jim 15:04:28 present+ Shawn, Jim, ErichM, JohnR, Laura, Scott 15:04:31 present+ JohnRochford 15:04:39 zakim, who is on the phone? 15:04:39 Present: alastairc, Laura, Erich, Jim, Shawn, ErichM, JohnR, Scott, JohnRochford 15:04:43 scribe: erich 15:04:54 present- Erich, JohnR 15:05:13 zakim, who is on the phone? 15:05:13 Present: alastairc, Laura, Jim, Shawn, ErichM, Scott, JohnRochford 15:05:24 present+ Glenda 15:06:03 JA: Looking ahead to the next 4 meetings for priorities. WCAG is looking to get first public working draft out in Feb 2017 15:06:55 JA: Since we're all members of the WCAG wg, feel free to participate in that also, to explain what we've done here, etc. 15:07:39 JA: With the Thanksgiving holiday, we've got this meeting plus 3 others. 15:08:15 zakim, open item 1 15:08:15 agendum 1. "Prioritization of what we can do in 4 meetings" taken up [from allanj] 15:08:24 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Tracking_Success_Criteria_Progress 15:09:08 JA: It seems our first 4 or 5 SC are the closest we have to complete 15:09:37 JA: All the others seem to be part of customization, could be addressed by other work, taskforces 15:10:07 JA: Suggesting we focus on the first group, closest to being done, as priority 15:10:25 +1 15:10:26 GS: Agrees with that 15:10:28 +1 15:10:34 LC: Also agrees 15:10:39 +1 15:11:05 WD: Agrees provisionally, but Dec 1st deadline limits us\ 15:12:04 GS: Let's get these solid and in by the deadline, and then when we have a chance to breath move to the others 15:12:45 SH: Let's buckle down and do it rather than talk about it, get as much to them as we can 15:13:54 WD: Element level customization needs attention 15:14:13 SH: We really must focus, next 2 or 3 meetings are critical 15:14:16 WD agrees 15:14:20 Topic: Contrast: Informational Graphics 15:14:36 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Informational_Graphic_Contrast_(Minimum) 15:15:13 JA: Did search on some info graphics that are up there, they are horrid 15:15:51 q+ to ask whether we can define what it contrasts with? 15:15:54 JA: If I have my infographic on a color wheel, there is no way I can make it meet 4.5:1 15:16:18 GS: Pattern, pattern, pattern 15:16:41 JA: I see it, differentiated pattern is part of it, ok 15:16:53 JA: How do we feel about it? 15:17:04 AC: One question from TPAC still needs addressing 15:17:24 AC: Do we need some way of saying what the graphic must contrast with? 15:17:44 LC: I agree, Glenda did a great job in the other contrast one, Interactive Elements, could we borrow from that? 15:17:57 interactive elements contrast - https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_%28Minimum%29 15:18:16 GS: I defined it as the visual presentation of important (non-text) information... think that covers it, what do you guys think? 15:19:01 http://media02.hongkiat.com/infographic-design-kit/yearly-infographic-elements.jpg 15:19:14 AC: Concerned less on icons, but more on larger info graphics. Realize the patterns help, but SC text is saying it should have a contrast ratio 15:19:38 JA: Just added an infographic sample from Google 15:19:52 JA: It's not text, it's a graphic, so you can't get in to it 15:20:30 AC: There's a good example from the 1948, where does the orange and blue need to contrast against the background, as well as each other 15:20:46 LC: That would be the same for a pie chart too 15:21:19 q+ 15:21:24 q- 15:21:31 ack me 15:21:42 GS: Need to take a small step back, no need to handle in color contrast, actually color alone causing the problem 15:22:41 SH: If I have pie chart and data table right next to it, it doesn't matter if I can see the colors. No need to overcomplicate 15:22:48 ack a 15:23:13 Wayne has joined #lvtf 15:23:16 AC: That would just mean we need some caveats, if it's being relied on and there's no redundancy it should have sufficient contrast, or are you saying it's not needed at all? 15:23:30 this is an interesting info graphic I was looking at last night http://sploid.gizmodo.com/the-history-of-all-religions-explained-in-one-fascinati-1643222359 15:23:59 SH: What else do we need to say, do adjacent colors not need to have sufficient contrast because we're already saying we're not relying on color 15:24:22 GS: Why don't we put that as an assumption, but for now think of less is more 15:24:39 JA: This seems to fall in 1.4.5 in WCAG, Images of Text 15:25:04 JA: Wouldn't infographic example I added already fail? 15:25:23 GS: There are some fun exceptions 15:25:50 GS: Not trapping text inside a graphic is very important 15:26:31 AWK has joined #lvtf 15:26:36 JA: What is it in our SC that we need to say something must be done to fix, and have we said that? 15:26:58 rrsagent: make minutes 15:26:58 I have made the request to generate http://www.w3.org/2016/11/03-lvtf-minutes.html allanj 15:27:36 WD: Would like to add a note: There is not a lot of explicit reference in the understanding document as to their application to low vision, things about keyboard use and other things 15:27:54 How about: The visual presentation of graphics that *are relied on to* convey important information have a contrast ratio of at least 4.5:1. (Using the 'important information' to define what needs the contrast.) 15:28:05 WD: May need to look at the techniques of using color only, embedded images, etc to see if there is an interpretation 15:28:36 WD: Need to use some asterisks along here 15:28:57 JA: Would like to focus on getting our language right in the SC 15:29:01 WD: Understood 15:29:23 JA: Does the language we currently have sufficiently convey there are issues needing to be fixed? 15:29:37 GS: Proposes adding a sentence similar to: 15:29:43 Propose adding a similiar sentence like this to “Informational Graphics”: The visual presentation of important (non-text) information in an interactive image has a contrast ratio of at least 4.5:1. 15:30:17 action: jim with LVTF to review wcag understanding document and techniques adding implications for Low Vision 15:30:17 Created ACTION-85 - With lvtf to review wcag understanding document and techniques adding implications for low vision [on Jim Allan - due 2016-11-10]. 15:30:43 LC: We would need to define, since pulling from COGA 15:30:49 Use COGA's important information definition: 15:30:50 important information 15:30:51 1. information the user may need to complete any action or task including an offline task. 15:30:51 2. information the user may need to know related to safety, risks, privacy, health or opportunities 15:31:36 AC: Is it the important information that needs to be contrasted with adjacent items? 15:32:01 GS: I would say background, then that follows the pattern for tests 15:32:08 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Informational_Graphic_Contrast_(Minimum)\ 15:32:15 COGA definition on important information is located here: https://rawgit.com/w3c/coga/master/extension/index.html#dfn-important-information 15:32:20 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Informational_Graphic_Contrast_(Minimum)#EM_Proposed_Description 15:33:19 +1 15:33:47 +q 15:35:14 +q 15:35:56 SM: Does not think asking people to check all possible color combinations is practical. Would almost say it woudl be easier to indicate to use information conveyed solely through color as the SC, and suggest removing all color to test whether same information can still be conveyed 15:35:58 q+ to say focusing on contrast ratio, but techniques list many other ways to fix. but sc says only 4.5:1 15:36:49 GS: This is an important gap which needs to be filled in 2.1 15:37:06 GS: There's something that's important to convey that is not text, but as important as text 15:37:26 q+ 15:37:41 ack s 15:37:44 GS: We're not talking about differences between that pie slice and every other pie slice, but can I see the image / important information 15:37:46 ack g 15:38:48 JA: There are different ways of seeing it, we have SC talking about 4.5:1, but all of our techniques (GARBLED) 15:38:55 Anyone else hearing distorted audio? 15:39:00 q+ to say that what I hear Glenda talking about is not relying on color alone 15:39:25 ack j 15:39:28 q+ 15:39:33 ack allanj 15:39:33 allanj, you wanted to say focusing on contrast ratio, but techniques list many other ways to fix. but sc says only 4.5:1 15:39:39 AC: Sounds like the hole we're trying to plug is discerning 'the thing' from it's surroundings 15:39:49 ack alastairc 15:39:54 AC: Status icons and warning images are more obvious use cases where we could simplify 15:40:13 AC: Don't think we need to get in to slices of a pie chart, as that is covered by the color alone aspect 15:40:32 ack awk 15:40:32 AWK, you wanted to say that what I hear Glenda talking about is not relying on color alone 15:40:41 I agree with what alastair just said. This is about discerning/seeing an item compared to the immediate surroundings. 15:41:00 AWK: We want to make sure things like status indicator warnings, if text, would be 4.5:1 15:41:45 ack wayne 15:41:52 SC: Covers status and focus in SC I am working on 15:42:33 GS: Covers status and focus in SC I am working on 15:42:40 So add to the SC text something like: "The visual presentation of icons or graphics that convey important information have a contrast ratio of at least 4.5:1 against the background". 15:43:05 +1 AC's suggestion 15:43:13 WD: Need to see the line indicating the changes, that's what needs to be 4.5:1 15:43:36 But it doesn't cover the use case of colored elements within a graphic 15:43:37 GS: Proposes that we add 'with it's immediate surroundings' to the end of what's currently written 15:44:52 AWK: If I make a line graph with two lines that follow a grid, 1 dashed line and 1 solid line, that might satisfy what Wayne is saying 15:45:22 Here is a timely example: http://projects.fivethirtyeight.com/2016-election-forecast/ 15:45:25 provided the lines are contrasting enough with the background 15:45:34 scroll to bottom to see line graph 15:45:45 AWK: We're getting in to real specific language that risks not having broad application 15:46:38 JA: Glenda example just posted fails SC as Alastair has posted 15:47:01 The yellow to white is 1.8 to 1 15:47:34 JA: The black text passes, for state names, but the white outlines, not so much 15:49:04 AWK: In state map situation, are we trying to differentiate between these different colors as well? 15:49:17 AWK: You can have one color that's touching many others 15:49:31 GS: It's okay, in those outlines, it's immediate surroundings 15:50:04 GS: I was actually looking at the line map at the very bottom, and just looking at the yellow, blue, red, and asking if they can all be 3:1 since they're all big things 15:51:00 AWK: On that same chart, do the grid lines need to be contrasted also? 15:51:04 GS: Is it important? 15:51:14 AWK: Argument could be made that it is 15:51:31 "The visual presentation of icons or graphics that convey important information have a contrast ratio of at least 4.5:1 against the background". 15:51:36 JA: So going back to AC's text, have we conveyed what we're trying to say 15:52:05 JA: Does the language address all the things we've talked about regarding issues we have with the particular image 15:52:08 AWK: no 15:52:39 Propose changing language to 'The visual presentation of important information in icons or graphics has a contrast ratio of at least 4.5:1 against the immediate surrounding background.” 15:53:08 AC: We would almost have to define which elements are important to understanding 15:53:50 AC: Need to come up with some frame around discernibility to understanding 15:54:47 JA: What sort of language do we need to work in to Glenda's proposed language to address discernibility to understanding? 15:54:49 Use COGA's important information definition: 15:54:49 important information 15:54:50 1. information the user may need to complete any action or task including an offline task. 15:55:15 +1 to using COGA definition of important information 15:56:10 JA: And we need to differentiate this from just the basic color contrast SC 15:57:05 JA: Trying to see how we separate color alone to other information 15:57:19 WD: Why does it fail color alone? 15:57:28 JA: It's the yellow line, I can't see it 15:57:42 GS: That's discernment 15:58:03 AC: It's the definition of graphics that's the problem here 15:58:21 AC: when we get in to more complex graphics, they need to be discernible against each other 15:58:48 AC: If we consider blue line, red line, yellow line as graphics, one surely fails 15:58:56 Suggest we handle it with examples (like this line chart and state chart for the election) 15:59:06 AC: if it's important to understanding, it should have sufficient contrast against it's background 15:59:29 GS: I propose that SC language suggested is within reason, and be supplemented with additional examples 16:00:04 AC isn't this covered under WCAG 1.4.3 Contrast (minimum) 16:00:16 Gotta go, folks. 16:00:45 WD: Informational text has a foreground and a background 16:01:24 WD: IG is generally trying to depict something, so in the foreground you can tell what it's depicting against clearly a background 16:01:30 what would we say about: https://finviz.com/map.ashx 16:01:33 each informational element in an information graphic must have a color contrast of 4.5 to 1 with it’s immediate surrounding. 16:01:59 AC: In complex graphics, need to say each complex graphic is made up of parts of a graphic, and if important to understanding, needs to have it's contrast 16:03:07 GS: Inside an icon, may have black icon with white smiley face, and that face is immediately surrounding the black, so it works and is simple 16:03:20 WD: What if your background color is dark charcoal 16:03:38 JA: You could see the white smiley face, but would you know that anything is surrounding it 16:03:48 JA: Are we any closer on this one? 16:04:14 WD: If we combine what AC did with GS clarification 16:04:17 proposal: each informational element in an information graphic must have a color contrast of 4.5 to 1 with it’s immediate surrounding. 16:04:46 AC: This could use more description, I will tackle for next week 16:04:52 s/it's/its 16:04:59 then we will need to add 3 to 1…can we look at my stuff 16:05:14 JA: We keep saying 4.5:1, but 3:1 for larger things 16:05:42 +q 16:06:46 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_%28Minimum%29 16:08:38 +1 for sticking with 4.5:1 and 3:1 (and 7:1) from WCAG 2.0 16:09:21 GS: Using 4.5:1 as default, and less comfortable but left it also for disabled elements 16:09:34 1 for sticking with 4.5:1 and 3:1 (and 7:1) from WCAG 2.0 16:10:47 GS: What is the normal pixel size at 14 pt, I did not measure for that 16:11:38 JA: Alastair will work more on the description. Seems we have loose agreement on proposed language, though we did not have a vote 16:11:52 JA: Thinks description will tease out the size aspects 16:12:35 AWK: I have concerns, very complicated and talking about many complicated things. Worried what we come up with may fail dramatically 16:12:59 AWK: We may wind up relegating to AAA because it's not specific enough about what we need to do 16:14:26 GS: Thinking a lot about it, and hoping your concerns is a normal concern at the beginning, but that you would start to become more comfortable with it 16:14:54 GS: Comes back to questioning, why did you put that in the graphic, did you want somebody to see it or not? 16:15:27 AWK, would you be willing to go with 3 to 1? and you just put borders around it… 16:15:36 AWK: Concerned about instances where there are many adjacent colors, and if one of those colors does not comply, the whole thing fails the SC 16:16:56 GS: I am not a designer, but I wonder if there are designers in the group 16:18:04 AC: I do work a lot with designers, and feel it's possible to do this, if we narrow and use patterns, labels 16:18:30 q 16:18:35 q+ 16:18:40 GS: It's being able to see the line, or to see the label. It's not getting in to interpreting the legend, but just merely it could enter my brain 16:18:44 AWK: agreed 16:19:08 GS: I would be willing to start with 3:1 if concern is high, or we could start with 4.5:1 and back down to 3:1 if needed 16:19:21 ack erich 16:19:46 AC: If anyone has come across examples (good or bad) please send to me 16:20:12 WD: THink the problem with IG from a visual point of view, they are important but cannot be changed programmatically 16:20:21 WD: there's no way with style that you can fix that 16:20:59 WD: I like AC's idea of narrowing it, I think we should narrow this to what we can see right now, with the risk or certainty we'll leave something out initially 16:21:24 GS: sending data visualizations example with Alastair 16:21:46 Data Visualizations to consider: http://www.informationisbeautiful.net David McCandless 16:22:37 WD: we could look at Edward Tufte (sp?) examples also 16:22:41 Topic: interactive contrast https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_%28Minimum%29 16:23:29 GS: Do we want to start with 4.5:1 or simplify and call everything 3:1 to start (would make it much easier, but not sure it's enough) 16:24:59 AC: 3:1 might be ok with a minimum pixel width of 3px (maybe 2?), but with 1px width then 4.5:1 would be needed. 16:26:41 [ I wonder if information not conveyed by color alone covers the deisabled issue] 16:27:44 [ also with high contrast, it might be too hard to have sufficient change in contrast to be able to tell the difference between enabled and disabled ] 16:28:00 Erich: +1 to 3:1 for disabled elements 16:28:07 wd: +1 also 16:28:10 q+ to ask what the contrast ratio is for default browser controls when disabled 16:29:33 ack w 16:30:12 AWK: Do we know default contrast ratio of the browser for disabled elements? 16:30:16 GS: no 16:30:30 AWK: Are we comfortable saying you fail if you use the default? 16:30:44 GS: This would be a change from 2.0, since 2.0 lets you get away with the default 16:31:09 q+ 16:31:24 GS: If we're trying to move a11y forward and see the focus, then it's not good enough, can we bring this forward and have the possibility of discussing with the browser vendors to make better 16:31:42 ack awk 16:31:42 AWK, you wanted to ask what the contrast ratio is for default browser controls when disabled 16:32:11 +1 to goodwitch 16:32:28 jim will create a chart of contrast for form elements and focus rings 16:35:37 default outlines on inputs in Chrome: 2.14:1 for regular, 1.41:1 for disabled! (1px wide) 16:36:13 +1 for developing additional material, e.g., adding to existing Understanding docs -- and maybe more supporting material for the new SCs 16:36:43 Quick test: https://alastairc.ac/tests/disabled-elements-test.html 16:37:01 thanks!!! 16:38:32 Glenda - can you update the wiki with your contrast SC text? Not sure I saw the right one go past... 16:39:38 rrsagent: make minutes 16:39:38 I have made the request to generate http://www.w3.org/2016/11/03-lvtf-minutes.html erich_manser