Draft meeting minutes: 14th October, 2015

http://www.w3.org/2015/10/14-lvtf-minutes.html



[W3C]<http://www.w3.org/>

- DRAFT -
Low Vision Accessibility Task Force Teleconference
14 Oct 2015

See also: IRC log<http://www.w3.org/2015/10/14-lvtf-irc>

Attendees
Present
MichaelC, Srini, AWK, erich_manser, shawn, Jim, Laura, Katie, Haritos-Shea, Wayne, jon_avila, Andrew, CharlesO, Shawn, wayne
Regrets
Bruce, Erich
Chair
AWK
Scribe
jon_avila
Contents

  *   Topics<http://www.w3.org/2015/10/14-lvtf-minutes.html#agenda>
     *   volunteers with action items for MORE user cases (5 per category)<http://www.w3.org/2015/10/14-lvtf-minutes.html#item01>
     *   teleconference attendance https://www.w3.org/2002/09/wbs/81151/LVTF-telecons/<http://www.w3.org/2015/10/14-lvtf-minutes.html#item02>
     *   volunteers with action items for MORE user cases (5 per category)<http://www.w3.org/2015/10/14-lvtf-minutes.html#item03>
     *   rewrite use cases<http://www.w3.org/2015/10/14-lvtf-minutes.html#item04>
     *   Review of overview<http://www.w3.org/2015/10/14-lvtf-minutes.html#item05>
  *   Summary of Action Items<http://www.w3.org/2015/10/14-lvtf-minutes.html#ActionSummary>

________________________________

<trackbot> Date: 14 October 2015

<Ryladog> +Katie Haritos-Shea

<scribe> scribe: jon_avila
volunteers with action items for MORE user cases (5 per category)
teleconference attendance https://www.w3.org/2002/09/wbs/81151/LVTF-telecons/


awk: reminder that are asking people to indicate their telecomm attendance or non-attendance on the survey link

<Wayne> wayne+

<ChuckOp> chuckop+
volunteers with action items for MORE user cases (5 per category)

awk: discussion about user stories and use cases -- Eric put in some work after the call and one from John R. We need to get more content into.

<AWK> Wiki link user stories: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/User_stories_-_use_cases


awk: preference to get this filled out at outset
... if you have questions ask. Plan some time to take a look.

wayne: sorting out the effects of low vision on the wiki -- that was a big job.
rewrite use cases

awk: some are on the longer side. We need to get them crisp and concise. Look at ther shorter ones as models.
... don't need to go into solution as there isn't always one solution. We want to identify the user experience that is going to manifest itself.

laura: so we don't need to put in what solves the problem? The instructions indicate that.

awk: probably should suggest that.
... trying to get at the issues accessing content so we can talk about what you can do about it as the author or tool maker
... a solution may only work in one situation in one technology. Want to keep resolutions separate. We will need to collect user stories are addressed today as well.

<shawn> Chair: Andrew

awk: maybe have bullet under number and say how a user might experience something.
... if there is a solution for everything then people might think there is not a problem.

katie: specific suggestion for use cases that have already been written. For people who wrote them to make bullets --- keep what you have and then have tag line and then summary and then a deep explanation.

awk: sounds reasonable
... Katie could you model one?

katie: yes

awk: if you can't add new content then please try help out and make the content that is there more clear.

wayne: can we do a rough bibliography and then refer to them for now and then later re-organize into a proper bibliography

awk: could put citations as bullet so it doesn't appear as part of use case.

wayne: redid mine as story as it reads better.

awk: meant to put in review of updates to overview.
Review of overview

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


awk: did make some updates with nested lists on the wiki
... in the wiki you use # to make a numbered list. To do sub bullets you use #* the next item with just a # will be a numbear 2

katie: just did on use cases page -- there is an example of that as well.

awk: overview of low vision is last link in IRC. Spent some time last week moving things around.
... 4 main areas. Acuity, contrast, color, field loss
... Updated outcomes -- desired outcomes are increased clarity and reduced fatigue
... last week we talked about field loss. We changed it so it would just be about physical field loss
... we didn't cover environmental field loss
... wonder like a phrase like perceptual area might be confusing or helpful

<shawn> jon: ... field loss - environmental, e.g., very close to object ...

