EOWG Accessibility Principles

https://deploy-preview-6--wai-accessibility-principles.netlify.com/fundamentals/accessibility-principles/#distinguishable

<shawn> * Text is resizable up to 200% without losing information, using a standard browser;

<shawn> * Text spacing can be adjusted without losing information, and reflows on small screens;

<shawn> e-mail thread https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2019Apr/0014.html

<scribe> scribe: jimA

sh: very brief overview highlevel of 2.1 - need response

https://deploy-preview-6--wai-accessibility-principles.netlify.com/fundamentals/accessibility-principles/#distinguishable

* Text is resizable up to 200% without losing information, using a standard browser;

* Text spacing can be adjusted without losing information, and reflows on small screens;

<shawn> maybe:

<shawn> * Text can be resized up to 400%, and text spacing can be adjusted, without losing information.

<shawn> * Text reflows to a single column @@

sh: looking for simple general statements

<shawn> JA: Text reflows when zoomed

jj: is "without loosing information" too broad?

sh: very high level not comprehensive.
... point 1 resize...

+1

laura: +1

no other objections

sh: item 2 reflow
... is i"Text reflows when zoomed" clear

wd: Text reflows when zoomed with a browser

lc: "when zoomed in"
... Text reflows when user zooms in with a browser

sh: is ^^^ comprehensive enough?

<shawn> sh: zoom in or resize window

<shawn> ... to avoid [horizontral/bi-direactional] scolling

<shawn> jA:scrolling in the direction of the text

<shawn> wd: in-line scrolling

<shawn> Text reflows so users don't have to scroll to read a line of text.

Text reflows when users zoom to prevent inline scrolling

<steverep> Add "when zoomed" or "under magnification"?

<shawn> missing small window

Text reflows when users zoom or shrink window to prevent inline scrolling

<shawn> viewport

<shawn> ja: text not clipped off

ja: viewport width

<shawn> slh: viewport

wd: read a line of text without scrolling

close item 3

open item 1

https://www.w3.org/2002/09/wbs/81151/wcag22orSupp/results

results are 7 in favor of guidance. all respondents

<steverep> My 2 cents... Reading a single line of text does not require scrolling even when zoomed

this is for 2.2

discussion of 3 proposed SC - https://docs.google.com/spreadsheets/d/11IKqjRFvkRd2dAfUiyc5whhB3yIYXvSiirWct7KQIB0/edit#gid=0

jon: will go along with group decision.

<shawn> jima: If someone comes up with something, we'll review and support.

<shawn> jon: we can write techniques and such

jima: there are 20 proposed SC - 3 are LVTF

<shawn> wd: prefer wroding that more people can understand (supplemental guidance vs. SC)

supplemental doc would be best practices.

jon: hard to keep in synch.

sh: hope to have an integrated supplemental guidance for all TF docs (lv, coga, mobile)
... there is existing content, lv needs to provide some

requirements document is not finished. finishing will inform supplemental guidance

jim will send AGWG message that LVTF will not propose any formal SC to the group, but will support

scribe: others efforts with review and techniques

close item 1

open item 2

<shawn> https://www.w3.org/2002/09/wbs/81151/reflow-understanding/results

jon: 1410 can be broken by sticky headers, hidden items, etc.
... viewport width and reflow, not so much about zoom, more about reflow

survey:

The intent of this Success Criterion is to support people with low vision who need to:

enlarge text or

shrink the viewport size,

and in both cases read read the text in a single column. When the browser zoom is used to scale content to 400% or when pinch zoom reduces the width to 1/4 the original, text reflows - i.e., it is presented in one column so that scrolling in more than one direction is not necessary.

For people with impaired visual acuity, enlarged text with reflow enables reading. For people with limited visual field, shortening lines enables reading. These changes are critical for both groups. Enlargement enables perception of characters. Shortening lines enables viewing entire lines. Reflow enables tracking. Tracking is following along lines of text, including getting from the end of...

scribe: one line to the beginning of the next line.

Avoiding the need to scroll in the direction of reading in order to reveal lines that are cut off by the viewport is important, because such scrolling significantly increases the effort required to read. It is also important that content is not hidden off-screen. For example, zooming into a vertically scrolling page should not cause content to be hidden to one side.

jon: missing connection between reflow and shortened lines.

waynes wording http://nosetothepage.org/WCAG/1410/Und1410Change.html

wayne moderate wording - http://nosetothepage.org/WCAG/1410/ModerateIntent.html

jon: the relationship section does not address the problem of text getting smaller when zooming.

<wayne> http://nosetothepage.org/WCAG/1410/Example.html

jon: you don't have to have text 200% at 320 px. technically it is allowed, we want to encourage authors to not make text smaller.
... intention to foster 400% for reading text not necessarily headings etc.
... edge case - mobile view, and on desktop things will break when you reach the breakpoint.

Revisit this.

wayne will put up an editable version for review

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/jA; /jA:/
Succeeded: s/ JA: If s/ jima: If s/
Default Present: Jim, Wayne, Shawn, JoAnne, Laura, SteveRepsher
Present: Jim Wayne Shawn JoAnne Laura SteveRepsher
Regrets: Jason
Found Scribe: jimA
Inferring ScribeNick: JimA
Found Date: 11 Apr 2019
People with action items: 

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.)