<scribe> Scribe: Laura

1.4.10 Reflow

<shawn> Background:

<shawn> * Understanding Doc: https://www.w3.org/WAI/WCAG21/Understanding/reflow.html

<shawn> * start of e-mail thread: https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2019Mar/0004.html

SH: issue is overall what is ideal vs what we could get in 2.1
... Is there additional guidance?
... we need draft wording.
... any issues we need to discuss?

wayne: we need to work on draft wording.

sh: we need a shared understanding first.

wayne: perplexed on how people can get confused on this.
... to allow for large print with reflow.
... the example 20 px text shrunk to 10 px.
... would be unexceptable.
... making fonts smaller is not a solution to this problem.
... relation to 1.4.4 some platforms can’t enlarge.
... need to correct understanding.

jon: accident or error?.

wayne: error.
... headings get mapped to smaller.

shawn: if it is a mistake it would be easy to fix.

jon: intention is stated at the top of the understanding doc. but that is not a given.
... what can we do to steer people in the right direction? and what can we do for 2.2?
... we want to proposed better sizes for the fonts.
... and make this about running text.
... legit reasons for shrinking some fonts.
... running text shouldn’t be changed.
... it is clear to me.
... goal change to 320 and be 4X size.
... have running text be that size.
... headings 200%
... need a technique.
... also a scale factor.
... same font size but scaled bigger.
... we don’t talk about that.
... people think this is about mobile but it is about low vision.

sh: sounds thike we have shared understanding. Do Jon and wayne want to work on wording?

Jon and Wayne: yes

jon: started to see the problem on things like collaborate.

wayne: don’t skrink running text.
... will start a first draft.

jon: need to adjust understanding doc and write a technique.

JJ: need to take care of the 10 px issue.
... makes sense to update understanding do a technique.

label proximity

<jon_avila> Detlev wrote up this https://docs.google.com/spreadsheets/d/1wRAViPfAJ4Ytqc71tGZp6gU07HNd2QQaNgtJsog-D90/edit#gid=124994642

<jon_avila> Label gaps When one element acts as a label of another element, the gap between the two is no larger than twice the width or height of the element labelled (whichever is smaller*). * This may be measured with an online ruler, possibly also automatically by a script processing the absolute positions and dimensions of two elements to work out the pixel offset. The simple formula is gap ≥ MIN(e.width;e.height) * 2

jon: delev agrees that there is a propblem with label proximity

<jon_avila> row 17

jon: row 17 of the spreadsheet.
... should detlev submit an issue or LVTF?

Shawn: who proposes it?

jon: shouldn’t matter who but the what (the wording matters).
... he is trying to come up with something objective.
... proposal is very limited.

wayne: need to think about it.

jon: lvtf agrees on principle.

wayne: sounds good. Would like to look for examples.

sh: should start a new email thread on list.
... vtf won’t we able to weigh offiaclly in before April 4 meeting -- unless we figure it out by e-mail

<shawn> s/lvtf won’t we able to weigh offiaclly in before April 4 meeting./lLVTF won’t be able to weigh offiaclly in before April 4 meeting -- unless we figure it out by e-mail

jon: Delev talked with wilco about auto test.

sh: thanks jon

jon: used to have AT to auto label

sh: anything else?
... do some work on list.
... next meeting April 4

s/LVTF won’t we/vtf won’t be/

rackbot, end meeting

trackbot, end meeting

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
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/stated/started/
Succeeded: s/offiaclly/officially/
FAILED: s/lvtf won’t we able to weigh offiaclly in before April 4 meeting./lvtf won’t we able to weigh offiaclly in before April 4 meeting -- unless we figure it out by e-mail/
Succeeded: s/deleve/Delev/
Succeeded: s/we ned to discuss/we need to discuss/
Succeeded: s/srinking/shrinking/
Succeeded: s/running text shouldn’t be changed./...running text shouldn’t be changed./
Succeeded: s/makes sense update /makes sense to update /
Succeeded: s/shouldn’t matter who but the wording./shouldn’t matter who but the what (the wording matters)./
Succeeded: s/looke/look/
Succeeded: s/lvtf won’t we able to weigh officially in before April 4 meeting./vtf won’t we able to weigh offiaclly in before April 4 meeting -- unless we figure it out by e-mail/
FAILED: s/LVTF won’t we/vtf won’t be/
Succeeded: s/vtf won’t we able/LVTF won’t be able/
Succeeded: s/undersranding/understanding/
Succeeded: s/techique/technique/
Default Present: Wayne, Shawn, Laura, Jon, JoAnne
Present: Wayne Shawn Laura Jon JoAnne
Regrets: Jason Alan
Found Scribe: Laura
Inferring ScribeNick: laura
Found Date: 21 Mar 2019
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)