W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

02 Dec 2015

See also: IRC log

Attendees

Present
jim, Shawn, Jeanne, Laura, AWK, Erich_Manser, JohnR, WayneD, Katie, Haritos-Shea
Regrets
Alan, Chuck
Chair
Andrew and Jim
Scribe
Laura

Contents


<JohnRochford> Jim, I can't get in to the conf call.

<JohnRochford> access codes being reported as invalid

<JohnRochford> I'm using the ones in your message

<JohnRochford> Has the meeting started?

<JohnRochford> That might be it

<JohnRochford> Good morning to you too!

<JohnRochford> I'm trying. Now finding password.

<JohnRochford> Hi, yes, I used that password. Unbelievably, I was just presented with a CAPTCHA, which is inaccessible to me.

<JohnRochford> I shall try by phone again.

<JohnRochford> I will send it to you, Jim, via email.

<JohnRochford> I'm in WebEx now

<AWK> +AWK

<AWK> +Erich_Manser

scribe

<AWK> Scribe: Laura

Framework for requirements document https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Overview_of_Low_Vision#Categories

AWK: Looking at overview of lowvision Wikii page. Want to move it to Git Hub.
... How do we want to use it in the overview?

<allanj> Shawn categories:

<allanj> Luminance and color

<allanj> Visual acuity

<allanj> Perceiving (Letter Characteristics)

<allanj> Spacing for Reading

<allanj> Distinguishing

<allanj> Perceptual area

<allanj> Tracking

<allanj> Point of Regard and Proximity

AWK: Initially had some other factors.

<allanj> Printing is missing from list above

AWK: What makes the most sense?

<Wayne> is there a different code?

John: list near sighted and farsighted under visual acuity?

Shawn: maybe in the overview as it is related to all.

Jim: Should focus on: can’t see the screen.

AWK: Far more nuanced.

<allanj> Katie+

Shawn: We need to find the link to piror minutes

John: Do we need to figure this out now?

AWK: Good point.
... Is everything captured in the second group?
... Don’t think it is a problem.

Katie: Think it may be too broad.

AWK: Distinguishing may not fit.

Katie: Barriers to distinguishing. Or ability to distinguish.

<Wayne> One issue is that individual impairments may imply multiple categories

John: why are we going int solutions?

Shawn: 2 different things.

AWK: Feels like the distinguishing section is more about perceiving element characteristics.

<allanj> Illumination/contrast discussion link added to the Overview Wiki

<Wayne> Fatigue occurs in almost conditions.

Katie: How about distinguishing and identifying?

AWK: The 3 things are definitely related.

Jim: Distinguishing is part of the spacing.

<shawn> how about Distinguishing Elements (e.g., headings)

Jim: All closely related.

John: Suggest don’t get into detail at this point.

AWK: look at tweaking these. Perhaps change the headings.

John: yes.

Katie: the need is the inability to distingusish.

<allanj> awk - requirement is the user needs to be able to distinguish

<JohnRochford> Clarification: I said "yes" to the characterization that this is a user needs doc, not a solutions doc.

AWK: Need to look at categories more.
... Tracking feels like they may be needs or solutions.
... Overview is general document and a frame work.
... shouldn’t be about the solutions.

<JohnRochford> +1

+1

<shawn> +1 agree to Andrew's overview of the sections & this doc , and next

<allanj> overview of low vision issues - broad strokes, general. set up a framework/categories

<allanj> requirements of specific user needs based on framework

<allanj> separate doc: solutions - techniques

<Zakim> Ryladog, you wanted to add that the NEED is to be able to Distinguish and Identify

Katie: Need is to distinguish and identify.

Wayne: Wonder if we need a middle section and think of these in terms of POUR.

<shawn> Wayne: Visual acuity is physical limitation whereas Luminance is @@

AWK: one topic for overview is perceptual area
... Can have things fit together.
... Move text around so that we only have one list

Wayne: Kind of losing things with luminance and color. Contrast sensitivity and light sensitivity.

<shawn> Wayne: contrast sensitivity, light sensitivity, color perception

AWK: For overview talk about 3 bullets.
... Categories and desired outcomes.

Wayne: Hard to measure fatigue. But we need to address it as it is a barrier for users.

AWK: Yes, we need to address the fatigue issue.

Wayne: Environmental issues are important.

AWK: Can move categories to GitHub. Are people okay with that?

Shawn: maybe work in the Wiki for a while.

<shawn> [ thinking about POUR... most of these are P I think... I agree save this until later ]

<allanj> jim tackle acuity overview

<allanj> wayne - luiminance and color

<allanj> andrew - perceptual

Wayne: Luminance and color

Jim: Visual acuity

<AWK> Trackbot, end meeting

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2015/12/02 16:32:51 $

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/I am having trouble getting in. Working on it.//
Succeeded: s/ solutions - techniques/separate doc:  solutions - techniques/
Succeeded: s/Visual acuity is @@ whereas Luminance is @@/Visual acuity is physical limitation whereas Luminance is @@/
Found Scribe: Laura
Inferring ScribeNick: laura
Default Present: jim, Shawn, Jeanne, Laura, AWK, Erich_Manser, JohnR, WayneD, Katie, Haritos-Shea
Present: jim Shawn Jeanne Laura AWK Erich_Manser JohnR WayneD Katie Haritos-Shea
Regrets: Alan Chuck
Found Date: 02 Dec 2015
Guessing minutes URL: http://www.w3.org/2015/12/02-lvtf-minutes.html
People with action items: 

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


[End of scribe.perl diagnostic output]