13:48:34 RRSAgent has joined #lvtf 13:48:34 logging to http://www.w3.org/2017/07/20-lvtf-irc 13:48:36 RRSAgent, make logs public 13:48:39 Zakim, this will be 13:48:39 Meeting: Low Vision Accessibility Task Force Teleconference 13:48:39 Date: 20 July 2017 13:48:39 I don't understand 'this will be', trackbot 13:54:36 chair: Jim 13:56:33 Agenda+ Fixed Headers (related to 77 resize content) 13:56:35 https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JulSep/0243.html 13:56:36 Agenda+ Popup Interference (MetaData on Hover) 13:56:38 https://github.com/w3c/wcag21/issues/75#issuecomment-309306101 13:56:39 Agenda+ Reflow/Linearize 13:56:41 https://github.com/w3c/wcag21/issues/58 13:56:42 Agenda+ Printing 13:56:44 https://github.com/w3c/wcag21/issues/76 13:57:02 zakim, clear agenda 13:57:02 agenda cleared 13:57:50 Agenda+ Fixed Headers (related to 77 resize content) 13:57:51 https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JulSep/0243.html 13:57:53 Agenda+ Popup Interference (MetaData on Hover) 13:57:55 https://github.com/w3c/wcag21/issues/75#issuecomment-309306101 13:57:56 Agenda+ Reflow/Linearize 13:57:58 https://github.com/w3c/wcag21/issues/58 13:57:59 Agenda+ Printing 13:58:01 https://github.com/w3c/wcag21/issues/76 14:49:28 laura has joined #lvtf 14:53:32 regrets: Marla 14:58:32 JohnRochford has joined #lvtf 15:00:06 Hi Jim. my 8:00 meeting is still going and I need to stay in there. :( I hope to be done before we get to the get to the printing topic 15:02:48 alastairc has joined #lvtf 15:04:38 scribe: Laura 15:05:12 Zakim, Open item 1 15:05:12 agendum 1. "Fixed Headers (related to 77 resize content)" taken up [from allanj] 15:05:14 Jim: Adapting text is in 15:05:16 Glenda has joined #lvtf 15:05:31 Jim: Congratulations to Laura for the Adapting Text SC! 15:05:37 https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JulSep/0243.html 15:06:06 Jim: Thread from Alastair on fixed headers 15:06:55 AC: most sites work well with our model. But grey area is fixed areas. 15:07:32 AC: can obsure 80% of content with fixed headers. 15:07:51 AC: media query can fix it 15:08:01 wayneDick has joined #lvtf 15:08:08 …need to define it. 15:08:33 …it is a tricky one. 15:09:35 …would be nice to have a failure. But not sure how to get it in. 15:10:08 Jim: Having it in the understanding doc seems resaonable. 15:10:32 …maybe a technique 15:10:59 s/resaonable/reasonable 15:11:28 SC: yes we can come up with a advisory technique. Hve one in mind. 15:11:49 s/Hve/Have 15:12:31 wayne: We can’t do everything at this time. 15:13:33 …we could put pictures in the techique. 15:15:02 Jim: would we test in portrait and landsacpe? 15:15:18 AC: should be covered in the existing SC text. 15:15:23 steverep has joined #lvtf 15:15:28 present+steverep 15:15:51 jim: add to the descriptiion. 15:16:25 Technique for: Using media queries to check for sufficient space of elements fixed to the viewport 15:16:59 AC: will draft a technique. 15:17:14 Action: Alastair to add text in description about fixed headers, and an advisory technique such as "Using media queries to check for sufficient space of elements fixed to the viewport" 15:17:15 Created ACTION-99 - Add text in description about fixed headers, and an advisory technique such as "using media queries to check for sufficient space of elements fixed to the viewport" [on Alastair Campbell - due 2017-07-27]. 15:17:40 present+ Laura 15:17:50 zakim, take up next item 15:17:50 agendum 2. "Popup Interference (MetaData on Hover)" taken up [from allanj] 15:18:32 jim: we have 4 weeks left before AG deadline for SCs 15:19:35 Jim: do we need any more on reflow? 15:19:47 topic: Reflow/linearize 15:20:15 AC: need to take away CSS so everything is vertical. 15:20:46 …lots of sites are unusable when you do this. 15:21:36 …more difficult. But think it is still on the table. 15:21:56 Laura: maybe ping David. 15:22:18 …David is the SC manager. 15:22:32 Wayne: think this is a lower priority. 15:22:54 …needs UA support. 15:22:59 A 15:23:11 AC: will take a lot of effort. 15:23:56 …lots of work still left to do on Adapting Text and Zoom 15:24:52 Jim: up to 400% we almost have linearization? 15:25:03 AC: it is different. 15:25:21 …zoom is cleaner. 15:25:56 Jim: any objections to lower prority for this one? 15:26:38 …no objections heard. 15:28:09 Jim: personization group will be forming. Will send out info on it later today. 15:28:50 topic: personalization 15:28:53 https://www.w3.org/TR/personalization-semantics-1.0/ 15:30:23 Task force in preliminary forrmation. LisaS and John LaPierre co-chairs 15:31:36 zakim, take up next item 15:31:36 agendum 3. "Reflow/Linearize" taken up [from allanj] 15:31:37 Topic: Popup Interference (MetaData on Hover) 15:31:46 https://github.com/w3c/wcag21/issues/75 15:32:01 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Wayne%27s_Metadata_Scratch_pad#Current: 15:32:37 Jim: link to waynes Scratch pad 15:32:54 For informational content that appears on hover or focus, all of the following are true: 15:32:56 Turn Off 15:32:57 The informational content can be turned off 15:32:59 Neither obscures nor is obscured 15:33:00 The informational content does not obscure the triggering content nor is it obscured by the pointer 15:33:02 Other method 15:33:03 hover and/or focus are not the only means of accessing the informational content 15:33:05 Not important 15:33:06 does not include information necessary to perceive content 15:33:08 Note 15:33:09 This does not apply to user agent rendering of the title attribute. 15:34:09 Jim: that is the current wording. 15:35:22 mgower comment: https://github.com/w3c/wcag21/issues/75#issuecomment-313684490 15:35:31 jim: mbgower had some concerns. https://github.com/w3c/wcag21/issues/75#issuecomment-313684490 15:37:00 he had issues with outline on links. and why this is against focus. 15:38:23 ja: if something has additional content, don't want it to pop up on hover or focus. want to know additional content exists and hit enter to make it appear and esc to make it go away 15:38:38 john: it can obscure 15:40:45 wayne: if outline (thick obscures) it shouldn't be there. 15:41:00 John: thin borders can obscure 15:42:44 Jim: The informational content can be turned off 15:43:29 …mike G said to use mechnism 15:43:31 mgower suggested: a mechanism is available to allow user control for the display of non-persistent textual information. 15:43:55 evil mechanism word 15:44:10 wayne: is it important to turn on/off 15:44:16 laura: depends 15:45:05 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Wayne%27s_Metadata_Scratch_pad#Current 15:45:15 reveal preseencse then activate in soem fashion 15:45:49 reveal presence then activate in some fashion 15:46:53 original wording: 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. 15:48:27 q+ 15:49:39 steve: for turning off what is the mechanism? 15:50:09 …how am I going to qurn it off? 15:50:34 s/qurn/turn/ 15:50:37 Meta Data on Hover · be fully visible, · be available on focus as well as hover · be available via any input method. · not be obscured, and · not obscure important content that is related to the triggering event. 15:51:38 Meta on Hover 15:52:41 steve: what is the other means? 15:52:47 jim: icon 15:52:55 be fully visible, be availableon focus as well as hover, be available via any input methos, Not be oblcuredd, not oblcure essential content 15:54:51 sr: if we eliminate focus/hover, what's left? 15:56:03 Gotta go, folks. 15:56:11 full visible, available on focus as well, not obscure essential content 15:57:08 sr: if not available on focus fails 2.1.1 - keyboard access 15:59:13 For informational content that appears on hover or focus, all of the following are true 16:00:35 q+ 16:00:46 all popup content is visible on the page, or a way to get to it to read it. (if you move mouse then no longer hover and tooltip vanishes) 16:02:03 sr: stuff running off the page, view a specific size/resolution. 16:02:08 steve: problem with stuff running off page. 16:02:31 ... focus is not triggered on hover. 16:03:27 ... if box appears when you hover over an icon, user should be able to move mouse to box and the box should not disappear until mouse off of the box 16:04:30 sr: should be any content 16:04:58 ... user can fully access content that pops up 16:05:11 ... user can get to information behind it also 16:06:34 lc: content is not obscured by or obscures triggering content. 16:07:33 Laura: Informational content that appears on hover or focus neither obscures nor is obscured by the triggering content. 16:08:58 To cover the one case: Content that becomes visible on hover or focus remains visible while hover or focus is on the triggering content or the appearing content. 16:11:12 1. not obscure triggering content 16:13:41 2. triggered content remains visible while mouse is on triggered content, or focus remains on triggering content. 16:14:24 gs: do we want authors to fix this, or can we get browser vendors to fix this. it will be a tough sell 16:15:51 sr: is this pointer dependent. if you have arrow pointer (even giant) - don't put tooltip in lower right, unless swap to left arrow then lower left is problematic 16:16:17 lc: perhaps an advisory technique 16:18:14 ja: tooltip is a browser thing. author created popups they can control 16:19:07 We have an exception related to “user agent control” in UIC Contrast Minimum. Jim, maybe you can be inspired by that language for this one too “User agent control 16:19:08 The color(s) of the user interface component and any adjacent color(s) are determined by the user agent and are not modified by the author.” 16:19:47 action: jim to create popup rewrite 16:19:47 Created ACTION-100 - Create popup rewrite [on Jim Allan - due 2017-07-27]. 16:20:15 topic: printing 16:20:30 https://github.com/w3c/wcag21/issues/76 16:21:08 wd: need to create a list of things that are necessary were dropped because of scope or browser issues 16:21:52 change font family and color 16:21:58 tooltip behavior 16:22:15 linearization 16:23:48 wayne: It works in firefox. 16:24:14 Jim: things can break. 16:24:42 this has browser implications 16:24:52 …is a browser issue in many ways. 16:25:17 wayne: 200% is the best you can do. 16:25:37 ja: all of the spacing trickles thru to printing, but not font size or zoom 16:26:08 present+ Shawn(part) 16:27:02 I know we're on printing, but here's my stab at Popup Interference: Popup content does not make its triggering content invisible, and remains visible while hover or focus is on the popup content or its triggering content. (where popup is defined as "appears on hoveror focus") 16:28:12 Jim: will post tesing to the list. 16:28:23 specify media in the CSS to change printing font size 16:28:46 +1 steve 16:28:48 shawn: fine with 200%. 16:30:47 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Printing_Customized_Text#Examples 16:33:13 shawn: thinks we should drop the zoom. 16:35:29 wayne: CNN is a failure of 1.4.4 on printed page. 16:36:13 laura has left #lvtf 16:36:35 need to reword SC to the authors makes print style sheet as flexible as on screen layout for accommodating adapting text spacing 16:38:18 rrsagent, make minutes 16:38:18 I have made the request to generate http://www.w3.org/2017/07/20-lvtf-minutes.html allanj 16:38:30 trackbot, end meeting 16:38:30 Zakim, list attendees 16:38:30 As of this point the attendees have been steverep, erich, Laura, Shawn(part) 16:38:38 RRSAgent, please draft minutes 16:38:38 I have made the request to generate http://www.w3.org/2017/07/20-lvtf-minutes.html trackbot 16:38:39 RRSAgent, bye 16:38:39 I see 2 open action items saved in http://www.w3.org/2017/07/20-lvtf-actions.rdf : 16:38:39 ACTION: Alastair to add text in description about fixed headers, and an advisory technique such as "Using media queries to check for sufficient space of elements fixed to the viewport" [1] 16:38:39 recorded in http://www.w3.org/2017/07/20-lvtf-irc#T15-17-14 16:38:39 ACTION: jim to create popup rewrite [2] 16:38:39 recorded in http://www.w3.org/2017/07/20-lvtf-irc#T16-19-47