Minutes: Low Vision Task Force 10 Feb 2016 telecon

Hello everyone,

Minutes from the today's teleconference can be accessed as hypertext at:
https://www.w3.org/2016/02/10-lvtf-minutes.html

and as plain text following this announcement --  please report any
errors, omissions, clarifications, mis-attributions, and the like by
replying-to this announcement on-list...

Thanks.

Kindest Regards,
Laura


W3C
- DRAFT -
Low Vision Accessibility Task Force Teleconference
10 Feb 2016

See also: IRC log
Attendees

Present
    Shawn, Jim, JohnRochford, Laura, Andrew, JonAvila
Regrets
Chair
    SV_MEETING_CHAIR
Scribe
    Laura

Contents

    Topics
        Color blindness - not include stats? #20
https://github.com/w3c/low-vision-a11y-tf/issues/20
        Change to focus on ICT more broadly #9
https://github.com/w3c/low-vision-a11y-tf/pull/9
        Address JB's comment on international perspective #8
https://github.com/w3c/low-vision-a11y-tf/pull/8
        User Needs - specific settings #21
https://github.com/w3c/low-vision-a11y-tf/pull/21
        Scope and specificity #16
https://github.com/w3c/low-vision-a11y-tf/pull/16
        Change to scope and definition #10
https://github.com/w3c/low-vision-a11y-tf/pull/10
        Separate color from contrast #15
https://github.com/w3c/low-vision-a11y-tf/pull/15
        Brightness #22
https://github.com/w3c/low-vision-a11y-tf/pull/22 (changed from
https://github.com/w3c/low-vision-a11y-tf/pull/18)
        Factual Correction #17 https://github.com/w3c/low-vision-a11y-tf/pull/17
        Sending to WCAG WG & EOWG for approval to publish
        Use cases
        Visibility, Legibility, Readability
    Summary of Action Items
    Summary of Resolutions

<JohnRochford> +JohnRochford

