16:00:23 RRSAgent has joined #wai-wcag 16:00:23 logging to http://www.w3.org/2017/01/10-wai-wcag-irc 16:00:25 RRSAgent, make logs public 16:00:25 Zakim has joined #wai-wcag 16:00:27 Zakim, this will be WAI_WCAG 16:00:27 ok, trackbot 16:00:28 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 16:00:28 Date: 10 January 2017 16:00:45 Zakim, who is on the phone? 16:00:45 Present: (no one) 16:00:47 zakim, who is here? 16:00:47 Present: (no one) 16:00:48 +AWK 16:00:49 On IRC I see RRSAgent, AWK, Greg, steverep, JF, KimD, Srini, jeanne, kirkwood, MichaelC, Rossen, yatil-away, trackbot 16:00:51 laura has joined #wai-wcag 16:01:00 present+ JF 16:01:09 present+steverep 16:01:14 present+ Greg_Lowney 16:01:24 Jim_S has joined #wai-wcag 16:01:26 agenda+ Survey: https://www.w3.org/2002/09/wbs/35422/WCAG21_SCs_1/results 16:01:39 tpresent+ Srini 16:01:39 agenda+ SC Manager questions 16:01:45 agenda+ Charter update 16:01:57 agenda+ Voice summary demos and cognitive roadmap (Willie Scott from IBM) 16:02:24 Lauriat_ has joined #wai-wcag 16:02:24 Joshue108 has joined #wai-wcag 16:02:40 alastairc has joined #wai-wcag 16:02:48 Present+ Lauriat 16:02:51 marcjohlic has joined #wai-wcag 16:02:52 +KimD 16:03:02 Zakim, who is on the phone? 16:03:02 Present: AWK, JF, steverep, Greg_Lowney, Lauriat, KimD 16:03:02 present+ Laura 16:03:03 marcjohlic has joined #wai-wcag 16:03:03 Kathy has joined #wai-wcag 16:03:06 present+ Kathy 16:03:18 Lisa_Seeman has joined #wai-wcag 16:03:24 David-MacDonald has joined #wai-wcag 16:03:25 present+ 16:03:28 present+ Jim 16:03:28 present+ kirkwood 16:03:37 present+ Lisa 16:03:37 present+ Srini 16:03:49 present+ alastairc 16:03:50 pressent+ jeanne 16:03:52 gowerm has joined #wai-wcag 16:03:52 present+ marcjohlic 16:03:56 Present+ David-MacDonald 16:04:35 regrets+ Detlev, Katie, Wilco 16:04:49 adam_solomon has joined #wai-wcag 16:04:59 present+ adam_solomon 16:05:04 present+ MikeGower 16:05:04 alastairc has joined #wai-wcag 16:05:26 Makoto has joined #wai-wcag 16:06:20 Kathy will scribe on Jan 24 16:06:41 scribe: alastairc 16:06:49 Laura will scribe next week 16:07:13 present+ Makoto 16:07:16 Zakim, take up item 1 16:07:16 agendum 1. "Survey: https://www.w3.org/2002/09/wbs/35422/WCAG21_SCs_1/results" taken up [from AWK] 16:07:23 Rachael has joined #wai-wcag 16:07:58 Pietro has joined #wai-wcag 16:08:04 present+ Rachael 16:08:17 try this: https://www.w3.org/2002/09/wbs/35422/WCAG21_SCs_1/results 16:08:42 present+ Joshue108 16:08:52 zakim, who is on the phone? 16:08:52 Present: AWK, JF, steverep, Greg_Lowney, Lauriat, KimD, Laura, Kathy, MichaelC, Jim, kirkwood, Lisa, Srini, alastairc, marcjohlic, David-MacDonald, adam_solomon, MikeGower, Makoto, 16:08:55 ... Rachael, Joshue108 16:09:15 zakim, agenda? 16:09:15 I see 4 items remaining on the agenda: 16:09:16 1. Survey: https://www.w3.org/2002/09/wbs/35422/WCAG21_SCs_1/results [from AWK] 16:09:16 2. SC Manager questions [from AWK] 16:09:16 3. Charter update [from AWK] 16:09:16 4. Voice summary demos and cognitive roadmap (Willie Scott from IBM) [from AWK] 16:09:28 https://github.com/w3c/wcag21/issues/57 16:09:34 David-MacDonald: I've defined a second version of this 16:10:08 present+ Pietro 16:10:09 Heres the one to merge https://github.com/w3c/wcag21/issues/58 16:10:13 ... the second to last comment https://github.com/w3c/wcag21/issues/57#issuecomment-271204200 16:10:20 jemma_ has joined #wai-wcag 16:10:48 q+ 16:11:00 ... it incorporates terminology used elsewhere in WCAG, so it is a little simpler. 16:11:17 MoeKraft has joined #wai-wcag 16:11:20 JF: Where did the 25 characters come from? 16:11:32 q+ 16:11:34 Lisa_Seeman_ has joined #wai-wcag 16:11:35 present+ JaEunJemmaKu 16:11:36 q+ 16:11:42 Q+ 16:11:56 q+ 16:12:07 q+ to say that there is a meaningful difference between "blocks of text" and "all text" 16:12:26 Wayne: We wanted a line length that wouldn't have excessive hyphenation required or excessive line breaking. 25 chars was relatively practical for western languages and how word wrapping works. It is slightly shorter than a standard newspaper column. 16:12:56 ... you can get efficient word wrapping down to 15 characters, but we didn't push it that far. 16:13:17 jon_avila has joined #wai-wcag 16:13:18 q+ 16:13:28 present+jon_avila 16:13:36 David: I made it 'blocks of text' rather than 'all text'. 16:13:51 ack j 16:13:54 Wayne: We'd removed blocks of text because there are lots of uses of text not in blocks. 16:14:30 Josh: Agree with Mark's comment about "mechanism", appears to require developers to create something to satisfy this. 16:14:32 ack me 16:14:35 ack jo 16:14:38 q+ to comment on viewport / exception 1 16:15:29 David: I've done a little testing re-sizing columns, there are some examples (e.g. CNN) and their columns are around 60 characters long, but I defer to the group on that. 16:16:25 Wayne has joined #wai-wcag 16:16:26 David: Mechanism is a stock phrase in WCAG 2.0, it is an update on "until user agents", it could be a content or a UA thing. Some things we thought UAs would do, so the mechanism could be the UA. 16:16:35 q+ 16:16:49 Mark: Are we at the point removing that language? 16:17:10 ack AWK 16:17:10 AWK, you wanted to say that there is a meaningful difference between "blocks of text" and "all text" 16:17:19 David: That's a WCAG 2.0 concept, and gives us the ability to pass things that are already dealt with in user-agents. 16:18:25 AWK: There isn't a meaningful difference between blocks and multiple-sentences. Text isn't always available in blocks, and should still apply (from the LVTF). We need to decide whether it needs to be blocks or not. 16:18:47 ack ada 16:19:06 Updated the proposal to "All Text" refresh... 16:19:28 Adam: Regarding screen resolution & magnification, does this relate to a particular size? 16:20:06 ... also if you start with very small text and it doesn't get to the required size, is that an issue? 16:20:17 q+ to disambiguate line length restriction from zooming 16:21:01 JF: I have a concern about articulating a number of characters, e.g. for German or Welsh, or RLT/ top-to-bottom languages? 16:21:15 q+ to +1 I18N concerns 16:21:26 ... don't see a relationship here to font size. If I have a small font size how does that affect it? 16:21:33 ack mike 16:21:35 +1 to that also 16:21:38 ack gower 16:21:38 q+ 16:21:41 +1 to JF 16:21:42 https://github.com/w3c/wcag21/issues/78 16:22:05 maybe it doesn't have to be so proscriptive 16:22:20 Mike: Regarding "Mechanism", it implies a burden on the author which is confusing to address. 16:22:23 jamesn has joined #wai-wcag 16:22:39 +1 to Mike on the mechanism thing - we obviously need to revisit this. 16:22:43 +1 to wording (Mike's comment) 16:22:48 rrsagent, make minutes 16:22:48 I have made the request to generate http://www.w3.org/2017/01/10-wai-wcag-minutes.html jamesn 16:22:50 ... for line length, I'd like clarity on how resize, reflow and line length interacts. 16:22:52 q+ 16:23:05 There appear to be 9 SCs that use a Mechanism is Available 16:23:35 ack l 16:23:44 1.4.8 Visual Presentation: For the visual presentation of blocks of text and objects, a mechanism is available to achieve the following (Level AA): 16:23:46 Foreground and background colors can be selected by the user. 16:23:47 Width is no more than 80 characters or glyphs for Latin and Semitic based languages; or 40 for Chinese, Japanese, and Korean; or can be selected by the user. 16:23:49 Text is not fully justified (aligned to both the left and the right margins), or justification can be set by the user. 16:23:50 Line spacing (leading) is at least space-and-a-half within paragraphs; and paragraph spacing is at least 1.5 times larger than the line spacing. 16:23:52 Text can be resized, without assistive technology, up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. 16:23:53 Increased line and border spacing can be added around blocks of text and objects, such that they can be increased up to 200% without loss of content or functionality. 16:24:16 Actually looking at the single column issue and the request to merge them - that may be an easier way to frame the use case https://github.com/w3c/wcag21/issues/58 16:24:46 Lisa: We have an SC (51?), we wanted to change visual presentation and upgrade it (faded out). we should merge it into that bullet point, rather than have two proposals about width of text. 16:25:04 Lisa: Nothing against the SC at all, but makes sense to merge them. 16:25:16 @josh - yep I agree. Might be easier to start w/ talk of merging 16:25:58 q+ to -1 over-combining with personalization (though personalization as technique is ok) 16:25:59 ... also, we are making (in ARIA WG + COGA), personalisation settings, and saying that it should work with the plugin would be much easier. 16:26:35 https://github.com/w3c/wcag21/issues/51 16:26:56 Lisa: We've made a proposal (51) we have changed "VIsual Presentation" to be AA, and I think we should merge it. 16:27:06 ack me 16:27:06 MichaelC, you wanted to comment on viewport / exception 1 and to disambiguate line length restriction from zooming and to +1 I18N concerns and to -1 over-combining with 16:27:06 ack m 16:27:09 ... personalization (though personalization as technique is ok) 16:27:20 +1 to Lisa and merging where possible 16:28:24 MichaelC: Underscore internationalisation aspect, when numerating characters. Also, on zooming & line length we need to be very clear. Line length restriction is related to people's ability to track and stay on a line. But they inter-relate, and meeting one might hamper the other. 16:29:22 ... Personalisation is a technique, it sounds good, but I don't think we should combine those as we'd end up with one SC of "make your site personalisable". 16:29:24 https://www.w3.org/TR/CSS21/visuren.html#viewport 16:29:50 Alastair, can you jump in on ViewPort 16:29:51 ... not sure if the exception can be reconciled with the definition of the viewport. 16:29:56 q? 16:30:01 ack wa 16:30:53 Wayne: Font size & line length are related, but there are people with low-vision have limited or no peripheral vision. It is very much the case where you would want short length, not a fact of large print. 16:31:02 q+ to speak to "mechanism" 16:32:19 Mike_Elledge has joined #wai-wcag 16:32:27 ... there was also no intention that authors would create the mechanisms. It just means that a mechanism exists, like programatic determinism. UAs have user-style sheets, and what I really want is something more like: If no user-agent for a given technology has a mechanism, then the author is not responsible to create it. However, that isn't possible under WCAG 2.0 framework, where some UAs can't do it. 16:32:28 q+ to say we don´t want SC that only apply if UAs do it 16:32:31 Present+ Mike Elledge 16:32:36 Lisa_Seeman_ has joined #wai-wcag 16:32:44 got it working now 16:33:17 ... also, I don't think the line length should be combined with the reflow criteria. The ability to control line length within table cells isn't possible unless it is separate. 16:33:49 q+ to say ¨mechanism¨ is a bugaboo from WCAG 2.0 that we might want to clear up in Silver 16:33:50 https://github.com/w3c/wcag21/issues/51 16:33:56 q+ to ask about the scope for merging techniques 16:34:06 but can we merge them so it does address them? 16:34:14 ack ala 16:34:24 Alastair: two points 16:34:42 q+ 16:34:44 ... marc asking about the relationship between reflow and resizing 16:35:08 ... currently resizing doesn't talk about horizontal scrolling so every site passes 16:35:36 q+ 16:35:43 ... the assumption on the resize content is that it will work with branding etc in place 16:36:13 ... first request for resizing was 1000% which seemed to be a problem for many sites to manage 16:36:28 ... 400% seems more feasible 16:36:40 ... while maintaining the order and presentation 16:37:00 q+ to say there may need to be a trade-off between resize and reflow, and people needing outside that boundaries use special technologies 16:37:05 ack AWK 16:37:05 AWK, you wanted to speak to "mechanism" 16:37:52 +1 16:38:14 AWK: Mechanism - is from WCAG2.0, was used and may yet have good utility, and it is key to technology independance of WCAG. There are things you can do as an author in one technology, but taken care of by technology on another platform. 16:38:23 ack mi 16:38:23 MichaelC, you wanted to say we don´t want SC that only apply if UAs do it and to say ¨mechanism¨ is a bugaboo from WCAG 2.0 that we might want to clear up in Silver and to say 16:38:23 ack me 16:38:26 ... there may need to be a trade-off between resize and reflow, and people needing outside that boundaries use special technologies 16:38:34 q+ 16:39:25 AWK: Mechanism - is from WCAG2.0, was used and may yet have good utility, and it is key to technology independence of WCAG. There are things you can do as an author in one technology, but taken care of by technology on another platform. 16:40:02 q+ to talk about things that would be prevented by no allowing mechanism terms. 16:40:55 q+ 16:40:57 q? 16:40:57 MichaelC: When people need things outside of those limits, what are the reasonable limits for the guidelines? 16:41:02 ack josh 16:41:02 Joshue, you wanted to ask about the scope for merging techniques 16:41:03 ack me 16:41:07 q+ 16:41:34 Lisa_Seeman_ has joined #wai-wcag 16:42:02 Josh: Personalisation, and what we can/can't merge. The initial issue (57) could probably dove-tail with 58 quite well? we should look at merging them, not to create a whitewash of generalisation, but when they have a genuine nexus of things. 16:42:27 ack gower 16:43:56 I have to drop off in 2 minutes to give a lunch webinar 16:44:23 +1 to Mike 16:44:28 Mike: the table cells aside, I think they are interdependent: with reflow, with the exception of things like tables everything can reflow into a single column. Once there, I don't need to control the line length anymore, because I can resize my browser width. Once it's in one column I'm not sure what relevance this SC has. 16:44:29 q+ 16:44:39 @gower it would be good to see the suggestion in text to help think about - a comment for #57/#58? 16:44:49 Mike: Oh, the table cells exception! I think we need a specific technique or SC for table widths. 16:44:55 +1 I have to agree with Mike's logic here 16:44:57 ack mako 16:46:06 Thanks Makoto! 16:46:10 Makoto: As JF pointed out, we need to think about internationalisation. The Japanese (and other) characters have 1.4.8 which defines 80/40 chars. If the number will be 25, it might be 12/13 for CJK chars. But I need to check with the LV community in Japan. 16:46:15 @makoto - checking with the LV community in Japan would be helpful 16:46:50 Thank you, Makoto. 16:47:03 ack wayne 16:50:18 Q+ 16:50:30 Wayne: 1st, the line length question - even though you can reflow, there are UAs that don't allow you to shrink the window. Reflow and word-wrap are different things. Reflow is a linearisation of elements, important because [sorry, missed a bit], it is safer to have a narrow column to search down to find things. Word-wrapping is what we mean in that sense. For the practicality, a 13" laptop starting with 12pt font will easily fit 25 chars on a screen. 16:50:56 ... 400% is a practical size, so that's why we had different ones. 16:51:02 ack ala 16:51:02 alastairc, you wanted to talk about things that would be prevented by no allowing mechanism terms. 16:51:14 zakim, close queue 16:51:14 ok, AWK, the speaker queue is closed 16:51:30 Alastair: talking about mechanism 16:52:04 q+ to say user agents don´t fit the viewport, the viewport is set by the user agent 16:52:06 ... on desktops/laptops you can zoom and the browser will reflow with media queries / responsive design 16:52:27 ... on mobile (iOS/Android) this isn't the case 16:52:44 ... when you use pinch zoom it expands beyond the layout 16:52:46 q- 16:53:07 ... so there is a divide between what "mobile" OS and desktop OS systems currently support 16:53:31 ... how to handle? an exception for mobile? (this is what that language was for) 16:53:45 ack d 16:53:56 ack jon 16:55:53 ack jf 16:55:55 Jon: I'd agree with Alastair & Wayne, you can't just get a bigger monitor. Some people with LV can't use widescreen monitors. Other situations you might be on a mobile device and have a fixed size screen. Magnification is not optimal for a lot of users, you can't see all the information. We need *some* requirement for reflowing content. 16:56:39 JF: I have a few concerns, the other being actual font-size, and starting points. 16:57:07 zakim, agenda? 16:57:07 I see 4 items remaining on the agenda: 16:57:08 1. Survey: https://www.w3.org/2002/09/wbs/35422/WCAG21_SCs_1/results [from AWK] 16:57:08 2. SC Manager questions [from AWK] 16:57:08 3. Charter update [from AWK] 16:57:08 4. Voice summary demos and cognitive roadmap (Willie Scott from IBM) [from AWK] 16:57:11 JF: I think we need to declare a font size, like the colour contrast SC does. 16:57:38 ... thinking of a webpage with H2/3 is set at 22pt, then I resize it I get horizontal scrolling quickly. 16:58:03 q+ 16:58:10 AWK: David will have to work through these comments. 16:58:17 Zakim take up item 2 16:58:27 q- 16:58:36 Zakim, take up item 2 16:58:36 agendum 2. "SC Manager questions" taken up [from AWK] 16:59:37 AWK: I asked if anyone had any to survey, haven't had a flood of those. Do people need to know more? Is it a time issue? 16:59:58 q+ 17:00:34 AWK: Telling me would be a good start. In the process on the SC manager page, it goes into a pull request. 17:01:57 AWK: We haven't resolved the editing current SCs aspect, which might hold some people back. 17:02:25 Rachael: How do we handle overlapping with other SCs which don't have managers? 17:02:39 AWK: I'll check with Josh and MichaelC about that and share with the list. 17:02:56 AWK: any other thoughts/questions please send them to Josh or me. 17:02:57 Joshue108 has joined #wai-wcag 17:03:00 agenda? 17:03:01 q? 17:03:08 Zakim, take up item 4 17:03:08 agendum 4. "Voice summary demos and cognitive roadmap (Willie Scott from IBM)" taken up [from AWK] 17:04:24 Will Scott at IBM, I'm the software architect for this technology. working on a tech for people with cognitive issues. 17:05:00 Will: Please ask questions as we go through. 17:05:25 Will: Called "Content Clarifier", which is a natural language generation tool. 17:05:58 ... take content and manipulate it, to help people with intellectual disabilities, and extend to other audiences. 17:06:14 ... first thing is simplification, to improve comprehension. 17:06:39 ... second is content enhancement, which is easier to understand from the demo. We take semantic text and add it to the source. 17:06:56 ... we can pull in symbols and more. 17:07:16 ... Also doing summarisation, pulling out the most important information from content. 17:07:33 ... finally, doing a second pass on summarised content to simplify it, like in step 1. 17:08:34 ... demographics that might benefit are people with Intellectual disabilities, older people, and people with second language issues. 17:09:24 Will: Overlap with WCAG additions, such as replacing complex words with short, simple words. Replace non-literal phrases, idioms etc with literal wording. 17:09:58 ... can add iconography, convey meaning visually, and combines with simplified text. 17:10:11 ... uses an open library of icons, but that's configurable. 17:10:46 Will: Some of the key components are IBM Watson, a scalable API, semantic web and "IBM Bluemix". 17:11:26 ... the technology is delivered as an API, so a programmer can pull things into their own app/site. The Bluemix is the cloud platform, which has benefit of scalability. 17:13:08 ... Watson, IBM's super-computer focused on cognitive computing. Exposing that to developers via APIs, so combining use of Watson, and doing creative things with manipulating content. A lot of the manipulations of the content are based on semantic web. Linked data sources on the web, which are queried to retrieve information. 17:13:17 Will: Any questions before the demo? 17:14:30 Will: Demo, showing a content clarifier, (interface looks a bit like a google-translate, but with options of conversational / news/ technical / corp content. 17:14:59 ... this is just a basic interface, the API is how we'd expect people to use it. 17:16:09 q+ 17:16:41 JF: Is anything being used that relies on flash kincade / readability scores? 17:17:16 Will: sort of, sometimes though it will make the content longer. measures for simplicity can complain in that aspect. 17:17:28 ... for example, if we insert a simple english definition, it will make it longer. 17:18:03 s/flash kincade/Flesch–Kincaid 17:20:09 Will: replaces things based on many factors. Also, can go out and get definitions for things like "mobile phone", turning the page into a self-glossary. 17:22:05 ... Using a News content source, with definitions selected. Inserts explanations inline, after the particular words it selects. 17:22:31 ... The content is longer, but it is explaining complex terms in detail. 17:23:49 ... it pays attention to the context when adding to or enhancing the content. 17:25:13 ... example shown which shows AAC symbols, inline with text. Helpful for the developer because it comes back with the attribution information for the icons. You can change many things, like size, alignment, what the developer wants to do. 17:25:50 ... if a human wants to do this, you have to Id the symbols, review them, select the symbol for the wording, and manually insert it. This is automatic. Same goes for the other enhancements shown. 17:28:57 ... example of natural language generation, an abstractive approach. Not just extracting sections. 17:29:22 Very interesting Will -appreciated. 17:29:25 ... Ultra mode - take the summarised content, do a second pass with simplification. 17:29:37 q 17:29:38 q? 17:29:55 AWK: How does a dev make use of this? 17:30:48 Will: this is deployed via bluemix, IBM's cloud offering, so it works as a cloud API. Once you have an account, you can call it. 17:31:08 http://ageandability.com/2016/09/21/simplifying-content-for-people-with-cognitive-disabilities/ 17:31:24 How does it deal with pictorial languages 17:31:29 Will: Can follow up with me on email. 17:31:53 Mike_Elledge: Language support? 17:32:11 q+ 17:32:14 zakim, who is on the phone? 17:32:14 Present: AWK, JF, steverep, Greg_Lowney, Lauriat, KimD, Laura, Kathy, MichaelC, Jim, kirkwood, Lisa, Srini, alastairc, marcjohlic, David-MacDonald, adam_solomon, MikeGower, Makoto, 17:32:17 ... Rachael, Joshue108, Pietro, JaEunJemmaKu, jon_avila, Elledge 17:32:32 ack mi 17:32:32 Will: Use cases for english at the moment, thus far that is the focus. Multi language support is on the roadmap. 17:32:35 ack r 17:32:38 ack l 17:33:24 Thanks Will! 17:34:11 +Wayne 17:34:14 present+ Jim_S 17:34:14 Thanks. Bye. 17:34:20 Thanks! 17:34:22 trackbot, end meeting 17:34:22 Zakim, list attendees 17:34:22 As of this point the attendees have been AWK, JF, steverep, Greg_Lowney, Lauriat, KimD, Laura, Kathy, MichaelC, Jim, kirkwood, Lisa, Srini, alastairc, marcjohlic, David-MacDonald, 17:34:26 ... adam_solomon, MikeGower, Makoto, Rachael, Joshue108, Pietro, JaEunJemmaKu, jon_avila, Elledge, Wayne, Jim_S 17:34:30 RRSAgent, please draft minutes 17:34:30 I have made the request to generate http://www.w3.org/2017/01/10-wai-wcag-minutes.html trackbot 17:34:31 RRSAgent, bye 17:34:31 I see no action items