<AllanJ> jim to check with Shawn about setting (ranges) for widget parameters (line spacing - at least 3 settings between x and y) that were proposed in UAAG

<ScottM> Is the availability survey still valid? The link is only showing me meetings through feb

<shawn> zaki, who is on the phone?

<ScottM> so moved :)

<scribe> Scribe: erich

AG call at 10:30, first item is Target Size and then Adapting Text

<AllanJ> open item 1

<laura> Proposal D

<laura> https://github.com/w3c/wcag21/issues/78#issuecomment-291618718

<laura> Proposal E F

<laura> https://github.com/w3c/wcag21/issues/78#issuecomment-291918379

<laura> Scoping

<laura> https://github.com/w3c/wcag21/issues/78#issuecomment-292174184

LC: Lots more discussion, and more proposals

<laura> If the technologies being used can achieve the following, text styles of the page can be overridden as detailed below with no loss of essential content or functionality.

WD: When WCAG 2.0 was devised, they were not talking about visual access to devices that can range 40 inches to 4 inches

LC: Need the exception, cannot be a note, needs to be right in the text

WD: Rule needs to be changed before we can write SC that make any sense

JA: There are several proposals on the table, all with slight variations of wording

LC: Could use help getting to concensus

<shawn> +1 (if I understadn the point)

<AllanJ> steve concerned about giving out for author doing bad things versus giving out for whole classes of technologies

<shawn> use a technology that supports it, (or else you have to make a widget or other way to do it)

(thanks Jim - was having trouble capturing)

<Zakim> steverep, you wanted to say author widgets may have unintended consequences since we haven't specified a full set of requirements

WD: Votes not to let authors off the hook because of technology

SR: Would like to keep it to the user is doing the styling

<Zakim> shawn, you wanted to reply to wayne and to ask question about providing alt version in conforming technology and to say instead of widget

<AllanJ> sh: if the technology doesen't work, then authors need to provide an alternate version

LC: Would expect to get objections from that, about needing to be technology agnostic

WD: That's why word-wrapping was not included in 1.4.4

<ScottM> font families or specific fonts?

<AllanJ> wayne: should be able to come up with 20 fonts (latin) to be included for the testing/widget

<AllanJ> ... other languages would have to come up with their own sets of fonts

<Zakim> steverep, you wanted to suggest exception language for technologies

<Zakim> shawn, you wanted to say SC setting the basis - and then more in Understadning and Techniques

<AllanJ> sh: have to have testable success criteria. then we have understanding document that explain what the SC means.

WD: in disagreement

<Glenda> Do we need ot move to the other call?

<laura> yes

<AllanJ> if you need to leave we will meet you there

<Glenda> see y’all in the next call

<steverep> Technology exception proposal for adapting text: Content presented in a technology which does not support changing text syles is exempt if either (a) a supported technology could not achieve the same content, or (b) text styles are not applicable to the content

<laura> bye

<shawn> We have said that we will need to document what users needs are met in WCAG 2.1 (and what not)

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/shawn is echoing really badly//
Present: Jim JohnR Laura ScottM Shawn Wayne Marla Erich StephenR JohnRochford steverep Glenda
Regrets: Glenda
Found Scribe: erich
Inferring ScribeNick: erich

WARNING: No "Topic:" lines found.

Found Date: 06 Apr 2017
Guessing minutes URL: http://www.w3.org/2017/04/06-lvtf-minutes.html
People with action items: 

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report