awk: field loss can be because of distance from screen or by zooming in. It is an outcome of what the user needs to do.
... field loss may be an outcome. Do we want to keep that in as a category as well.

wayne: find that effects fell into two categories -- functional limitations versus physical limiations.
... disease resuilt in conditions in eye or brain and the result is something such as field loss
... try to group together in field loss
... glare is another interesting one. There could be internal glare which could make external glare an issue. Glare could appear on both lists. The ability to deal with glare is a problem.
... does it present in the person or what the person can do.

<AWK> Wayne talking about this wiki page: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Types_of_Low_Vision


awk: wayne is referring to the types of low vision page

<laura> Wayne's 2 lists:

<laura> Effects: Conditions

<laura> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Types_of_Low_Vision#Effects:_Conditions


<laura> Effects: Functional Limits

<laura> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Types_of_Low_Vision#Effects:_Functional_Limits


wayne: challenges with categorizing the effects of low vision

shawn: wnated to check to see if I understand Wayne. Did you separate out into two lists. I think that is interesting and happy to help anyone figure out.
... Could create sub categories as nested lists.

wayne: would like someone to check over it.

<AWK> Jon: I like the approach of working toward functional issues rather than diseases

<laura> +1

<shawn> jon: continue to work to the functional issue. lot of people don't fit well into categories or even spcific eye condition, but have functional limitation

<AWK> ... many people don't have a specific condition but do experience the functional results

<AWK> ... people will want to be able to map conditions to functional outcomes to help understand

<AWK> ... other factors play into how users are affected - e.g. environmental factors

awk: goal was to have an appendix to relegate the specific of the medical conditions to functional concerns that ultimately work out.
... want to tell people that a site needs to address functional needs rather than a specific condition

wayne: would like people to review his list and make recommendations. Made a laundry list of items -- some are similar but have slight differences.

<shawn> [ refresh https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Types_of_Low_Vision#Effects:_Functional_Limits -- I started sub-bullets. I think it will help refine it ]

wayne: while we have a long list I want to get it down to a smaller group of main categories

awk: feels like it's something we could work on for 5 years and still not be perfect. We want to make it clear.
... our process is messy and imprecise -- we all need to try out different models and then come to consensu on the model that works.
... does that sound right to people?

<Wayne> +1

awk: our asks of people for the week are to review Wayne's page and the overview page and try and help us make some suggestions.
... carve out some time to take a look at user stories or items just mentioned.

<AWK> Overview page: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Overview_of_Low_Vision


<AWK> Types of low vision page: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Types_of_Low_Vision


shawn: thanks to Wayne for starting the comprehensive list. We will distill it -- I will work with it while multi-tasking with the others.

wayne: comes from the Anne Corne list of low vision

awk: any other thoughts to raise?

* I will be at IAAP

awk: not seeking a quarum -- if there are people and things to work on we can still have a call next week even though some people will be out at IAAP and elsewhere

shawn: leave time slot open for now.

awk: will let you know on Monday if it will happen.
... thanks everyone

<laura> Thanks! Bye.

Summary of Action Items
[End of minutes]
________________________________
Minutes formatted by David Booth's scribe.perl<http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm> version 1.140 (CVS log<http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2015/10/14 15:28:28 $
________________________________
Scribe.perl diagnostic output
[Delete this section before finalizing the minutes.]

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30

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 promise I'll volunteer to scribe in the future.  I need to become familiar with the procedures involved.//

Succeeded: s/wayen/wayne/

Succeeded: s/Wayne's 2 list:/Wayne's 2 lists:/

Found Scribe: jon_avila

Inferring ScribeNick: jon_avila

Default Present: MichaelC, Srini, AWK, erich_manser, shawn, Jim, Laura, Katie, Haritos-Shea, Wayne, jon_avila, Andrew, CharlesO

Present: MichaelC Srini AWK erich_manser shawn Jim Laura Katie Haritos-Shea Wayne jon_avila Andrew CharlesO Shawn wayne

Regrets: Bruce Erich

Found Date: 14 Oct 2015

Guessing minutes URL: http://www.w3.org/2015/10/14-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<http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm> diagnostic output]

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
Phone 703.637.8957
Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | Twitter<http://twitter.com/#!/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP>