14:14:48 RRSAgent has joined #lvtf 14:14:48 logging to http://www.w3.org/2016/06/16-lvtf-irc 14:14:50 RRSAgent, make logs public 14:14:52 Zakim, this will be 14:14:52 I don't understand 'this will be', trackbot 14:14:53 Meeting: Low Vision Accessibility Task Force Teleconference 14:14:53 Date: 16 June 2016 14:15:04 Chair: Jim 14:15:37 Agenda+​ create process for proposing and revising SCs 14:15:47 zakim, agenda? 14:15:47 I see 5 items remaining on the agenda: 14:15:48 2. Section 2.5: Functional Vision https://github.com/w3c/low-vision-a11y-tf/issues/73 [from allanj] 14:15:48 3. Disclaimer draft (action-58) https://github.com/w3c/low-vision-a11y-tf/issues/67 [from allanj] 14:15:48 5. Begin working on SC - acceptance criteria (review), walk the gap analysis (proposed - WCAG needs SC before Dec 2016) [from allanj] 14:15:49 6. meeting time [from shawn-off] 14:15:49 7. ​ create process for proposing and revising SCs [from allanj] 14:16:09 zakim, clear agenda 14:16:09 agenda cleared 14:16:14 Agenda+​ create process for proposing and revising SCs 14:16:33 Agenda+​ ​review questions to ask about modifying/creating SC 14:16:43 Agenda+ review SC for User Need 3.1.2 14:18:01 regrets: laura 14:18:07 present+ 14:18:20 zakim, who is here? 14:18:20 Present: Jim, Wayne, shawn, Laura, Scott, allanj 14:18:22 On IRC I see RRSAgent, jeanne, MichaelC, shawn-bbiab, allanj, Zakim, trackbot 14:19:21 present -wayne -shawn -laura -Scott -Jim 14:19:25 zakim, who is here? 14:19:25 Present: Jim, Wayne, shawn, Laura, Scott, allanj 14:19:27 On IRC I see RRSAgent, jeanne, MichaelC, shawn-bbiab, allanj, Zakim, trackbot 14:19:43 present-wayne 14:19:52 zakim, who is here? 14:19:52 Present: Jim, shawn, Laura, Scott, allanj 14:19:54 On IRC I see RRSAgent, jeanne, MichaelC, shawn-bbiab, allanj, Zakim, trackbot 14:20:09 present- scott 14:20:19 present- Laura 14:20:23 zakim, who is here? 14:20:23 Present: Jim, shawn, allanj 14:20:25 On IRC I see RRSAgent, jeanne, MichaelC, shawn-bbiab, allanj, Zakim, trackbot 14:20:34 present- Jim 14:52:04 JohnRochford has joined #lvtf 15:00:28 laura has joined #lvtf 15:01:45 Wayne has joined #lvtf 15:05:01 ScottM has joined #lvtf 15:05:14 hats rerettable 15:06:14 ScottM_ has joined #lvtf 15:06:35 Webex problems. will try calling in via phone instead of computer. 15:06:56 s/hats rerettable/ 15:07:03 irc going nuts for me 15:08:15 Agenda? 15:08:57 zakim, open item 1 15:08:57 agendum 1. "​ create process for proposing and revising SCs" taken up [from allanj] 15:13:41 q+ 15:13:52 ack w 15:14:13 proposed process 15:14:15 ack sh 15:14:20 - create an issue for each user need 15:14:21 Jim: proposed a way to create SCs 15:14:22 - use comments for proposing and editing SCs 15:14:23 - when SC finalized update current table putting SC with all appropriate 15:14:25 user needs (same SC in multiple user needs 15:14:26 - or - 15:14:28 - create new table of SCs with all the user needs met by the SC 15:14:29 also 15:14:31 - use comments for the resolution of how we dealt with the user need 15:14:32 (defer to WCAG.next or something else) 15:15:07 see new table http://w3c.github.io/low-vision-SC/GapAnalysis-SC.html 15:17:01 sh: create issue for each proposed SC, then discussion in comments 15:17:41 sh: suggests rewording Wayne's work for proposed SC 15:18:32 proposed acceptance criteria for SC from WCAG: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Requirements_for_Success_Criteria 15:20:29 zakim, who is on the phone? 15:20:29 Present: shawn, allanj 15:20:49 present+ Laura 15:20:55 Andrew: We are workiing on what the acceptance criteria are for SC 15:21:02 present+ AWK, JohnRochford, Laura, Scott McMormack, Wayne 15:21:08 present+ Andrew 15:21:15 present+ Wayne 15:21:28 Present+ John, Scott 15:22:20 Andrew: We will be wanting TF members to be able to help engage and advocate for good wording for SC 15:24:58 AWK has joined #lvtf 15:25:04 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Requirements_for_Success_Criteria 15:25:04 Jim: Important criterion is to structure statement so answer is binary: true/false. 15:25:15 statement = SC 15:26:23 Andrew: No decisions made on phone calls, but rather via calls for consensus 15:26:52 CfC = call for Concensus 15:27:18 Andrew: There may be things we can't say because ecosystem and tools are not ready. 15:28:10 Wayne: Example = finding your place again after enlargement 15:29:19 Andrew: We will be providing "clearer" guidance that TFs can use 15:30:51 Jim: In response to Shawn, we don't need to use Wiki - we can go right to GitHub 15:31:49 zakim, close item 1 15:31:49 agendum 1, ​ create process for proposing and revising SCs, closed 15:31:50 I see 2 items remaining on the agenda; the next one is 15:31:50 2. ​ ​review questions to ask about modifying/creating SC [from allanj] 15:31:57 ​http://w3c.github.io/low-vision-SC/GapAnalysis-SC.html 15:33:00 Jim: Shawn created a new Git instance with Wayne's proposed SCs 15:33:22 s/instance with Wayne's proposed SCs/instance for SCs/ 15:33:45 ? 15:34:15 zakim, open item 2 15:34:15 agendum 2. "​ ​review questions to ask about modifying/creating SC" taken up [from allanj] 15:34:17 zakim, open item 2 15:34:17 agendum 2. "​ ​review questions to ask about modifying/creating SC" taken up [from allanj] 15:34:26 Current SC 15:34:28 1. is there a WCAG SC that meets the need? 15:34:29 2. does the SC need to be raised a level (or 2), e.g. from AAA to AA? 15:34:31 3. does the SC need modification? (modification must meet WCAG Acceptance 15:34:32 Criteria) 15:34:34 4. do we need to create a new SC? 15:34:35 New SC 15:34:37 1. Is it possible to write an SC for WCAG or do we save this need/SC for 15:34:38 WCAG.next 15:34:40 2. Is the new SC worded as a true/false statement? 15:34:41 3. Is the new SC a statement of "what is" - when the statement is true? 15:34:43 then you have met the SC. 15:36:34 Jim: One issue to consider is whether or not an SC should be deferred to WCAG Next 15:36:47 seems good to me 15:37:06 +1 15:38:32 Andrew: Can the WCAG Next consideration be step 1 of the process to create an SC? 15:39:10 + to 2 lists 15:39:22 Andrew: We could divide an SC into to lists: what we can address today and what we can address later 15:39:28 to = two 15:39:35 two lists 15:40:00 q+ 15:40:49 ack w 15:41:54 q+ to say 1. cautious about putting things off, 2. like writing what need now, even if some not do-able yet - provides info for future 15:42:20 Wayne: We could focus on the content level and content-related accessibility issues. 15:42:48 ja: we don't have to totally defer to 3.0, can make minor modifications for 2.1, then in 3.0 do it totally. 15:45:30 Andrew: We should focus on end-user needs and what is achievable by authors, and not be constrained by current-technology limitations. 15:45:52 It seems likely that 80% or what we need for customization is possible with HTML. If others can only support 20% of this can we call these accessible, or should we simply declare that an accessible alternative should be used. 15:46:00 ack me 15:46:00 shawn, you wanted to say 1. cautious about putting things off, 2. like writing what need now, even if some not do-able yet - provides info for future 15:48:20 Wayne: Developers use unneccessary techniques to structure a page, for example, that interfere with accessibility. 15:48:22 We need to make sure our efforts don't end up AAA 15:49:00 +1 scott 15:49:18 +1 Scott 15:49:34 +1 15:50:03 Shawn: We could write up stuff we can't do now but can do later. 15:50:09 zakim, make minutes 15:50:09 I don't understand 'make minutes', allanj 15:50:20 rrsagent, make minutes 15:50:20 I have made the request to generate http://www.w3.org/2016/06/16-lvtf-minutes.html allanj 15:51:22 +1 to 2-lists idea 15:52:49 Question for Jim: should I still scribe given it looks to me that you just generated the minutes? 15:53:34 s/Question for Jim: should I still scribe given it looks to me that you just generated the minutes?/ 15:53:40 s/We could write up stuff we can't do now but can do later./ 15:54:38 scribe: Laura 15:55:10 zakuim, open item 3 15:55:34 Zakim, open item 3 15:55:34 agendum 3. "review SC for User Need 3.1.2" taken up [from allanj] 15:55:46 https://github.com/w3c/low-vision-SC/issues/2 15:55:47 https://w3c.github.io/low-vision-SC/GapAnalysis-SC.html 15:57:41 be right there 15:58:30 s/be right there/ 15:58:58 q+ 15:59:39 Shawn: Thinks this is less than we want. 16:00:57 Jim: Attacking piece meal. then we can merge. 16:03:56 Jim: is wording okay? 16:04:25 wayne: can wordsmith on second pass 16:05:49 ja: is 200% sacrosanct or open to change 16:06:08 AWK: can increase requirement but not decrease it. 16:11:41 can we change to /at least/ 200% 16:12:40 increase to the limits of browser zoom 16:13:13 wayne: 4 or 500%, technology can do this. 16:13:24 wayne: 400 or 500% is achievable 16:14:40 +1 16:14:53 +1 to scott 16:15:41 Jim: propose increase to the level of browser zoom. 16:17:03 wayne: g legge recommended 1100 percent 16:18:13 minimum characters on page in order to read is 5, or user can't remember what they read 16:18:16 LC: if we can document it. Let’s go with 1000% 16:20:11 current: Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. 16:20:44 wayne: pages have to be re-organizable. 16:21:31 shawn: uni-directional scrolling, not horizontal or vertical. and need to define uni-directional 16:22:23 proposed: Text can be resized without assistive technology up to 1100 percent in a way that does not require bi-directional scrolling to read a line of text on a full-screen window. 16:22:45 +1 16:22:54 +1 16:23:08 Jim will find research to cite for this 16:24:31 shawn: keep hear developers say meeting 200% is the hardest SC to meet. 16:25:08 ... need to make it clear in the Understanding doc, that you need reflow, rewrap, single column 16:25:26 Shawn: we will make to make it clear in the understanding doc about reflow etc. 16:26:02 Psychophysics of reading--I. Normal vision. Legge GE, Pelli DG, Rubin GS, Schleske MM Vision Res. 1985; 25(2):239-52. 16:26:32 Effects of Word Width and Word Length on Optimal Character Size for Reading of Horizontally Scrolling Japanese Words http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4754429/ 16:27:42 Shawn: we have the research page 16:27:46 add these to general research page, and include in the SC, pull direct quote with citation 16:29:39 Shawn: separate issues for each bullet. 16:30:40 Jim: have a good weekend folks 16:30:58 rrsagent, make minutes 16:30:58 I have made the request to generate http://www.w3.org/2016/06/16-lvtf-minutes.html laura 16:31:08 tackbot, end meeting 16:31:15 trackbot, end meeting 16:31:15 Zakim, list attendees 16:31:15 As of this point the attendees have been Jim, Wayne, shawn, Laura, Scott, allanj, AWK, JohnRochford, McMormack, Andrew 16:31:23 RRSAgent, please draft minutes 16:31:23 I have made the request to generate http://www.w3.org/2016/06/16-lvtf-minutes.html trackbot 16:31:24 RRSAgent, bye 16:31:24 I see no action items