Minutes: Low Vision Task Force date

Hello everyone,

Minutes from the today's teleconference can be accessed as hypertext at:
https://www.w3.org/2016/04/13-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
13 Apr 2016

See also: IRC log
Attendees

Present
    allanj, shawn, JohnRochford, Wayne, Scott, Laura, Jeanne, AWK(second_part)
Regrets
Chair
    Jim and Andrew
Scribe
    Laura

Contents

    Topics
        Issue 35 Update information on acuity
        Issue 42 3.5.1 - poor example illustration
        Issue 43 figure descriptions
        Issue 45 Note to tool developers not a user need - delete or edit?
    Summary of Action Items
    Summary of Resolutions

<shawn> [ when you send requests for comments, you can list it here so
we have a record of it ]

<shawn> [ ... https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Comments ]

Scribe List: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Scribe_List

<scribe> Scribe: Laura
Issue 35 Update information on acuity

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/35

<allanj> straw proposal:Some low visual acuity can be corrected with
glasses, contact lenses, or surgery – and some cannot. Therefore, some
people will not see small text or fine details no matter what.

<ScottMcCormack> I like it

Jim: Some discussion on the topic. Shawn has a straw proposal.

<JohnRochford> I suggest "at all" rather than "no matter what".

Jim: any thoughts?

<shawn> Some low visual acuity can be corrected with glasses, contact
lenses, or surgery – and some cannot. Therefore, some people will not
see small text or fine details at all.

<jeanne> +1 at all

RESOLUTION: Change intro to: Some low visual acuity can be corrected
with glasses, contact lenses, or surgery – and some cannot. Therefore,
some people will not see small text or fine details at all.

<Wayne> +1
Issue 42 3.5.1 - poor example illustration

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/42

<shawn> +1 to that response

<allanj> +

<allanj> +1

Jim: Comment on contrast of illustration of Wayne’s style sheet. It is
a real style sheet. He needs it to read.

Shawn: maybe change the figcaption?

<ScottMcCormack> does this figure meet color contrast requirements?

wayne: it is a little above minimum.

<ScottMcCormack> note that a user’s custom style may not meet color contrast

<ScottMcCormack> +1

<shawn> +1

Jim: preface with it with “This a real style sheet ueed by a person
with low vision.”

<ScottMcCormack> A user’s style sheet meets the user’s need and does
not need to meet WCAG requirements

<allanj> +1

<ScottMcCormack> maybe include a couple user examples to show some
wide variations

