15:24:41 RRSAgent has joined #lvtf 15:24:41 logging to http://www.w3.org/2015/12/09-lvtf-irc 15:24:57 rrsagent, set logs public 15:25:11 rrsagent, make minutes 15:25:11 I have made the request to generate http://www.w3.org/2015/12/09-lvtf-minutes.html allanj 15:25:26 rrsagent, set logs public 15:25:46 chair: Jim 15:27:47 regrets: Andrew 15:29:33 present+ Shawn 15:29:43 zakim, who is on the phone? 15:29:43 Present: jim, Shawn, Jeanne, Laura, AWK, Erich_Manser, JohnR, WayneD, Katie, Haritos-Shea 15:29:45 AWK has joined #lvtf 15:29:48 present: 15:29:52 zakim, who is on the phone? 15:29:52 Present: (no one) 15:29:54 present+ jim 15:30:11 present+ shawn 15:30:36 agenda? 15:30:44 Wayne has joined #lvtf 15:30:53 zakim, drop agenda 8 15:30:53 agendum 8, user needs section intros: descriptions or summaries, or both?, dropped 15:31:46 +AWK 15:31:58 present+ John 15:32:03 +wayne 15:32:35 Ryladog has joined #lvtf 15:32:45 JohnRochford has joined #lvtf 15:34:06 I love awards 15:35:11 how do I dial in or use webex. I have been trying for 15 minutes and I don't want to miss this meeting. 15:35:54 s/how do I dial in or use webex. I have been trying for 15 minutes and I don't want to miss this meeting. / 15:35:58 present+ Laura 15:37:01 Alan_Smith has joined #lvtf 15:37:25 Present+ Katie Haritos-Shea 15:37:32 trying to connect audio 15:37:50 could you dial me. 15:37:52 Just joining in on irc. There are two different phone number acccess codes in last meeting invite and they both do not work 15:38:07 Wayne 562-256-4458 15:38:35 No 562 493 8210, I'm flustered 15:39:59 I hung up by accident. 15:40:41 updating my calendar entry and downloading webex as this is first time I got in on new tablet. 15:42:04 W3C number +1-617-324-0000 is "not in service"? 15:42:45 katie - see my e-mail with passcode correction 15:42:51 ok 15:42:55 thanks 15:43:00 meeting code correction 15:45:10 Yes I am on that one but the audio does not work and the W3C call in number is out of service 15:45:28 ok, what is correct phone number to dial in on. 15:48:51 zakim, who is on the phone? 15:48:51 Present: jim, shawn, AWK, John, wayne, Laura, Katie, Haritos-Shea 15:49:04 +alan 15:49:29 Im in, user error, I was using the old W3C number 15:50:40 present- Haritos-Shea 15:50:43 Scribe: Laura 15:50:46 zakim, who is on the phone? 15:50:46 Present: jim, shawn, AWK, John, wayne, Laura, Katie, alan 15:50:51 topic: Ontology 15:51:05 https://github.com/w3c/low-vision-a11y-tf/issues/3 15:52:11 Wayne: Table from Texas School is inreresting. 15:52:54 Wayne: Observation functional limits come in clusters. 15:53:34 Wayne: Documenting how things work together. Completed functional limits. 15:53:47 fyi http://www.tsbvi.edu/eye-conditions 15:54:00 … could prepare a table. 15:54:28 ontology diagram - http://www.nosetothepage.org/WCAG/LVTF/Ontology/images/TopER.png 15:55:10 +1 to table 15:55:11 …We want to look at functional limits not the medical model. 15:56:04 …tracked Macular Degeneration 15:58:50 …Main barriers: Legibility, readability, Layout and Viewport Capacity 15:59:37 q+ 15:59:38 …interested in pursuing further 16:00:06 q+ 16:00:12 …has taken a lot of time. 16:00:29 ack john 16:01:10 john: ontology apply to mobile and non-mobile 16:01:23 John: Does it apply to mobile and non mobile? 16:01:36 wayne: yes and no 16:02:56 Wayne: same barriers in multiple ways. 16:03:22 John: Could you explain way finding? 16:03:44 Wayne: getting around the screen. 16:04:39 …we could change the term for location proximity issues 16:04:56 Shawn: impressed 16:05:09 ack shawn 16:05:29 Shawn: thinking about the terminology 16:06:32 Correction: John knows what wayfinding is, but wanted to know how Wayne was relating it to the ontology. Wayne explained he is using Wayfinding as an analogy. 16:06:34 Shawn: Regarding table, do we want to change the Texas table. Add a column. 16:07:01 Wayne: yes. That is the goal. 16:07:07 +1 to changing third column on http://www.tsbvi.edu/eye-conditions, IT considerations or Information Access considerations 16:08:41 Wayne: Will put updates out there. 16:09:57 Wayne: 90 percent functional limits. 16:10:47 …Certain clusters occur repeatedly. 16:11:18 s/do we want to change the Texas table. Add a column./Can we use first 2 columns - and change the last column to user interface or such? 16:11:49 Wayne: Will work on table. 16:12:25 Jim: that would be great. 16:13:10 close item 5 16:13:17 close item 6 16:13:35 ACTION: shawn look at categories in Wayne's ontology with what we have so far 16:13:35 Created ACTION-14 - Look at categories in wayne's ontology with what we have so far [on Shawn Henry - due 2015-12-16]. 16:14:14 topic: Review Perceptual Area of Overview 16:14:27 http://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Overview_of_Low_Vision#Perceptual_Area_.28Field_Loss.29 16:15:13 Jim: likes the concept of Perceptual Area 16:16:09 …Pictures are useful to illustrate 16:17:26 q+ 16:17:30 Jim: 1 question on of field loss and size limitations. 16:17:55 Wayne: think we need both. 16:19:15 q+ to say zoom & large text results in smaller amount of info.. 16:19:17 ack me 16:19:17 shawn, you wanted to say zoom & large text results in smaller amount of info.. 16:19:18 …Wayne: 2 different kinds of accommodations. 16:19:45 Shawn: More than scrolling left or right. 16:20:41 shawn: no field loss, but low acuity, then increase text size, then user has smaller viewport even if all text wraps. still have smaller viewport 16:20:46 Shawn: Issues can persist even with scrolling. 16:22:54 Wayne: under visual accuracy is limited content 16:23:03 …Perceptual areas does occur with tunnel vision. 16:23:26 wayne: add restricted viewport to clarity section 16:23:44 topic: review of Clarity in overview 16:23:56 http://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Overview_of_Low_Vision#Clarity_.28Visual_acuity.29 16:25:09 Jim: I worked on this section. Came out late last night. 16:26:17 Jim: Low vision is a continuum. 16:27:06 Wayne: This is good. 16:27:53 action: jim to add para to Clarity expanding magnification reduces perceptual area 16:27:54 Created ACTION-15 - Add para to clarity expanding magnification reduces perceptual area [on Jim Allan - due 2015-12-16]. 16:28:12 ack mi 16:28:40 inverse square relationship, as magnification goes up, perceptual area is reduced 16:32:49 I suggest that we do include info on legibility vs. readability -- I have some write up on that I'll stick in... 16:33:33 good point, Jim! 16:33:42 Jim: Functional disease has nothing to do with your numbers. 16:34:00 …may want to bring that out here. 16:35:31 Jim: functioning is separate and apart. 16:35:31 thanks for scribing, Laura! 16:35:40 visual functioning is different from disease, and acuity numbers 16:36:28 rrsagent, make minutes 16:36:28 I have made the request to generate http://www.w3.org/2015/12/09-lvtf-minutes.html laura 16:37:30 trackbot, end meeting 16:37:30 Zakim, list attendees 16:37:30 As of this point the attendees have been jim, shawn, AWK, John, wayne, Laura, Katie, Haritos-Shea, alan 16:37:38 RRSAgent, please draft minutes 16:37:38 I have made the request to generate http://www.w3.org/2015/12/09-lvtf-minutes.html trackbot 16:37:39 RRSAgent, bye 16:37:39 I see 2 open action items saved in http://www.w3.org/2015/12/09-lvtf-actions.rdf : 16:37:39 ACTION: shawn look at categories in Wayne's ontology with what we have so far [1] 16:37:39 recorded in http://www.w3.org/2015/12/09-lvtf-irc#T16-13-35 16:37:39 ACTION: jim to add para to Clarity expanding magnification reduces perceptual area [2] 16:37:39 recorded in http://www.w3.org/2015/12/09-lvtf-irc#T16-27-53