14:51:03 RRSAgent has joined #lvtf 14:51:03 logging to http://www.w3.org/2017/02/16-lvtf-irc 14:51:05 RRSAgent, make logs public 14:51:05 Zakim has joined #lvtf 14:51:07 Zakim, this will be 14:51:07 I don't understand 'this will be', trackbot 14:51:08 Meeting: Low Vision Accessibility Task Force Teleconference 14:51:08 Date: 16 February 2017 14:51:18 chair: jim 14:52:04 regrets: Glenda 15:39:16 regrets+ Laura 15:39:36 Agenda+ Open AG questionnaires 15:39:44 Agenda+ Metadata on Hover 15:39:57 Agenda+ Printing customised text 15:40:22 s/customised/customized 15:59:29 erich has joined #lvtf 16:01:35 Scribe: Erich 16:04:42 Wayne has joined #lvtf 16:04:48 ScottM has joined #lvtf 16:04:59 steverep has joined #lvtf 16:05:07 present+steverep 16:05:09 zakim, who is on the call? 16:05:09 Present: steverep 16:05:26 present+ 16:06:37 Present+ Jim, Wayne, Eric, Shawn, Stephen 16:06:58 present+ ScottM 16:06:58 present+ScottM 16:07:18 whoohoo 16:07:24 Present: Jim, Wayne, Erich, Shawn, steverep, ScottM 16:08:47 Zakim, Open item 1 16:08:47 agendum 1. "Open AG questionnaires" taken up [from allanj] 16:09:06 Resize Content, Linearize and Graphics Contrast have been accepted to WCAG 2.1 so far 16:09:33 https://www.w3.org/2002/09/wbs/35422/SC_20170207/ 16:09:34 https://www.w3.org/2002/09/wbs/35422/SC_review_Feb14_2017/​ 16:09:57 Be sure to contribute your opinions to the 2 surveys currently open 16:16:11 SH: out clause question regards combined SC 124, we had discussed some alternate text 16:16:38 Bottom line: Authors provide content in a format that allows users to change the font, faimly, color, and spacing - and print it that way. (now make that in to SCs! :-) 16:16:48 JA: I can add a comment to the pull request to see what happens with it 16:20:24 WD: there will be a break point where you'll need to drop the linearize, but within certain limits you don't have to change the sructure of the page 16:20:33 current results Adapting Text survey https://www.w3.org/2002/09/wbs/35422/SC_review_Feb14_2017/results#xnew4 16:22:04 close item 1 16:22:27 Open item 2 16:22:53 https://github.com/w3c/wcag21/issues/75 16:23:35 JA: This may need to be overhauled to say write your own tool-tip that you have control over 16:24:33 SH: So we're saying we want every person to write their own tool tip? 16:24:37 Alastair 16:24:44 If we continue with that one, I suggest we narrow it to one of the possible issues: 16:24:45 1. Access to content in title attributes (I suspect this is generally covered by 2.1) 16:24:47 2. Title attribute obscuring other content. 16:24:48 3. Content becoming unusable with large pop-overs (like the Perkins example). 16:24:50 It occurs to me that removing title attributes is a very easy script to do, shall we tackle that on the UA site? 16:24:51 Does someone want to convert that issue into pop-overs obscuring content? 16:24:52 JA: Adding Alastair's comments 16:25:29 s/tool tip?/tool tip? (no) 16:26:48 +1 16:27:05 SM: Would not suggest people create their own tool-tips, cause lots of problems. Pop-overs seem like a good methoed 16:27:14 s/methoed/method 16:27:21 current SC text - Informational content that is only shown by hovering a mouse over an element is not used as the only means of conveying information and does not obscure other content. 16:28:47 JA: We have definition of informational content, but sounds like we need to describe 16:29:25 q+ 16:31:03 ack steve 16:31:31 https://github.com/w3c/wcag21/issues/75 16:34:11 The browser controlled tooltips will usually get out of the way of the mouse 16:35:50 JA: What is it that we want the author to do, a rule that's testable? 16:35:56 WD: And do-able 16:37:33 do we want users to be able to turn off these pop-overs 16:38:02 s/these pop-overs/these pop-overs? 16:39:00 WD: I can take this as an action to sort it out, though perhaps not by Tues 16:39:23 JA: This SC is not up on survey yet, so we have time to work on it 16:40:35 Action: Wayne to refocus #75 to pop-overs 16:40:40 Created ACTION-95 - Refocus #75 to pop-overs [on Wayne Dick - due 2017-02-23]. 16:41:53 close item 2 16:42:06 No thoughts on how to fix obscuring stuff, but I wish there was never actionable content within a hover element 16:42:40 open item 3 16:42:45 +1 16:43:14 https://github.com/w3c/wcag21/issues/76 16:43:36 Erich manager 16:45:52 Erich: when I print document, like the regular print and the none inverted colors. Use CCTV. I print to give to other people. they don't need what I need. 16:46:28 ... Comment - wcag is electronic not physical. 16:47:04 shawn: need content offline, so print for personal needs 16:47:52 examples: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Printing_Customized_Text#Examples 16:49:55 Author provides content in a format that allows print customization 16:50:53 current SC text: A mechanism is available to allow users to print page content with the presentation changes made by the user. 16:52:46 This would be very useful for creating large print handouts when necessary as well 16:55:04 shawn: access to information. people need to print for use off line. Authors should provide content in a format that can be printed based on user needs 16:55:39 q? 16:56:23 Content is in a format that allows print customization. 16:57:42 Content is provided in a format that allows print customization. 16:58:41 there are issues with presentation modifications being printed directly. Currently, must go to printing layer 16:58:48 +1 16:59:00 q+ customize what? 16:59:27 ack s 16:59:28 q- customize 16:59:32 q- what? 17:00:17 Content is provided in a format that allows print customization of #124. 17:00:22 customize what? 17:00:40 steve: text only? 17:00:52 SH: Well, there's ideal and then there's minimum 17:01:04 SH: The issue is what is the acceptable minimum 17:01:39 UAAG 2.0 "the user can have content printed as it is rendered on screen," 17:01:54 SH: (from uaag) users can have content printed as it is rendered on screen 17:01:54 is under "1.4.4 Configured and Reflowed Text Printing: The user can print the rendered content, and the following are all true: (Level AA)" 17:02:07 shawn: start with 124, ideally - spacing, font, hyphenation, margins, etc. 17:02:46 perhaps user queries https://decadecity.net/blog/2015/06/28/user-queries and for printing 17:05:03 shawn: printing with changes from 124 and reflow. perhaps linearization 17:08:00 close item 3 17:11:03 rrsagent, make minutes 17:11:03 I have made the request to generate http://www.w3.org/2017/02/16-lvtf-minutes.html erich 17:15:42 +q 17:20:23 ack s 17:20:50 rrsagent, make minutes 17:20:50 I have made the request to generate http://www.w3.org/2017/02/16-lvtf-minutes.html erich 19:25:31 Zakim has left #lvtf 20:51:26 rrsagent, clear agenda 20:51:26 I'm logging. I don't understand 'clear agenda', allanj. Try /msg RRSAgent help 20:51:40 trackbot, end meeting 20:51:40 Zakim, list attendees 20:51:48 RRSAgent, please draft minutes 20:51:48 I have made the request to generate http://www.w3.org/2017/02/16-lvtf-minutes.html trackbot 20:51:49 RRSAgent, bye 20:51:49 I see 1 open action item saved in http://www.w3.org/2017/02/16-lvtf-actions.rdf : 20:51:49 ACTION: Wayne to refocus #75 to pop-overs [1] 20:51:49 recorded in http://www.w3.org/2017/02/16-lvtf-irc#T16-40-35