W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

05 Oct 2017

See also: IRC log

Attendees

Present
JohnRochford, alastairc, allanj, scott, steverep
Regrets
Shawn, Glenda, Erich
Chair
Jim
Scribe
allanj

Contents


Hour long meeting today! then AG call

<scott> hello hello?

<alastairc> Something for discussion soon, perhaps not today: https://github.com/w3c/wcag21/issues/335#issuecomment-334468667

<alastairc> Regarding zoom content.

<scribe> scribe: allanj

zoom

Something for discussion soon, perhaps not today: https://github.com/w3c/wcag21/issues/335#issuecomment-334468667

For content with horizontal lines of text, content can be zoomed up to 400% from a starting width of 1280 CSS pixels without loss of content or functionality, and without requiring horizontal scrolling to read horizontal lines of text.

For content with vertical lines of text, content can be zoomed up to 300% from a starting height of 960 CSS pixels without loss of content or functionality, and without requiring vertical scrolling to read vertical lines of text.

Parts of the content that require two-dimensional layout for usage or meaning are excepted.

<JohnRochford> https://github.com/w3c/wcag21/issues/335#issuecomment-334468667

ac: this text seems to cover all possible cases
... it is longer. covers the cases, prevents what we don't want, allows what we do want.

<alastairc> https://www.chenhuijing.com/zh-type/

sr: the vertical part. browser reflow horizontally regardless of the text directions

ac: horizontal reflow is new to browsers.
... there are small blocks that will fail depending on text direction.
... focusing on blocks of content rather than page level.
... need to mull this a bit.

jr: pixel definition absolute to viewport size?

ac: pixels are relative to device by definition. should be consistent

sr: will this be a testing issue... always have to start at 1280 pixels

ac: desktop browsers only current ones that zoom with reflow. it eliminates pinch zoom.
... could add testing criteria

No testing in Understanding document

ac: join in on GitHub

jim mine https://github.com/w3c/wcag21/issues/77 for content for Understanding

<scott> woot woot

Understanding Graphics Contrast https://www.w3.org/2002/09/wbs/81151/Understanding2/results#xq1

essential vs important vs necessary wording

please review: https://www.w3.org/2002/09/wbs/35422/essential_breakout/

ac: perhaps remove second part of def.

sr: first part is subjective. second part is essential and hard to meet

ac: as site owner... if you took X away ... does it matter. as a definition

ja: perhaps a rule or protocol

sr: essential - effects many lvtf SC. 11 times in 2.1 SC.
... glossary def doesn't match what is meant in SC
... lvtf uses it in Graphic Contrast and others.
... proposed use necessary or required for understanding. synonym replacement.
... UI contrast, Adapting Text, all use essential.
... what loss is acceptable?
... hover - essential content in trigger - white space, part of background. added pure decoration

ac: UI contrast. ... if you have a visual identifier, if you add essential then you need to define essential visual identifier.

sr: produce examples on both sides of the word.

jr: voted yes for suggested changes in essential breakout

need Written techniques for

-include labels and values with the graphic

-contrasting differentiated pattern

-include contrasting lines between adjoining colors.

-include data within graphic (red piece of pie chart - white circle within red piece - 37% written in white circle)

would be interesting to use the same graphic and apply different techniques to make contrast accessible

sr: agree with Laura. Make the graphic visible by improving contast. not just applying text contrast to graphics.

<JohnRochford> I too agree with Laura.

ac: will be adding more examples, strengthening first intent para.

jim will post related materials for graphics.

add to agenda - Hover Understanding review

add to agenda reviewing comments

and suggest to AG to close

with explanation

Trackbot, end meeting

rrsagne, please leave

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/10/05 15:55:21 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Default Present: JohnRochford, alastairc, allanj, scott, steverep
Present: JohnRochford alastairc allanj scott steverep

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

Regrets: Shawn Glenda Erich
Found Scribe: allanj
Inferring ScribeNick: allanj
Found Date: 05 Oct 2017
Guessing minutes URL: http://www.w3.org/2017/10/05-lvtf-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]