W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

30 Sep 2015

See also: IRC log

Attendees

Present
jeanne, AWK, wayne, jallan, Laura_Carlson, bruce_bailey, Ashley_graham, cherie
Regrets
Chair
SV_MEETING_CHAIR
Scribe
wayne

Contents


<trackbot> Date: 30 September 2015

<trackbot> Sorry, jeanne, I don't understand 'trackbot should start both zakim and rrsagent.'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.

<AWK> +AWK

<allanj> +allanj

<jeanne> present?

<AWK> +AWK

+wayne

<allanj> +jallan

<laura> +Laura_Carlson

<scribe> scribe: wayne

<AWK> +bruce_bailey

<allanj> close item 5

<bruce_bailey> +bruce_bailey

<allanj> open item 4

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

jallan: Ashley Grahm from IBM sought advice from Jim Allan to discuss low vision accessibility issues for a hack-a-thon

<allanj> Ashley from IBM Design

<allanj> Rejoin email is dated Sept 25

<AWK> +Ashley_graham

<AWK> +cherie

AWK: The WCAG charter was renewed. You need to rejoin WCAG WG. Invited Experts need to join, other members need to contact your AC member, This can be done though a survey that only has submit that MichaelC sent out.

<AWK> +erich_manser

Ashley_Grahm: UX from IBM is here to listen and learn.

<AWK> +michaelC

The Group: Introductions around

<allanj> close item 4

<allanj> Open item 6

<allanj> - these are who LV users are (overview)

<allanj> - functional limitations (e.g. low acuity - larger font size)

<allanj> - these are their visual content needs

<allanj> - appendix: map functional limitations to low vision conditions

allanj: We have been gathering user stories as a basis to start the discussion on user needs

<allanj> wd: like the categorizing and functional descriptions

<allanj> ... make it clear what function if being blocked

<allanj> conditions are fuzzy, you can have folks with identical conditions but function very differently

AWK: Do we use limitations as mapped to condition and then barrier.

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

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

allanj: I am leery of focusing on medical conditions. Functional definitions are better to describe conditions for our use.

<AWK> We need to update the overview page with the modifications on the user stories page

<allanj> ACTION: jim to humanize the Overview of Low Vision [recorded in http://www.w3.org/2015/09/30-lvtf-minutes.html#action01]

<trackbot> Created ACTION-4 - Humanize the overview of low vision [on Jim Allan - due 2015-10-07].

<laura> Medical conditions are all over the map: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Types_of_Low_Vision

allanj: Can clean up the overview page definition, give it characters (names), clarify etc.

<allanj> ack

<AWK> Wayne: I think that functional categorization is a good starting point when we are talking about needs

<AWK> Bruce: legge's 4 categories vs "jim's" 6 categories?

<allanj> wd: Legge and Jim's overview are similar.

<bruce_bailey> * I have to drop off for ~15 minutes

<laura> Beyond Accessibility: Treating Users with Disabilities as People: http://www.nngroup.com/articles/beyond-accessibility-treating-users-with-disabilities-as-people/

allanj: Neilson/Norman study reveals that it takes more time to do many tasks for partial sight than no sight.
... Could overview be expanded to include functional limitations? An open question.

+1

<laura> +1

<AWK> +1

<allanj> +1 outline

allanj: Is the basic structure of the outline a good start.

<allanj> close item 6

<allanj> Open item 7

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

<allanj> perhaps combine blur/glare and light sensitivity

<allanj> wd: there are differences.

<allanj> wd: blur/glare is functional limitation.

<allanj> fatigue is a result of reading with low vision

CherieE: With lighter eyes light sensitivity increases, it also increases with age.

<allanj> as you age you need more light,

CherieE: It is fairly common to become increasingly light sensitivity, use sunglasses, don't stare at a back-lit computer.

allanj: I use beige instead of white.
... I change the elements extensively, background, tool-tips, icon fonts

<allanj> in windows

<allanj> wd: windows 95 was very flexible for color/contrast for elements

<allanj> wd: had to choose high contrast then adjust color in Win8

<allanj> wd: it was responsive to my needs. word wrap was important

<allanj> awk: many applications allow this color change

AWK: There are desktop apps has a lot of HTML native apps.

allanj: Mobile apps are what they are and that is what you get.

<AWK> Erich, the wiki page: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/User_stories_-_use_cases

<allanj> wd: size limitation is that an encoding for acuity? some of the terms are not functional, like contrast.

<allanj> ... we have blurring of functional limitation and medical condition

<allanj> wd: diagnosis, consequence, solution

<allanj> awk: light sensitivity and low acuity - needs contrast and size

<allanj> wd: field loss, light sensitivity

<allanj> awk: field loss - restricted field - missing parts of visual field.

<allanj> ... reduced field because of increased font size

<allanj> wd: "environmental field loss"

AWK: Field loss has two sides physical and caused by adjustment.

<allanj> ACTION: jim to edit terms create definitions to clearly focus on function with wayne [recorded in http://www.w3.org/2015/09/30-lvtf-minutes.html#action02]

<trackbot> Created ACTION-5 - Edit terms create definitions to clearly focus on function with wayne [on Jim Allan - due 2015-10-07].

<allanj> rssagent, make minutes

<bruce_bailey_> * back, sorry

<laura> bye

<bruce_bailey_> * bye

trackbot, end meeting

Summary of Action Items

[NEW] ACTION: jim to edit terms create definitions to clearly focus on function with wayne [recorded in http://www.w3.org/2015/09/30-lvtf-minutes.html#action02]
[NEW] ACTION: jim to humanize the Overview of Low Vision [recorded in http://www.w3.org/2015/09/30-lvtf-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/09/30 15:31:27 $

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)

Found Scribe: wayne
Inferring ScribeNick: Wayne

WARNING: No "Topic:" lines found.

Default Present: jeanne, AWK, wayne, jallan, Laura_Carlson, bruce_bailey, Ashley_graham, cherie, erich_manser, michaelC

WARNING: Replacing previous Present list. (Old list: AWK, Wayne, Bruce, Srini, Cherie, Laura, Chuck, Jeanne, Michael, Alan, Charles_Oppermann, Srinivasu, Carlson, bruce_bailey, Alan_Smith, jon_avila, chuckop)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ 


WARNING: Replacing previous Present list. (Old list: (no, jeanne, one))
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ jeanne, AWK, wayne, jallan, Laura_Carlson, bruce_bailey, Ashley_graham, cherie

Present: jeanne AWK wayne jallan Laura_Carlson bruce_bailey Ashley_graham cherie

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

Found Date: 30 Sep 2015
Guessing minutes URL: http://www.w3.org/2015/09/30-lvtf-minutes.html
People with action items: jim

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]