<allanj> ACTION: Jim to respond to commenter on Issue 42 [recorded in
http://www.w3.org/2016/04/13-lvtf-minutes.html#action01]

<trackbot> Created ACTION-46 - Respond to commenter on issue 42 [on
Jim Allan - due 2016-04-20].

RESOLUTION: Will preface with something to the affect that “This a
real style sheet used by a person with low vision.”
Issue 43 figure descriptions

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/43

Jim: Jim stated on writing long descriptions. Laura added some.

<ScottMcCormack> would our audiance need such long descriptions?

<allanj> laura and wayne think they are useful

<shawn> +1 to Scott

Jim: Useful and they are already done.

<JohnRochford> -1 to Scott

<allanj> shawn: what is the use case? would someone need the details?

<allanj> wayne: when they cant see them.

<allanj> awk: this section is to explain the issue, not to get into details.

<allanj> ... all see color differently. these are simulations.

<allanj> ... perhaps a couple of examples - yellow, pale yellow, pink,
light gray.

<allanj> ... point is ... people see colors differently, and need to
able to adjust colors to meet needs.

<allanj> laura: information is useful...for those who don't have full
color perception.

<allanj> awk: make simpler color wheels.

https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Color-Blindness-Table

<allanj> ... rainbow ROYGBIV

<ScottMcCormack> Color names are not always meaningful to people.
Describe the key differences such as reds or blues are missing

<allanj> ... worry about descriptions. what do those words mean?

<allanj> laura: perhaps we take them out.

<allanj> js: think they are useful.

<allanj> jr: these are user needs. should provide information.;

jon: why are we referencing color wheels at all?

jim: we have the info. What do we do?

Shawn: If we had something simpler? Would 3 colors get across the point?

<ScottMcCormack> Give details about what changes for each simulated wheel

<allanj> RGB

Shawn: maybe do the same with fewer colors.

wayne: if we think it is important. why not describe ot to all?

<ScottMcCormack> Fig5: “Shows red-green color blindness- Reds and
greens are missing replaced by shades of yellow with green and dark
red being the same shade of yellow"

<ScottMcCormack> something like that

JS: We lose the impact by simplfying it.

<jeanne> +1 for not being in the main document - a link to an appendix is good.

<shawn> shawn: I won't object to it being not in the main doc
(appendix or something)

https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Color-Blindness-Table

<shawn> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Color-Blindness-Table

<allanj> add clock positions

Scott: very educational
... information may get lost.

<shawn> ACTION: Shawn tweak color wheel alts - see Scott's suggestion
in minutes [recorded in
http://www.w3.org/2016/04/13-lvtf-minutes.html#action02]

<trackbot> Created ACTION-47 - Tweak color wheel alts - see scott's
suggestion in minutes [on Shawn Henry - due 2016-04-20].

<shawn> +1 wayne to intro sentence

wayne: maybe add a sentence.

<allanj> +1 wayne

+1

<jeanne> +1 wayne's intro sentence

<JohnRochford> +1 to sentence Wayne is trying to recall

<shawn> ACTION Shawn before color wheel examples, add an intro
sentence about this is what people see (see minutes with Wayne's idea)

<trackbot> Created ACTION-48 - Before color wheel examples, add an
intro sentence about this is what people see (see minutes with wayne's
idea) [on Shawn Henry - due 2016-04-20].

<Wayne> Colors that are different for people with full color
perception are the same for different types of color blindness.

<jeanne> ACTION: Jeanne will add the gray percentage instead of the
hex values. And the clock positions. [recorded in
http://www.w3.org/2016/04/13-lvtf-minutes.html#action03]

<trackbot> Created ACTION-49 - Will add the gray percentage instead of
the hex values. and the clock positions. [on Jeanne F Spellman - due
2016-04-20].

RESOLUTION: Will update table, alts and images descriptions - and add
appendix with detailed image descriptions.
Issue 45 Note to tool developers not a user need - delete or edit?

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/45

<allanj> ACTION: Jim create appendix for detailed image descriptions
from issue 43, and action-49 [recorded in
http://www.w3.org/2016/04/13-lvtf-minutes.html#action04]

<trackbot> Created ACTION-50 - Create appendix for detailed image
descriptions from issue 43, and action-49 [on Jim Allan - due
2016-04-20].

<ScottMcCormack> +1 for edit

Jim: perhaps an edit “It is easier to pick more readable fonts if each
font name in the list is in its font — e.g., Times, Veranda, Courier
(these should be in their font to illustrate) — so users can see how
each font looks before choosing it.”

<ScottMcCormack> I really like being able to preview fonts before I
pick something I can’t see

AWK: would vote for throwing it out.
... worries that it is a distraction.

<ScottMcCormack> Font names don’t convey information about how the font looks

<shawn> [ /me waffling back and forth on this one! ]

<ScottMcCormack> and one could end up with an unreadable page and
limited ability to switch out

<JohnRochford> Gotta go folks. Until next week...

<ScottMcCormack> yes

shawn: is this more of an issue for people with low vision?

JS: Choice is important to someone with albinism.

Scott: has been in situations where font choice it is important.

AWK: where does that actually happen? maybe have another preview. What
is the need?

<shawn> Scott: if change the font to an unreadable one, then maybe
can't even read it enough to change it back

<ScottMcCormack> +q

<shawn> http://w3c.github.io/low-vision-a11y-tf/requirements.html#font

<Zakim> shawn, you wanted to propose "see font before making
selection" (rather than specific in font) -- keep as note but not
specific user need?

Scott: we don’t want to restrict people to 1 solution but a preview is
a possible solution.

shawn: maybe change what we have to be more generic. Not prescriptive.

<allanj> +1 to shawn

AWK: can live with it.
... maybe we are describing a different user need.

Wayne: maybe we need to think about the big user need.

Jim: propose we make an issue

RESOLUTION: Will make the editorial change on issue 45 per minutes.

Jim: Let’s work in Github and try to get work done prior to call.
Summary of Action Items
[NEW] ACTION: Jeanne will add the gray percentage instead of the hex
values. And the clock positions. [recorded in
http://www.w3.org/2016/04/13-lvtf-minutes.html#action03]
[NEW] ACTION: Jim create appendix for detailed image descriptions from
issue 43, and action-49 [recorded in
http://www.w3.org/2016/04/13-lvtf-minutes.html#action04]
[NEW] ACTION: Jim to respond to commenter on Issue 42 [recorded in
http://www.w3.org/2016/04/13-lvtf-minutes.html#action01]
[NEW] ACTION: Shawn tweak color wheel alts - see Scott's suggestion in
minutes [recorded in
http://www.w3.org/2016/04/13-lvtf-minutes.html#action02]

Summary of Resolutions

    Change intro to: Some low visual acuity can be corrected with
glasses, contact lenses, or surgery – and some cannot. Therefore, some
people will not see small text or fine details at all.
    Will preface with something to the affect that “This a real style
sheet used by a person with low vision.”
    Will update table, alts and images descriptions - and add appendix
with detailed image descriptions.
    Will make the editorial change on issue 45 per minutes.

[End of minutes]
Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/04/13 15:36:25 $
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)

Succeeded: s/proposed edit:/straw proposal:/
Succeeded: s/proposed edit/straw proposal/
Succeeded: s/If we had something simpler?/If we had something simpler?
Would 3 colors get across the point?/
Succeeded: s/Will update table, alts and images descriptions/Will
update table, alts and images descriptions - and add appendix with
detailed image descriptions/
Succeeded: s/+!//
Found Scribe: Laura
Inferring ScribeNick: laura
Present: allanj shawn JohnRochford Wayne Scott Laura Jeanne AWK(second_part)
Found Date: 13 Apr 2016
Guessing minutes URL: http://www.w3.org/2016/04/13-lvtf-minutes.html
People with action items: jeanne jim shawn

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


[End of scribe.perl diagnostic output]


-- 
Laura L. Carlson

Received on Wednesday, 13 April 2016 15:44:43 UTC