See also: IRC log
<allanj> https://www.w3.org/WAI/GL/wiki/Providing_a_Semantically_Identified_Icon_Font_with_role%Dimg
<scribe> Scribe: Laura
Jim: Zoom content is going to CFC
AC: not sure when. Maybe soon.
Jim: Should be on Tuesday.
... Filed bugs on all the browsers.
... Google has been very active. May fix it.
... we will chip awy where we can.
... increased disscussion on ig list and webAIM
Steve: bugs for focus indicators?
Jim: not yet.
<allanj> http://w3c.github.io/low-vision-SC/luminosity-form-controls.html
Jim: maybe make a separate page for that?
Steve: should be separate.
Jim: With chrome has been
explaining how things should work.
... Glenda, if you need anything let us know.
Jim: people have been writing on this topic.
AC: Come at the problem from
another point of view though sizing.
... vertical and horizontal.
<allanj> SC - Adapting text:
<allanj> SC Text
<allanj> If the technologies being used allow the user agent to adapt style properties of text, then no loss of essential content or functionality occurs by adapting all of the following:
<allanj> line spacing (leading) to at least 1.5
<allanj> letter spacing (tracking) to at least 0.12 em
<allanj> word spacing to at least 0.16 em
<allanj> Note: Examples of text which are typically not affected by style properties are open captions and images of text, which are not expected to adapt.
<allanj> Editor's note: The Working Group seeks to to include overriding text color, background color, and font-family as part of this SC, but is not yet able to identify a way to do so that is sufficiently testable.
<alastairc> https://alastairc.ac/tests/letter-spacing.html
AC: letter spacing is our best bet.
<allanj> .1em letter spacing is about 23% horizontal size increase
AC: if we go above that 23%
things will break.
... then maybe reduce. it.
John: can the SC limit for body text?
AC: that is an option.
<wayne> Letter Spacing + 1/5(word spacing)+fontwidth =.1
wayne: thinking of a formula.
Letter Spacing + 1/5(word spacing)+fontwidth =.1
... may have stated 1.2 too strongly.
... may be too big.
AC: CSS units are EMs
... do need rationale. Limit is the difficulty it would
cause.
wayne: wide fonts are a problem
steve: trying to
understand.
... no idea what the user starts with.
... simplest is to spec a font.
AC: we are setting a benchmark.
<allanj> wd: need to bring font bullet back
I still don't know how bringing the font bullet back with the proposed metrics would help eliminate conflict pairs in font families.
Users can override font family.
Do we really want to try to bring back the font bullet?
<wayne> Use the language mean character size.
<Zakim> shawn, you wanted to say Understanding should make clear that user ability to change font and it works is bottom line assumption. (even though font is not specifically included in
Shawn: users can change
fonts.
... make it clear in the understanding doc.
https://rawgit.com/w3c/wcag21/adapting-text_ISSUE-74-78-79/understanding/21/adapting-text.html
<allanj> Shawn: Understanding document should make clear that user ability to change font and it works is bottom line assumption. (even though font is not specifically included in SC wording)
<alastairc> NB: The AG meeting is starting
wayne: make tables and compute
the numbers.
... tables of tolerance.
jim: users can change
fonts.
... authors can't do anything about it.
<shawn> what about technologies other than html & browsers :(
jim: font cant be blocked by the author.
ac: makes it hugely more complicated to have the bullet.
wayne: I’ll loose this one this time.
jim: we have silver coming up.
steve: current metics are not
being opposed.
... we have the editors note. Let’s try to get the SC in.
Jim: wayne has done incredible work.
Editor's note: The Working Group seeks to to include overriding text color, background color, and font-family as part of this SC, but is not yet able to identify a way to do so that is sufficiently testable.
<alastairc> Wayne: Chrome's high contrast extension: https://chrome.google.com/webstore/detail/high-contrast/djcfdncoelnlbldjfhinnjlhdjlikmph?hl=en
jim: we will come back to color.
<allanj> laura: still need a definition for "style properties"
<allanj> laura will work on CfC for Adapting Text
<allanj> wd: it may be possible to block font change with web components.
<allanj> open item 4
https://www.w3.org/WAI/GL/wiki/Providing_a_Semantically_Identified_Icon_Font_with_role%3Dimg
<allanj> ja: please give feed back.
<allanj> ... email
Steve: would like to see it applied to 1.3.1
Applicability: https://www.w3.org/WAI/GL/wiki/Providing_a_Semantically_Identified_Icon_Font_with_role%3Dimg#Applicability
<allanj> lc: some are resistant to adding failure techniques
<Glenda> +1 let’s try to establish this as a failure :)
<allanj> +1 to move on the 1.3.1 failure
wayne: do it for 2.1
<wayne> +1 to 1.3.1 failure
Steve: will draft a 1.3.1 failure.
wayne: it is important to get it through.
trackbot, end meeting
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/authors can/authors can't/ Default Present: Jim, Shawn, ScottM, steverep, Laura, Glenda, Wayne, alastairc, JohnRochford WARNING: Replacing previous Present list. (Old list: Jim, Erich, Shawn, ScottM, steverep, Laura, Glenda, Wayne, alastairc, JohnRochford) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Jim, Shawn, ScottM, steverep, Laura, Glenda, Wayne, alastairc, JohnRochford Present: Jim Shawn ScottM steverep Laura Glenda Wayne alastairc JohnRochford Regrets: Erich Found Scribe: Laura Inferring ScribeNick: laura Found Date: 08 Jun 2017 Guessing minutes URL: http://www.w3.org/2017/06/08-lvtf-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]