14:59:13 RRSAgent has joined #lvtf 14:59:13 logging to http://www.w3.org/2016/09/29-lvtf-irc 14:59:15 RRSAgent, make logs public 14:59:15 Zakim has joined #lvtf 14:59:17 Zakim, this will be 14:59:17 I don't understand 'this will be', trackbot 14:59:18 Meeting: Low Vision Accessibility Task Force Teleconference 14:59:18 Date: 29 September 2016 14:59:25 Chair: AWK 14:59:30 Regrets: JimA 14:59:53 alastairc has joined #lvtf 14:59:59 ScottM has joined #lvtf 15:02:15 ah, thanks 15:02:24 AWK_ has joined #lvtf 15:03:40 s/ah, thanks// 15:03:42 zakim, who is on the call? 15:03:42 Present: (no one) 15:03:45 +AWK 15:03:54 regrets+ jallan 15:03:57 Chair: AWK 15:04:07 present+ Shawn, Alastair, ScottM, Wayne 15:04:10 Agenda+​ review TPAC minutes https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Sep/0060.html https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Sep/0062.html 15:04:19 Agenda+ Deadline for proposing NEW SCs Nov 4 15:04:28 Agenda+ Any Proposals for DEFERRING browser specific SCs from current SC list https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page 15:05:50 Wayne has joined #lvtf 15:06:49 present+ Laura 15:07:03 present+ alastairc 15:07:05 + Laura 15:07:11 present+ Wayne 15:07:38 Scribe: Laura 15:07:50 Zakim, take up item 1 15:07:50 agendum 1. "​ review TPAC minutes https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Sep/0060.html 15:07:52 ... https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Sep/0062.html" taken up [from AWK_] 15:09:08 AWK: Some people called into TPAC. It can be challenging. 15:09:23 …did people review the minutes? 15:09:29 Wayne: yes. 15:10:08 …We were not making user agent requests in any of our SCs. 15:10:25 …for example, Size. 15:10:47 …I thought we were really clear. 15:11:15 …Glad I didn’t attend. Disappointing. 15:11:21 q+ 15:11:44 …Don't be disheartened. We will need to educate. 15:12:01 AWK: …Don't be disheartened. We will need to educate. 15:12:05 q+ 15:12:16 q- last 15:12:32 …it is going to be challenging. 15:12:55 Wayne: I understand. 15:13:03 q- later 15:13:16 ack al 15:13:39 AC: Sent an email to the list. 15:14:28 …has reviwed SCs. Some SCs can be done now. 15:14:36 q+ 15:14:44 …some SCs appear to be achievable in browsers now. 15:15:03 …some SCs appear to require user-agent functionality. 15:15:20 …some may be a huge burden. 15:15:38 q- 15:15:58 https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Sep/0063.html 15:16:07 ack shawn 15:16:43 Shawn: don’t be disheartened yet. 15:17:38 s/don’t be disheartened yet./agree with Andrew. don’t be disheartened yet -- I think it was a positive tone overall. 15:17:55 q+ 15:18:42 AWK: When we submit an sc we may need to be more basic. and just present the problem. 15:18:53 …need to move the needle forward. 15:19:31 ack wa 15:19:39 q+ to say very cautious about "not WCAAG 2.1, will do later" 15:20:24 wayne: we have to make clear that we want to remove obstructions. 15:21:00 …screen magnifiers can't solve the problem. 15:21:07 ack shawn 15:21:07 shawn, you wanted to say very cautious about "not WCAAG 2.1, will do later" 15:21:11 q+ 15:21:53 Shawn: cautious when I hear something won't get in 2.1 15:21:54 ack ala 15:22:31 AWK: User Agents are not part of 2.1 15:23:02 s/cautious when I hear something won't get in 2.1/cautious when I hear something won't get in 2.1. that may be all there is in some cases for many years. agree not to "cover" user agents. however, "a mechanism is available" is appropriate in many cases 15:23:15 AC: May need to rephrase some SCs so they are not about User Agents 15:23:18 q+ 15:24:32 Shawn: If using standard HTML you are covered. If not need to provide a mechanism. 15:24:34 ack w 15:25:29 Wayne: SCs need to be stated in a positve way. Can be difficult. 15:26:10 …content developers need to make there content available. 15:26:30 …may need an alternative format. 15:26:40 AC: example? 15:27:31 …non-html environment. 15:28:12 AWK: a lot of discussion on personalization at TPAC. 15:28:15 s/covered. If not need to provide a mechanism./covered by browser functionality. For other technology, if not in the user agents, then you need to provide a mechanism. 15:29:03 +1 to figuring out a way to minimize # of new SCs! and coordinating personalization between COGA & LVTF & others 15:29:22 AWK: Number of SC was a topic. Not worried about it. 15:30:01 …we will work it out. 15:30:28 Zakim, close item 1 15:30:28 agendum 1, ​ review TPAC minutes https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Sep/0060.html 15:30:30 ... https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Sep/0062.html, closed 15:30:30 I see 2 items remaining on the agenda; the next one is 15:30:30 2. Deadline for proposing NEW SCs Nov 4 [from AWK_] 15:30:42 Zakim, take up item 2 15:30:42 agendum 2. "Deadline for proposing NEW SCs Nov 4" taken up [from AWK_] 15:31:41 timeline https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Time_Line!! 15:32:08 Shawn: Jim was trying to set stakes in the ground. 15:32:47 AWK: Dec 1 have everything done. 15:33:32 AWK: we have 7 thursdays left not counting Thanksgiving. 15:33:46 …we will stat running out of time. 15:34:12 …anything new should be started before Nov 1. 15:34:33 Wayne: are we ready for a freeze? 15:34:38 q+ 15:34:43 AWK: not me 15:34:58 ack al 15:35:20 Wayne: not comfortable. but we have covered essentials 15:35:27 zakim, agenda? 15:35:27 I see 2 items remaining on the agenda: 15:35:28 2. Deadline for proposing NEW SCs Nov 4 [from AWK_] 15:35:28 3. Any Proposals for DEFERRING browser specific SCs from current SC list https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page [from AWK_] 15:35:41 AC: not yet. may want to condense. 15:35:51 agenda+ Alastair questions :-) 15:35:52 Zakim, close item 2 15:35:52 agendum 2, Deadline for proposing NEW SCs Nov 4, closed 15:35:53 I see 2 items remaining on the agenda; the next one is 15:35:53 3. Any Proposals for DEFERRING browser specific SCs from current SC list https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page [from AWK_] 15:35:57 …would like to ask questions at end of agenda. 15:35:58 Zakim, take up item 3 15:35:58 agendum 3. "Any Proposals for DEFERRING browser specific SCs from current SC list https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page" taken up [from AWK_] 15:38:08 AWK: Jim suggested some may be browser specific SCs. 15:38:20 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Tracking_Success_Criteria_Progress 15:40:32 Content picks up all relevant user settings, such as ... 15:40:43 Shawn: feels like content. 15:40:56 awk: how would you do this? 15:41:22 Shawn: I don’t know. 15:41:38 Wayne: Will check it out this week. 15:42:08 awk: how would an author conform or not conform? 15:42:17 q+ 15:42:52 wayne: are there any of ouside the scope? 15:43:18 ack a 15:43:22 …may not need this one. 15:44:39 AC: nothing for an author to do. Already done by the user agent or may be customisation 15:45:05 Shawn: so maybe if all the important elements are covered by our the SC, then don't need this as a separate SC 15:45:25 s/our the SC/our other SC 15:45:25 AWK: no SC text for this one. 15:46:38 wayne: postioning can be a problem. 15:46:38 Shawn: general comment: I think just because something is already done in HTML & browsers, doesn't mean we shouldn't include it -- esp. considering non-html content 15:46:55 awk: we have an sc for that. 15:47:22 Definitely agree with that comment Shawn. 15:47:34 [choosing high contrast option in OS is a good example to think about] 15:47:36 Windows High Contrast removes all background images as does printing by default 15:47:49 wayne: background images are a problem. Breaks pages. 15:48:13 q+ 15:48:57 AC: I think windows 10 has fixed HCM and background images. 15:49:13 ack s 15:49:28 wayne: content needs to be flexible. 15:50:17 thanks to Wayne for working more on this! 15:50:18 awk: let this one set for a bit. 15:50:47 AC: maybe a repsect user settings SCs. 15:52:05 AWK: Element Level Customization may be another one. 15:52:25 SC: why is is separtate? 15:53:04 wayne: Programing perspective at the parse level. They can be identified. 15:53:16 +1 for looking at consolidating. issue is overall for blocks of text, vs. *element-level* 15:53:38 …size can be a poor indicator for low vision. 15:55:17 …we authors should use proper semantics. 15:56:42 AC: strengthening 1.3.1 15:57:15 AWK: need to be more specific 15:57:22 Shawn: again, good HTML already does this. We still need to say: content is provided in a way that users can do element-level customization 15:58:05 …for instance controls in Flash. 15:58:26 s/…for/AWK: …for 15:58:35 rrsagent, draft minutes 15:58:35 I have made the request to generate http://www.w3.org/2016/09/29-lvtf-minutes.html shawn 15:58:48 …enable this in a technolgy independed way. 15:59:58 s/enable this in a technolgy independed way./AWK: enable this in a technology independent way. 16:00:33 agree with AWK, that in some cases the accessibility support may not be available 16:01:09 AWK: in some cases the accessibility support may not be available 16:02:09 Shawn: content enables users to do this. 16:02:30 q+ 16:03:01 q+ to say a big thing that we need to make clear is that some of these are already coverd in html 16:03:02 awk: this is not a UA SC 16:03:03 ack m 16:03:03 ack s 16:03:03 shawn, you wanted to say a big thing that we need to make clear is that some of these are already coverd in html 16:03:38 shawn: need to make clear it you are doing html you are covered. 16:04:40 AWK: SVG, PDF, epub needs to consideration. 16:05:15 …how you accomplish these things today. 16:05:42 AWK: Let’s talk about the printing one. 16:06:05 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Printing_Customized_Text 16:06:33 shawn: exactly like the last one. 16:06:58 AC: print style sheets come into play. 16:07:44 shawn: an issue of accessibility support. 16:08:21 AC: may not work with print style sheets. 16:08:44 …may be able to come up with techniques. 16:10:18 ScottM has joined #lvtf 16:10:31 Not all browsers support print selection 16:10:32 …see need for an SC. Mostly coved in HTML. 16:10:53 Scott, unfortunately not, agree 16:11:08 wayne: overriding issue is structure of HTML 16:12:21 wayne: there is a matching issue. 16:13:12 awk: Current SC Text “A mechanism is available to allow users to print page content that matches page presentation changes made by the user. “ 16:13:54 A mechanism is available to allow users to print page content with the page presentation changes made by the user. 16:13:55 AC: Allow users to print the page with the changes the user has made to the page 16:14:11 AC: mechanism is available to allow users to print page content with the page presentation changes made by the user. 16:14:31 Shawn: updated wiki. 16:14:46 zakim, agenda? 16:14:46 I see 2 items remaining on the agenda: 16:14:47 3. Any Proposals for DEFERRING browser specific SCs from current SC list https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page [from AWK_] 16:14:47 4. Alastair questions :-) [from shawn] 16:15:55 AWK: do people know what they should be working on? 16:16:30 …we need to do 4 a week. 16:16:35 To review next week: 16:16:43 reflow to single column 16:16:48 element level customization 16:17:31 Printing customized text 16:17:37 and one more TBD 16:18:00 Laura will work on a contrast or interface elements ones. 16:19:24 AC: What is the thinking behind separate SCs for size of all content and text size SCs? 16:19:57 https://www.w3.org/WAI/GL/wiki/Possible_wording_from_Jason/David_for_LVTF_re:_zoom_without_horizontal_scroll#Version_4 16:20:22 Wayne: because reading is a huge problem to people with low vision. 16:21:07 AC: is horizonal scrolling a issue. 16:21:18 Wayne: yes. 16:22:11 AC: worked on a wiki page that may cover for size of all content and text size. 16:22:48 q+ 16:22:51 …should be able to combine. 16:23:01 wayne: will take a look. 16:23:47 q+ to comment on large images 16:23:53 AC: does reflow need to act independently? 16:23:57 q+ to sat replow cognitive & screen mag 16:24:41 wayne: it is very easy for some users to lose content. 16:25:20 https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Reflow_to_Single_Column 16:25:41 ack me 16:25:41 shawn, you wanted to comment on large images and to sat replow cognitive & screen mag 16:26:07 q+ 16:26:08 wayne: people with tunnel vision can have problems. 16:26:21 ack s 16:26:31 shawn: there are use cases for reflow. 16:27:25 shawn: both text size and zoom can be useful. 16:27:57 …text size is more useful. 16:28:55 AC: easier with zoom for developers. 16:29:34 …media queries handles reflow. But everything zooms. 16:30:17 …ems can be used for media queries. 16:30:38 q+ 16:30:56 ack sc 16:30:59 …but still need to reflow at some stage. 16:31:56 Scott: white space can be problematic with reflow with screen magnification. 16:32:09 …tables are an isssue. 16:32:57 wayne: we need to talk about style sheets . 16:33:32 …ways to write AT style sheets. 16:34:58 AWK: Not sure if I will be here next week. Could have a working session. 16:35:19 AC: we would have plenty to talk about. 16:35:44 Shawn: I will be around. And can start WebEx. 16:36:22 AWK: Thanks all. 16:36:51 rrsagent, list participants 16:36:51 I'm logging. I don't understand 'list participants', AWK_. Try /msg RRSAgent help 16:37:00 rrsagent, make minutes 16:37:00 I have made the request to generate http://www.w3.org/2016/09/29-lvtf-minutes.html laura 16:37:06 trackbot, list participants 16:37:06 Sorry, AWK_, I don't understand 'trackbot, list participants'. Please refer to for help. 16:37:53 present+ AWK 16:38:04 rrsagent, make minutes 16:38:04 I have made the request to generate http://www.w3.org/2016/09/29-lvtf-minutes.html laura 16:38:46 zakim, list participants 16:38:46 As of this point the attendees have been AWK, Shawn, Alastair, ScottM, Wayne, Laura, alastairc 16:39:21 trackbot, end meeting 16:39:21 Zakim, list attendees 16:39:21 As of this point the attendees have been AWK, Shawn, Alastair, ScottM, Wayne, Laura, alastairc 16:39:29 RRSAgent, please draft minutes 16:39:29 I have made the request to generate http://www.w3.org/2016/09/29-lvtf-minutes.html trackbot 16:39:30 RRSAgent, bye 16:39:30 I see no action items