14:06:35 RRSAgent has joined #lvtf 14:06:35 logging to http://www.w3.org/2015/10/28-lvtf-irc 14:06:37 RRSAgent, make logs public 14:06:37 Zakim has joined #lvtf 14:06:39 Zakim, this will be 14:06:39 I don't understand 'this will be', trackbot 14:06:40 Meeting: Low Vision Accessibility Task Force Teleconference 14:06:40 Date: 28 October 2015 14:07:12 rrsagent, set logs public 14:07:20 rrsagent, make minutes 14:07:20 I have made the request to generate http://www.w3.org/2015/10/28-lvtf-minutes.html allanj 14:07:47 chair: Jim and Andrew 14:08:01 present+ 14:09:13 Agenda+ scribe 14:09:15 Agenda+ report on User Stories clean up 14:09:16 "User Stories" morphed into succinct "User issues"/"User experience problems" 14:09:18 Agenda+ report on Wayne Ontology 14:09:19 Agenda+ discuss Work_topics and User_Stories overlap 14:09:36 jeanne has left #lvtf 14:10:18 agenda+ Low Vision User Requirements 14:12:37 laura has joined #lvtf 14:17:47 shawn has joined #lvtf 14:18:27 shawn has changed the topic to: 14:19:25 shawn has changed the topic to: WebEx (*new*) https://mit.webex.com/mit/j.php?MTID=m2486867b0c5117ca58dffc7aee66ca29 password: lvtfnow 14:25:29 trackbot, start meeting 14:25:31 RRSAgent, make logs public 14:25:33 Zakim, this will be 14:25:33 I don't understand 'this will be', trackbot 14:25:34 Meeting: Low Vision Accessibility Task Force Teleconference 14:25:34 Date: 28 October 2015 14:25:37 zakim, clear agenda 14:25:37 agenda cleared 14:25:42 present: 14:26:40 present+ Shawn 14:27:53 present+ Bruce 14:27:57 present+ Andrew 14:30:39 Agenda+ scribe 14:30:40 Agenda+ report on User Stories clean up 14:30:42 "User Stories" morphed into succinct "User issues"/"User experience problems" 14:30:43 Agenda+ report on Wayne Ontology 14:30:45 Agenda+ discuss Work_topics and User_Stories overlap 14:31:01 agenda+ low vision requirements 14:31:04 Bruce_Bailey has joined #lvtf 14:31:41 Present+ Alan 14:31:45 Present+ Jim 14:32:06 Present+ Bruce_Bailey 14:32:23 Present+ Charles 14:32:31 Present+ Laura 14:33:23 ChuckOp has joined #lvtf 14:33:36 scrib: chuckop 14:33:45 scribe: chuckop 14:34:00 close item 1 14:34:24 AWK has joined #lvtf 14:34:37 present+ Jon 14:35:35 +AWK 14:35:59 take up next item 14:36:19 Present- Charles 14:36:25 Present+ Chuck 14:36:42 present+ Wayne 14:37:36 Discussing this page: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/User_stories_-_use_cases 14:37:47 Jim did clean up on the user stories use cases page 14:38:11 q+ to ask about UC cites 14:38:46 Jim encourages others to clean up, add to, and generally improve the use cases 14:39:15 Allan also did some additions 14:39:27 Bruce notes that the use cases are looking better 14:39:29 ack bruce 14:39:29 Bruce_Bailey, you wanted to ask about UC cites 14:39:42 Wayne has joined #LVTF 14:40:02 q- 14:41:21 take up next item 14:41:45 wayne+ 14:41:47 present+ Erich 14:41:50 close item 2 14:41:52 present+ Erich 14:42:07 Erich has joined #lvtf 14:42:24 ontology http://nosetothepage.org/WCAG/LVEffects_files/Dictionary.html 14:43:28 Wayne: Created ontology/dictionary page located at http://nosetothepage.org/WCAG/LVEffects_files/Dictionary.html 14:44:51 Wayne: symptoms fall into two categories 14:45:54 jon_avila has joined #lvtf 14:46:24 q+ 14:47:06 Wayne: our use cases will turn into our lists (of requirements? of tasks?) 14:47:11 ack jon 14:47:39 John: preference is not to focus not on medical model of low vision, but rather on the functional barriers. 14:47:59 John: the problem isn't the condition, but that the content isn't adaptable 14:48:04 + 1 to content & tools is the problem, not the user 14:48:55 Wayne: general agreement 14:49:11 q+ 14:49:25 q- 14:49:29 Jon: Preference to ensure our wiki and notes reflect the functional barriers 14:49:36 +1 user is not the problem 14:50:22 +1 to medical model OK in wiki for data analysis but not in final docs 14:50:25 ack awk 14:50:48 great 14:50:50 Andrew: Our intent is to have an appendix that references medical terminology to help with mapping 14:51:17 Andrew: Not to focus on the medical diagnoses 14:51:27 thanks 14:51:47 Yes, the info is very good. 14:52:08 Laura: the appendix and mapping can be very useful 14:52:33 jim: thanks wayne for his work and encourages others to contribute to it. 14:52:35 agenda? 14:53:02 close item 3 14:53:28 Shawn: Thinks ChuckOp is best scribe evah! 14:54:36 Jim: Shawn did amazing work on Low Vision requirements and would like to discuss that now 14:54:41 take up item 5 14:54:43 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Low_Vision_User_Requirements 14:57:38 Shawn: What if we started presenting actual user requirements? Went through use cases and started translating them into requirements with categories, with handles and notes. 14:58:02 Shawn: First pass, not polished, use as a starting point 14:58:55 Jim: Was reading the requirements, calls it an amazing amount of work. 14:59:43 Jim: We can edit and add to the requirements since it is in a wiki 15:00:07 Shawn: Notes difficulty of editing and using wiki markup 15:00:38 Yes, great stuff! 15:01:27 Excellent work, Shawn. 15:01:53 I wonder if it would help to mark some of these as scoped to authored content or user agent 15:02:10 Jim: Shawn, how did you come up with categories? 15:02:44 Shawn's TAdER work - http://www.tader.info/index.html 15:02:58 (Text Adaptability is Essential for Reading) 15:03:07 Shawn: I added some categories based on information in the use cases and user stories. Wondered about organizing according to the high level overview, might need sub-categories. 15:04:14 Shawn: Categories are a bucketing system, Handle is a one-word (ideally) title. 15:04:32 I prefer table 15:04:37 Shawn: What's better; tables or paragraphs? 15:04:46 Jim: I like the table 15:06:51 Discussion between Jim and Shawn regarding wording of "user can..." 15:07:54 q+ 15:09:16 ack w 15:09:17 looking at "Related information is in close proximity. " or "user can choose to have related information in close proximity to viewport" 15:09:34 content developer vs browser developer 15:09:34 Wayne: We have reps from WAI UA and CA groups. We need to separate 15:09:36 q+ 15:09:53 Jon: Some of these can be both. Content zooming for example. 15:09:54 s/CA/GL 15:09:58 Shawn: Good point 15:10:10 Thanks Allan 15:11:02 shawn: Say what users need...then say what content folks can do, and what browser folks can do 15:13:08 what the content authors or browsers do are solutions to user needs 15:13:37 + 1 Focus: User needs!! 15:13:46 Shawn: Eventually we need to do the breakout that Jim references, but not to do it too early. Focus on getting the first draft out first (of user requirements) 15:16:01 Shawn: The work that everyone did (Jim, et al) on use cases really helped in drafting requirements. 15:16:39 q+ 15:16:49 it takes a working group... 15:17:13 ack shawn 15:17:29 ack jon 15:17:34 Shawn asking about " Icon fonts that when combined with custom fonts are browser/AT combinations like ZoomText and Firefox change to squares and are unrecognizable." 15:19:31 Bruce asked about "WingDings" but Andrew says situation can be more complex than that. 15:20:10 Jon: discussion of symbol fonts and availability of fonts when working with low vision tools 15:20:42 [ eowg tried using icons fonts and gave up and used SVG ] 15:20:48 Of interest for icon fonts: https://www.filamentgroup.com/lab/bulletproof_icon_fonts.html 15:21:40 Jon: ARIA labels can be used to provide textual context to symbols 15:22:11 ?: Not easily accessible to keyboard users 15:22:38 Bruce thanks Andrew for the example. Here is one that might be related: https://css-tricks.com/examples/IconFont/ 15:23:04 Jim: How would names/description be made available for symbol-based characters 15:23:33 Andrew: Other user groups can benefit from icon-based fonts 15:24:05 s/ [ eowg tried using icons fonts and gave up and used SVG ]/ 15:25:18 wayne: high contrast icon font available? 15:26:01 q+ 15:26:07 ack me 15:26:11 q? 15:26:41 Shawn: One of the issues: if we mess up and overlap editing can be problematic. 15:27:00 Jim: Should we do editing over the mailing list and send issues to Shawn for editing? 15:27:20 Shawn: Is okay with being the primary editor for the time being. 15:27:54 Jim: Send issues and discussion to the mailing list, and Shawn will incorporate into the user requirements page 15:28:04 Jim: Really excited and thanks Shawn 15:28:09 Thanks everyone. 15:28:16 good team work, folks! 15:31:04 rrsagent, make minutes 15:31:04 I have made the request to generate http://www.w3.org/2015/10/28-lvtf-minutes.html allanj 15:31:47 zakim, please part 15:31:47 leaving. As of this point the attendees have been Shawn, Bruce, Andrew, Alan, Jim, Bruce_Bailey, Charles, Laura, Jon, AWK, Chuck, Wayne, Erich 15:31:47 Zakim has left #lvtf 15:31:52 rrsagent, make minutes 15:31:52 I have made the request to generate http://www.w3.org/2015/10/28-lvtf-minutes.html allanj 15:32:05 rrsagent, please part 15:32:05 I see no action items