See also: IRC log
BRB
https://mit.webex.com/mit/j.php?MTID=mf593f4e1a73476b329f8348e58f53ffd
<allanj> s/Sean, use https://mit.webex.com/mit/j.php?MTID=mf593f4e1a73476b329f8348e58f53ffd/
<ScottM> My link worked but I had to type in meeting numbers and stuff
<allanj> scribe: JohnRochford
Jim: The first public working draft is coming up.
Laura: I think it's the end of February.
Ah, thanks.
Erich: Chatter on SC font family
and SC text color are being merged with SC spacing.
... I have been trying to facilitate discussion as SC
manager.
<Glenda> SC Manager Role: https://www.w3.org/WAI/GL/wiki/SC_Managers_Phase1#SC_Manager_Role
Laura: SC font and SC text color are so similar, they should be merged.
Jim and Alastairdiscussing print features of Safari.
Shawn: presented use case for discussion
Thanks, Laura.
<shawn> Use Case - e.g., user changes line-height & font with UserCSS, then wants to print it. (Think this works on most/all browsers, but not on some other technology user agents -- so authors need to provide format that does this.)
Wayne: Printing from PDFs is really a problem.
Shawn: That's what this is trying to address.
<laura> https://www.w3.org/WAI/GL/wiki/SC_Text_to_Combine_79,_78,_74
Laura: Latest issue is 19,
ability to override.
... Metrics are needed for each one.
Alastair: Just because the user can modify does not mean the web site will work afterward.
<allanj> to be testable, had to have some metrics. color = black/white then 99% of all other color combinations should work
Laura: Proposal 17 has all of Alastair's metrics in it, including using Comic Sans
<allanj> perhaps use verdana (wide font)
Wayne, Alastair, Laura agree Verdana issimilar to Comic Sans
<Glenda> From the ACAA “Characters displayed on the screen must be in a sans serif font. Characters must be 3/16 inch (4.8 mm) high minimum based on the uppercase letter I.”
<shawn> +1 for Verdana
<allanj> need to just use a "web safe font"
<allanj> +1 for verdana
Glenda: Talking about a requirement of the Air Carriers' Act.
<Glenda> ACAA = Air Carrier Access Act
Glenda: Actually required holding a ruler to the screen.
<alastairc> https://alastairc.ac/2013/02/how-to-hold-your-ipad/
<allanj> definition of a pixel: https://alastairc.ac/wp-content/uploads/2013/02/pixel-distance-graph.png
Jim: Next - Laura's comment on line height.
<allanj> line-height of all text to 1.36, letter-spacing to 0.03em, and word-spacing to 0.07em?
Glenda: Do we need to add a line after 1.36?
<allanj> line height is a unit less measurement
Glenda: It could be easily misinterpreted.
<allanj> shawn: line-height 1.5
Jim: Word spacing seems really small to me.
Wayne: This seems more like a technique than a SC.
Alastair: Agrees with Wayne.
Wayne: This could be applied at the element level.
<alastairc> My process email: https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JanMar/0418.html
Jim: Agrees with Wayne.
... We have some issues with this SC wording, but it will morph
some more.
Laura: Change the line height to 1.5?
+1 to 1.5
<allanj> Alastair: the SC is not restrictive. its just a base line to begin testing to see what breaks
<alastairc> suggest 1.5 / 0.05 (letter) / 0.1 (word)
Wayne: Will investigate line height and get back to Laura.
<shawn> [ Shawn is looking at data on leading. Some say up to 2.0. Shawn will put info on wiki page for folks to point to.]
<allanj> +1 to leaving letter and word spacing as is
<shawn> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/References#Leading
<alastairc> 1+
<allanj> if we apply max values for spacing will break things. perhaps choose a moderate level
Alastair: 2.0 would break most web sites - we should push for a moderate amount
<Glenda> +1 to setting a moderate baseline (that makes a difference)
<laura> Proposal 20:
<allanj> https://github.com/w3c/wcag21/issues/9
Glenda: Investigating/comparing 4.5 to 1 and 3 to 1
<allanj> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Informational_Graphic_Contrast_(Minimum)
Glenda: We should defer overlap with COGA to next stage
<allanj> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_(Minimum)
<Glenda> Take a screenshot and blow it up until you can see the pixels, and count. You do have to know whether your screen is high-DPI though.
<Glenda> For example, my MacBook is a 'retina' one, so when I take a screenshot it is double the resolution. I.e. my browser reports 1280px wide, but a screenshot of that comes out at 2560!
<Glenda> I also have a standard-res monitor I plug into as a second screen at work, so screenshots on that are 'normal' sized...
<Glenda> I would use the browser to add a 3px border around the image, and see if it is the same or bigger. I would then screenshot it and expand the image if I'm not sure. (See the attached, the outer red line is from the browser.)
<ScottM> should we use points instead?
Glenda: On Web Developer on Chrome, under Misc, is a ruler
<Glenda> There is a Display Ruler under Web Developer look under Miscellaneous (in Chrome)
<Glenda> http://www.quirksmode.org/blog/archives/2010/04/a_pixel_is_not.html
<alastairc> Or video: https://www.youtube.com/watch?v=4wscVOXjIzQ
Scott: Points are related to a physical size.
Glenda: Points are not consistent across resolutions and screen sizes.
<alastairc> See https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JanMar/0248.html
Alastair: CSS pixel is the most reliable measurement across resolutions and screen sizes.
Wayne: An absolute point does not exist any more on the web.
<alastairc> Content can be resized to 400% without loss of content, functionality or requiring two-dimensional scrolling, except for parts of the content where fixed spatial layout is essential to use or meaning.
Alastair: Resize text is now
shorter than it was.
... We are down to one exception because we dropped mobile.
Jim: Do we have a manager for metadata on hover?
Wayne: I will take it.
<allanj> ACTION: Wayne to manage metadata [recorded in http://www.w3.org/2017/01/26-lvtf-minutes.html#action01]
<trackbot> Created ACTION-94 - Manage metadata [on Wayne Dick - due 2017-02-02].
<allanj> https://github.com/w3c/wcag21/issues/75
Wayne: What's the status of the discussion on linearize?
Alastair: I don't think it's moved on.
<erich> got pulled to urgent matter, won't be able to rejoin FYI
<allanj> trackbot, end meeting
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Is anyone else getting a webex error? "Cisco WebEx had a problem processing your request. Contact support or your administrator and provide the following error tracking ID"/ / Succeeded: s/Sean, use // WARNING: Bad s/// command: s/Sean, use https://mit.webex.com/mit/j.php?MTID=mf593f4e1a73476b329f8348e58f53ffd/ Succeeded: s/Searn, Erich is logged in as erich, not ErichM/ / Succeeded: s/SC scripting/SC spacing/ Succeeded: s/line-height/line-height & font/ Succeeded: s/Alistair /Alastair/ Succeeded: s/technology user agents.)/technology user agents -- so authors need to provide format that does this.)/ Succeeded: s/are /is/ Succeeded: s/Shawn: We should defer overlap with COGA to next stage/Glenda: We should defer overlap with COGA to next stage/ Found Scribe: JohnRochford Inferring ScribeNick: JohnRochford Default Present: allanj, Laura, Wayne, Shawn, JohnR, ScottM, JohnRochford, Glenda, AlastairC, ErichM WARNING: Replacing previous Present list. (Old list: allanj, Laura, Wayne, Shawn, JohnR, ScottM, scribe, Glenda, wayne, AlastairC) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ allanj, Laura, Wayne, Shawn, JohnR, ScottM, JohnRochford, Glenda, AlastairC Present: AlastairC ErichM Glenda JohnRochford Laura ScottM Shawn Wayne allanj Found Date: 26 Jan 2017 Guessing minutes URL: http://www.w3.org/2017/01/26-lvtf-minutes.html People with action items: wayne WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]
