dialin info at https://www.w3.org/2017/08/01-lvtf-info.html

Understanding https://github.com/w3c/wcag21/tree/master/understanding/21

<shawn> Jim: list of Understanding docs. Chairs decided TF should do first pass. Would like before TPAC early Nov

<shawn> ... anyone can edit

see the rendered (non-code view) - https://rawgit.com/w3c/wcag21/master/understanding/21/

<shawn> ... that is list of all -- including ones that didn't get included

<shawn> JohnR: I did understanding doc a few weeks ago and it hasn't been updated.

<shawn> Jim: Put it into here.

see the rendered (non-code view) - https://rawgit.com/w3c/wcag21/master/understanding/21/*short-name.html*

<shawn> These are just templates. Put content here. (some of it is elsewhere)

see the rendered (non-code view) - https://rawgit.com/w3c/wcag21/master/understanding/21/adapting-text.html

<shawn> For example, https://rawgit.com/w3c/wcag21/master/understanding/21/adapting-text.html

<shawn> Jim: Also need to work on Techniques

<shawn> Shawn & Jim will update User Needs/Req doc as well

Printing https://github.com/w3c/wcag21/issues/76

<shawn> Erich: Not looking good based on call and comments.

<shawn> Shawn: Theere is some support and understanding. But a lot of misunderstandings

<shawn> Jim: Red herring (like in mystery books - throws you off course) -- not related to real issue.

<shawn> ... page size and zoom are red herrings

<shawn> Erich: Likelihood of bringing people to understanding real issues?

<shawn> Jim: Responsive print design is a known best practice

https://www.polyglotprogramminginc.com/responsive-design-and-print-styling/

https://responsivedesign.is/articles/the-printer-is-a-device-too/

<shawn> Shawn: If there are legitimate issues, I'm fine letting it drop. But what I'm seeing is misunderstanding, not legitimate issues.

Testing

@media print {

body {

line-height: 1.5;

letter-spacing: .12em;

word-spacing: .16em;

}

p {

padding-bottom: 2em;

}

}

<shawn> Jim: Set adapted text settings. If prints, then passes.

sometimes I remove the @media and apply just to the rendered view to make it print correctly

<shawn> Erich: Need consensus by tomorrow

author knows content, knows layout and knows whats important it should print fine with the settings above.

the BROWSER does not know any of this.

<shawn> John: Somewhere under the impression that things that are at AAA now could be moved to AA possibly later.

<shawn> Jim: Getting it into the document, then can tweak.

<JohnRochford__> Correction: The comment just attributed to Erich was actually made by Jon,

+1 to getting it in at AAA

<JohnRochford__> John

NOTE: there is no requirement for testing larger fonts

<shawn> Erich: propose CSS for testing. add as AAA for this version so it gets public input.

<shawn> Shawn: Need to clear up misunderstandings.

<shawn> Shawn: Some people understood importance but said OK to put off to WCAG 2.2. I'm very concerned about that approach. For several reasons, one being that 2.2 is not a given.

<shawn> [some discussion about why there is resistance]

<shawn> Erich: I

<shawn> Erich: I'll do next comment as SC manager.

<shawn> Jim updated https://github.com/w3c/wcag21/issues/76

update issue and the SC for viewing to say When a page can be printed, essential information is printed with no loss of content or adapted text properties. (Level AAA)

survey - folks were not looking at current version. and did not understand the issue

jim added definitions

There are misunderstanding about what the SC covers. People were not reviewing the current wording. The SC doesnot cover Page/paper Size, Font Size, Zoom. Images not an issue with this proposed SC.

the people who opposed this before should be able to review.

img {max-width: 100%;}

https://github.com/w3c/wcag21/issues/76

https://github.com/w3c/wcag21/issues/76#issuecomment-324167545

if you put the adapted text in the rendered view, it prints. I think the issue is that we dont want the page to break when printing

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/ is dial in code still 646 045 716?//
Succeeded: s/Erich: I did understanding/JohnR: I did understanding/
Succeeded: s/(like in mystery books/(like in mystery books - throws you off course/
Succeeded: s/Erich: Some /John: Some/
Succeeded: s/ Images will be covered in Techniques./ Images not an issue with this proposed SC./
Default Present: Jim, Shawn, JohnRochford, Erich

WARNING: Replacing previous Present list. (Old list: Jim, Shawn, Glenda, JohnRochford, SteveRep)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ Jim, Shawn, JohnRochford, Erich

Present: Jim Shawn JohnRochford Erich
Regrets: Laura Glenda
No ScribeNick specified.  Guessing ScribeNick: allanj
Inferring Scribes: allanj
Found Date: 24 Aug 2017
Guessing minutes URL: http://www.w3.org/2017/08/24-lvtf-minutes.html
People with action items: 

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