<allanj> (If Wayne and I work on it Tuesday morning, we might get it
ready before the telcon. Otherwise, we might want to ask the LVTF if
this can be put off until after FPWD -- in which case we might want to
add a specific review note that we're working on it...)

<JohnRochford> I'm being identified incorrectly. Last name = Rochford

<scribe> Scribe: Laura
Color blindness - not include stats? #20
https://github.com/w3c/low-vision-a11y-tf/issues/20

Jim: Any objections to including the stats?

<shawn> OK with infcluding the stats

Jim: none

RESOLUTION: No objections to including the stats
Change to focus on ICT more broadly #9
https://github.com/w3c/low-vision-a11y-tf/pull/9

Jim: Okay with Shawn’s wording?
... none

RESOLUTION: No objections to Shawn’s wording

<allanj> https://github.com/w3c/low-vision-a11y-tf/pull/9#issuecomment-181577087
Address JB's comment on international perspective #8
https://github.com/w3c/low-vision-a11y-tf/pull/8

AWK: Looked into the legal aspect. Want to make sure we are speaking broadly.

Shawn: Thinks we cover it.

AWK: Okay.

<allanj> shawn's wording -
https://github.com/w3c/low-vision-a11y-tf/pull/8#issuecomment-181540462

RESOLUTION: No objections to Shawn’s wording.
User Needs - specific settings #21
https://github.com/w3c/low-vision-a11y-tf/pull/21

<allanj> change note:
https://github.com/w3c/low-vision-a11y-tf/pull/21/files?diff=split

RESOLUTION: No objections to Shawn’s wording.
Scope and specificity #16 https://github.com/w3c/low-vision-a11y-tf/pull/16

<shawn> "Most people with low vision have multiple visual impairments.
For example, people with macular degeneration usually develop central
field loss ("blind spots"), poor visual acuity, low contrast
sensitivity, and high light sensitivity."

<shawn> https://github.com/w3c/low-vision-a11y-tf/pull/16#issuecomment-181471268

RESOLUTION: No objections to Shawn’s wording.

<JohnRochford> +1 to most
Change to scope and definition #10
https://github.com/w3c/low-vision-a11y-tf/pull/10

<shawn> Edit suggestion:

<shawn> Some people have extreme sensitivity to light (called
photophobia). Bright light makes it difficult or impossible to see,
and causes eye pain and headaches. For some people, the normal
brightness of a computer screen with a light background is not
readable and painful. They need to change the background to a darker
color.

<allanj> +1

RESOLUTION: No objections to Shawn’s wording.
Separate color from contrast #15
https://github.com/w3c/low-vision-a11y-tf/pull/15

<shawn> suggested rewording

<shawn> Contrast sensitivity is the ability to distinguish bright and
dim areas of images, for example, to discern text on a background. A
common accessibility barrier for people with low contrast sensitivity
is gray text on a light background.

<shawn> Contrast is based on brightness ("luminance"). Colors that
look very different (for example, red, blue, green) can have similar
brightness, and not provide sufficient contrast. Tools are available
to determine the contrast ratio between colors.

<shawn> [ maybe without ("luminance") depending later discussion ]

RESOLUTION: No objections to Shawn’s wording.
Brightness #22 https://github.com/w3c/low-vision-a11y-tf/pull/22
(changed from https://github.com/w3c/low-vision-a11y-tf/pull/18)

<JohnRochford> +1 to brightness rather than luminence

<allanj> +1 to brightness rather than luminence

<jon_avila> using brightness is good with me as I think it is more understood

<shawn> use Brightness for the heading, and then put something like
this: "Brightness relates to luminance and luminosity. [references]
This document uses &quot;brightness&quot; for simplicity. -- and then
a separate write up on the more about luminance and luminosity

Wayne: Brightness is a generic term. Could write another paragraph
explaining things.

<shawn> ACTION: Wayne write up bit on luminance and luminosity for a
WAI page (or wiki page) [recorded in
http://www.w3.org/2016/02/10-lvtf-minutes.html#action01]

<trackbot> Created ACTION-34 - Write up bit on luminance and
luminosity for a wai page (or wiki page) [on Wayne Dick - due
2016-02-17].

RESOLUTION: No objections to Shawn’s wording.
Factual Correction #17 https://github.com/w3c/low-vision-a11y-tf/pull/17

Wayne: could leave it or could do a minor thing.

<jon_avila> I think the difference is important -- so thank you for
bringing this up. Not sure we have time to address now.

Jim: We could leave it for now and make a note we are working on that section.

RESOLUTION: No objections to making an explicit note that we are
working on this visibility section.
Sending to WCAG WG & EOWG for approval to publish

<shawn> http://w3c.github.io/low-vision-a11y-tf/requirements.html#to-do-before-fpwd

<allanj> things to do:

Shawn: Still some items to take care of @@ etc.

<jon_avila> +1 I am ok with the images

<JohnRochford> +1 I am ok with the images

<allanj> +1 am ok with images

Laura: +1

<shawn> I'll take a look at the images

shawn: may still have some minor tweaks.

<shawn> to dos:

<shawn> Sources / references 3Feb e-mail

<shawn> "categorical statements that should be qualified" 3Feb e-mail
(see also 3 Feb minutes "spacing is an issue for all people including
those without low vision")

<shawn> Final issues before FPWD

<shawn> Images

<shawn> CSS

<shawn> @@s throughout

wayne: references in wiki are quite complete.

<allanj> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Research

Shawn: don’t want to point to something that can change.
... could leave it flexible for now.

RESOLUTION: Accept sending to WCAG WG & EOWG for approval to publish
with understanding completion of minor “to dos” and notification.

<JohnRochford> +1

<allanj> +1

Laura: +1

<Wayne> +1

<shawn> +1
Use cases

Wayne: Looking at use cases. Thinking that organization should be inverted.
... example font size and single column has 2 uses.

Jim: good idea. But wants to take up next item.

<allanj> use technical aspect first and group user needs beneath
Visibility, Legibility, Readability

<allanj> visibility - can i see it at all

Shawn: Visibility = Can see if text is there.

Wayne: Difference of what a person can see and what they can read.

<shawn> [ I need to do more reading up on this because right now I'm
thinking differently about legibility and readability...]

Tinker study on what makes type legibile

Jim: Visibility term is new to me.

<shawn> +1 to Jim that visbility is new. and that we might need only
legibility and readability

<allanj> [me also -
http://logotalks.com/2012/06/05/font-readability-and-legibility/]

<shawn> Tinker, Miles A. (1963). Legibility of Print. Iowa: Iowa State
University Press.

<shawn> Note: In his seminal research, Tinker used only the term
legibility to avoid confusion with readability formulas for the level
of difficulty of the language; however, most recent literature
distinguishes between legibility and readability as explain on this
page. [from http://www.tader.info/understanding.html#refreadability ]

wayne: Visibility is usually called acuity limit. 20/20 line

shawn: we need to work on this some more.

Jime: Thanks all.
Summary of Action Items
[NEW] ACTION: Wayne write up bit on luminance and luminosity for a WAI
page (or wiki page) [recorded in
http://www.w3.org/2016/02/10-lvtf-minutes.html#action01]

Summary of Resolutions

    No objections to including the stats
    No objections to Shawn’s wording
    No objections to Shawn’s wording.
    No objections to Shawn’s wording.
    No objections to Shawn’s wording.
    No objections to Shawn’s wording.
    No objections to Shawn’s wording.
    No objections to Shawn’s wording.
    No objections to making an explicit note that we are working on
this visibility section.
    Accept sending to WCAG WG & EOWG for approval to publish with
understanding completion of minor “to dos” and notification.

[End of minutes]
Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/02/10 16:35:17 $
Scribe.perl diagnostic output
[Delete this section before finalizing the minutes.]

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Laura
Inferring ScribeNick: laura

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


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

Present: Shawn Jim JohnRochford Laura Andrew JonAvila

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 10 Feb 2016
Guessing minutes URL: http://www.w3.org/2016/02/10-lvtf-minutes.html
People with action items: wayne

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

-- 
Laura L. Carlson

Received on Wednesday, 10 February 2016 16:45:35 UTC