14:48:58 RRSAgent has joined #ag 14:48:58 logging to http://www.w3.org/2017/04/11-ag-irc 14:49:00 RRSAgent, make logs public 14:49:03 Zakim, this will be WAI_WCAG 14:49:03 ok, trackbot 14:49:03 Meeting: Accessibility Guidelines Working Group Teleconference 14:49:03 Date: 11 April 2017 14:49:16 Zakim, agenda? 14:49:16 I see 2 items remaining on the agenda: 14:49:17 3. Adapting Text [from Joshue108] 14:49:17 4. Accidental activation [from Joshue108] 14:49:55 interaccess has joined #ag 14:50:00 zakim, clear agenda 14:50:00 agenda cleared 14:50:05 trackbot, start meeting 14:50:08 RRSAgent, make logs public 14:50:11 Zakim, this will be WAI_WCAG 14:50:11 Meeting: Accessibility Guidelines Working Group Teleconference 14:50:11 Date: 11 April 2017 14:50:11 ok, trackbot 14:50:12 agenda+ WCAG 2.1 progress/expectation/pace - brief discussion 14:50:18 marcjohlic has joined #ag 14:50:23 agenda+ New techniques work 14:50:30 marcjohlic has joined #ag 14:50:33 agenda+ Three new SC to review - https://www.w3.org/2002/09/wbs/35422/SCs_April_11/ 14:50:45 agenda+ Thursday call agenda items 14:50:58 agenda+ TPAC F2F 14:51:12 Chair: Joshue 14:51:13 zakim, agenda order is 5,1,2,3,4 14:51:13 ok, AWK 14:52:51 regrets+ Mike_Elledge, EA_draffan, Rachael, Neil_Milliken, Denis_Boudreau, Jim_Smith 14:53:15 laura has joined #ag 14:53:18 Scribe: Kathy 14:53:43 Next week's Scribe is Laura. 14:53:48 present+ 14:54:07 zakim, who is on the phone? 14:54:07 Present: Greg_Lowney, MichaelC, Glenda, Laura, jasonjgw, david-macdonald, Joshue108, steverep, ScottM, JF, erich, Shawn, Katie_Haritos-Shea, kirkwood, KimD 14:54:30 Present: jasonjgw 14:54:35 +AWK 14:54:37 zakim, who is on the phone? 14:54:37 Present: jasonjgw, AWK 14:55:36 Jake has joined #ag 14:55:57 MelanieP has joined #ag 14:57:28 Kathy has joined #ag 14:57:41 present+ Kathy 14:58:12 present+ 14:58:51 present+ Joshue108 14:59:02 KimD has joined #ag 15:00:26 scribe: Kathy 15:00:43 adaml has joined #ag 15:01:06 Present+ KimD 15:01:19 prsent+ kirkwood 15:01:33 Makoto has joined #ag 15:01:39 present+ Laura 15:01:41 JF has joined #ag 15:01:48 Lauriat has joined #ag 15:01:52 present+ JF 15:01:55 present+ kirkwood 15:01:55 present+ Makoto 15:01:56 Present+ Lauriat 15:02:07 bruce_bailey has joined #ag 15:02:11 present+ adam_lund 15:02:20 present+ Melanie_Philipp 15:02:33 present+ bruce-bailey 15:02:38 Glenda has joined #ag 15:02:39 zakim, agenda? 15:02:39 I see 5 items remaining on the agenda: 15:02:40 5. TPAC F2F [from AWK] 15:02:40 1. WCAG 2.1 progress/expectation/pace - brief discussion [from AWK] 15:02:40 2. New techniques work [from AWK] 15:02:40 3. Three new SC to review - https://www.w3.org/2002/09/wbs/35422/SCs_April_11/ [from AWK] 15:02:40 4. Thursday call agenda items [from AWK] 15:03:00 present+ jasonjgw 15:03:19 gowerm has joined #ag 15:04:12 zakim, who is on the phone? 15:04:12 Present: jasonjgw, AWK, Kathy, allanj, Joshue108, KimD, Laura, JF, kirkwood, Makoto, Lauriat, adam_lund, Melanie_Philipp, bruce-bailey 15:04:33 present+ MikeGower 15:04:53 Josh - new member Chris 15:04:59 david-macdonald has joined #ag 15:05:04 steverep has joined #ag 15:05:18 present+steverep 15:05:19 present+ Glenda 15:05:50 present+ 15:05:54 Jake has joined #ag 15:06:11 present +david-macdonald 15:06:30 zakim, who's here? 15:06:30 Present: jasonjgw, AWK, Kathy, allanj, Joshue108, KimD, Laura, JF, kirkwood, Makoto, Lauriat, adam_lund, Melanie_Philipp, bruce-bailey, MikeGower, steverep, Glenda, MichaelC 15:06:33 On IRC I see Jake, steverep, david-macdonald, gowerm, Glenda, bruce_bailey, Lauriat, JF, Makoto, adaml, KimD, Kathy, MelanieP, laura, marcjohlic, Joshue108, RRSAgent, AWK, jeanne, 15:06:33 ... allanj, kirkwood, MichaelC, jasonjgw, Zakim, yatil, csarven, trackbot 15:06:37 Wilco has joined #ag 15:07:01 Greg has joined #ag 15:07:12 Can you post a link on how to sign up for scribing? 15:07:26 present+ Greg_Lowney 15:07:40 https://www.w3.org/WAI/GL/wiki/Scribe_List 15:07:43 Scribing Commands and Related Info: https://www.w3.org/WAI/GL/wiki/Scribing_Commands_and_Related_Info 15:07:50 another new member Jake 15:08:13 ChrisLoiselle has joined #AG 15:08:20 present+ marcjohlic 15:09:30 present+ jeanne 15:10:19 zakim, take up next 15:10:19 agendum 5. "TPAC F2F" taken up [from AWK] 15:10:33 https://www.w3.org/2002/09/wbs/35422/AGWG_TPAC2017/ 15:10:33 q+ 15:10:37 Josh: we will have a meeting at TPAC 15:10:45 held in November 15:11:02 in California 15:11:09 JF => http://www.pepemilan.com/resize.php?imagen=galeria/articulos/modelo-z614-horma-cuba-toga-snake-metal-azul-par_180_5.jpg&ancho=1500&alto=1065 15:11:13 there will also be remote participation 15:11:25 we need to figure out the preference for days 15:12:30 q+ 15:12:33 Wayne has joined #ag 15:12:41 alot of people said they only want 2 days - then we need to figure out the days 15:12:42 Ryladog has joined #ag 15:12:55 ack awk 15:12:57 Present+ Katie_Haritos-Shea 15:13:10 Andrew - we have taskforces that want to meet 15:13:15 Present+ Wayne 15:13:26 Michael - there can be separate meetings for the taskforces 15:14:23 Michael - there will be conflicts so we should schedule what is needed 15:14:43 q+ 15:14:50 Andrew - we may not have control over what days we will have 15:15:42 ack r 15:16:21 Katie - the other groups have not decided on the days, should not use the Wed for meetings 15:16:39 Michael - Wed is a good day to learn more about what is happening 15:16:51 Proposed resolution: WCAG will meet at TPAC, days TBD. 15:17:41 Resolution: AG meeting will be happening at TPAC 15:18:05 What is the host hotel? 15:18:14 Michael - recommend booking hotels nwo 15:18:24 -> https://www.w3.org/2017/11/TPAC/ TPAC 2017 15:19:24 link is not working 15:20:30 jamesn has joined #ag 15:20:48 rrsagent, make minutes 15:20:48 I have made the request to generate http://www.w3.org/2017/04/11-ag-minutes.html jamesn 15:20:53 zakim, take up next 15:20:53 agendum 1. "WCAG 2.1 progress/expectation/pace - brief discussion" taken up [from AWK] 15:21:22 present+ 15:22:10 Josh - been through a lot and wanted to talk through peoples concerns 15:23:00 wanted to talk about managing expectations 15:23:29 q+ 15:24:07 q+ 15:25:05 Andrew - know there are concerns about the pace and how we are going to get through all 55 SC. The work we are doing is ongoing. It is challenging to find solutions for all good ideas. We need to be practical and identify the failings in the language. If we put it out without the appropriate language it will get a lot of comments and potential of being rejected. This is hard 15:25:19 Q+ 15:25:47 we don't know how many we will get completed. Good to have a few that are implementable and testable 15:25:57 ack ry 15:26:59 q+ 15:27:13 ack me 15:27:16 Katie - keep in mind there is a monthly release. Not surprised that we got comments. We will experience burn out if we are releasing too frequently. What ever that means... 4, 5, 6 months to get good comments 15:27:31 q+ to ask where outsider comments are posted 15:27:44 big +1 to Katie 15:28:07 Josh - want us to all manage the work at a good sustainable pace. People are feeling pressure and we need to work at what we can do 15:28:21 this is a .1 release and there may be another version 15:28:24 nominally, 2.1 comment are here: http://lists.w3.org/Archives/Public/public-agwg-comments/ 15:28:30 ack Jf 15:28:31 but that is not the full set... 15:28:49 +1 to watching our own nervous systems and mental health 15:29:01 +1 to taking a reasonable pace and quality being "job 1" 15:29:01 John - earlier this year at CSUN there were conversations that we may want to publish what we have at the readiness of where we are at 15:29:28 we have a lot of good proposals and research. There is alot of documentation that is scattered about 15:29:45 we may want to publish it but state where it is at 15:29:57 +1 to John on publishing as is 15:30:20 Josh - there was a thread about this. W3C looks for cutting edge. We could publish as non-normative 15:30:22 ack wayne 15:31:10 q+ to say that WCAG is not setting national law 15:31:10 Wayne - I am worried about legal responsibility. We become national law. The impression we give is that we meet the needs of people with disabilities. People do not have any legal recourse 15:31:50 ... barriers for a user with low vision to be a programmer 15:32:05 ... we are putting people at risk - we should be doing no harm 15:32:52 Josh - github is the platform that was chosen and we could use other tools but that will take research 15:33:03 Clarifying that my comment was also mostly about getting other to take commenting on our work seriously - like it has to this point. We need to make it do-able for the important orgnizations and individuals who commented on the FPWD, to be able to assign experinced staff to provide the thoughtful comments that they have. We cannot expect them to do that every month. 15:33:22 Wayne - in the research we found that this was not sustainable. This is a barrier for users with low vision but meets wcag 2.0 15:33:43 Josh- we need to bridge the gaps and looking for guideance in the low vision 15:33:47 q? 15:33:59 q- 15:34:36 ack bruce 15:34:36 bruce_bailey, you wanted to ask where outsider comments are posted 15:34:37 ... we have a lot of competing needs and we are listening to the requirements and balancing these needs 15:34:55 Bruce - there were comments that we are not responding to yet 15:34:56 My only point is that we need to be clear that WCAG 2.x doesn't result in full accessibility and ideally we will signal rolling updates to continually bridge the gap. 15:35:15 tinyurl.com/jmo9st4 15:35:17 ... are those github numbers 15:35:17 https://github.com/w3c/wcag21/issues/ 15:35:30 David - there is a list of all the comments 15:35:47 Pietro has joined #ag 15:36:01 Present+ Pietro 15:36:09 Josh - that is useful. To speak briefly on the comments. SC managers will be the responder for the comment and to suggest the response 15:36:10 q? 15:36:47 Josh - we need to keep focused and on quality 15:36:49 zakim, take up next 15:36:49 agendum 2. "New techniques work" taken up [from AWK] 15:37:10 Josh - SC work is good but we need to back up this with techniques 15:37:24 we need to start thinking about the techniques 15:37:33 q+ 15:37:48 ... we need to figure out how this will work and the TF 15:38:01 ack kathy 15:38:17 KW: There is already a lot of work done. 15:38:26 KW: We will need to go back to that and review etc 15:38:49 Josh - there will be expertise in the TF 15:39:00 KW: And make sure none of this is lost. 15:39:28 Wayne - we have been working on collecting the difficult pages when we try to implement the SC and the techniques 15:39:55 bad page is where we can identify what is going on to discuss techniques on how to remedy this 15:39:59 that is where we are at 15:40:06 It also has info on Testability: 15:40:07 https://www.w3.org/WAI/GL/wiki/Issue_78_Options#Testabilty 15:40:13 Laura - for issues 78 we are thinking of a strategy for this 15:40:57 q? 15:41:03 Josh - keep this in the back of your mind. we will put formal structure for this in the coming weeks 15:41:07 Josh - keep this in the back of your mind. we will put formal structure for this in the coming weeks 15:41:13 zakim, take up next 15:41:13 agendum 4. "Thursday call agenda items" taken up [from AWK] 15:41:22 zakim, take up next 15:41:22 agendum 4 was just opened, Kathy 15:41:48 zakim, take up next 15:41:48 agendum 4 was just opened, Kathy 15:42:02 zakim, close item 4 15:42:02 agendum 4, Thursday call agenda items, closed 15:42:03 I see nothing remaining on the agenda 15:42:03 zakim, take up agenda item 5 15:42:03 'item\ 5' does not match any agenda item, Kathy 15:42:06 agenda? 15:42:18 TOPIC: SC Review 15:42:24 https://www.w3.org/2002/09/wbs/35422/2017April5_top3/results 15:42:41 Josh - kick off Accidental Activation 15:42:54 it is a SC from mobile taskforce 15:43:01 Pietro_ has joined #ag 15:43:12 there were a few comments 15:43:38 believe so - the options 15:43:50 but threw me off with the link 15:44:20 there were comments on the accessbility support 15:44:24 s/It also has info on Testability:/The Issue 78 Options Wiki page for the survey has info on Testability/ 15:44:29 are there any objections 15:45:05 Resolution: accept Accidental Activation 15:45:24 RESOLUTION: Accept Accidental Activation SC 15:46:46 Josh - Support Personalization 15:46:47 https://www.w3.org/2002/09/wbs/35422/SCs_April_11/results 15:47:06 TOPIC: Support Personalization 15:47:11 Support Personalization / Issue 6 15:47:15 https://github.com/w3c/wcag21/issues/6 15:47:29 https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/guidelines/#support-personalization-minimum 15:48:04 there were no thumbs up for this SC 15:48:05 q? 15:48:50 KW: It is not clear what is being asked to be done beyond what is done in 1.3.1. or 4.1.2 15:49:00 KW: It seems like a lot of this is already covered. 15:49:19 KW: Not sure about diff between control and screen. 15:49:26 q+ 15:49:55 ack gow 15:50:06 zakim, ping me in 15 minutes 15:50:06 ok, Joshue108 15:50:12 Mike: is there someone from Coga on the phone? 15:50:30 John: I am on the call and will relay to Lisa 15:51:20 Wayne: there are classifications and was wondering if essential term is good enough 15:51:34 Q+ 15:52:00 could also be tightened up... I don't understand what the techniques would be for this 15:52:04 ack jf 15:52:31 JohnF: concerned about the wording of the SC. It seems to suggest a separate version 15:52:48 ... history has shown us that we should not have a parallel version 15:53:26 James: 5 controls per screen is not enough to do anything 15:53:43 John, would it be okay if it make it clearer that it means a version or presentation option is available? 15:53:54 how do you know what is essential functionality. People could be using the system differently 15:54:03 q+ 15:54:15 +1 to james 15:54:16 q+ 15:54:16 ack wayne 15:54:39 Wayne: WCAG 2.0 answered that by if you can throw this out of the page then it is not essential 15:54:51 James: then everything is essential 15:55:07 JohnF: there is a difference between applications and webpages 15:55:26 +1 to James N - "we don't put anything on the page that isn't essential" for a customer to use it. 15:55:40 ack glenda 15:56:57 Glenda: context is important on the number; change to number for each chunk. In the future you could have an overlay through personalization 15:57:02 q+ 15:57:21 ack jason 15:58:16 q+ 15:58:20 Jason: you can limit the number of controls by having control at a deeper level; that may not make it easier for the user. Now harder to find controls. Understand the rational but having a number is not the right way to achieve it 15:58:33 +1 15:59:17 Question: would a five-button "fly-out" menu, with each of those five top-level buttons containing 5 more navigation choices... would that meet the "Maximum of 5" criteria? 15:59:27 I also dont think we can restrict authors in that way as they design content for users in a way that they hope supports their needs in the first place. 15:59:34 q- 15:59:39 If we could have an ability to semantically identify what is absolutely essential for the “chunk” you are focused on now. Rather than setting a number of only 5 controls, an ability to only see the absolute essential controls. Could even later add the semantic ability to prioritize controls (just like heading levels). So…future semantic thinking here…but it could lead to overlays that let you filter out anything extra. 16:00:00 ... we don't know what is required to satisfy the proposal and it is not testable. We need to develop the AT before we start putting SC in place 16:00:28 ... it is too early to determine what is required 16:01:21 David: Jason covered my comments. I can see require authors do something to help users for cognitive impariments 16:01:56 Josh: is there any comments that have not been addressed? 16:02:09 ... needs a lot of work right now 16:02:36 q+ 16:03:03 Greg: what is comes down is that there is comments but needs to be address by the COGA TF 16:03:22 ack gower 16:03:24 ... should take in account all of the comments raised 16:03:53 Mike: my comments from January, there is lot of potential and we need to implement techniques 16:04:09 ... as it matures we can bring it back as SC 16:04:56 RESOLUTION: go back to COGA for reviewing comments and further work 16:05:07 Joshue108, you asked to be pinged at this time 16:05:43 TOPIC: Adapting text options 16:06:13 Josh: proposal C and D got comments 16:06:39 https://www.w3.org/2002/09/wbs/35422/SCs_April_11/results#xsc 16:06:42 https://www.w3.org/WAI/GL/wiki/Issue_78_Options 16:06:50 https://www.w3.org/WAI/GL/wiki/Issue_78_Options 16:07:08 q+ 16:07:11 It also has info on Testability: 16:07:12 https://www.w3.org/WAI/GL/wiki/Issue_78_Options#Testabilty 16:07:17 Laura: James comment on testability and there is some info on the WIKI page 16:07:23 q+ 16:07:51 ... it is for adapting text to override author settings 16:07:57 https://github.com/w3c/wcag21/issues/78#issuecomment-291918379 16:08:54 do we need to have a definition of minimum - the term at least 16:09:46 q+ 16:10:06 zakim, ping me in 10 minutes 16:10:06 ok, Joshue108 16:10:41 Greg: the problem is where you are allowing support overwriting the minimum. it needs to compatible for all fonts. If there is a function on the page then you can set a minimum number of fonts 16:10:42 q? 16:11:16 -1 on that. 16:11:51 scribe, wayne 16:11:59 scribe: wayne 16:12:54 There was no specification on splitting: Level A formatting overide, Level AA, AAA page doesn't supply it. 16:13:08 q+ to suggest we stick to the AA proposal as the AAA is not necessarilty suported by the LVTF 16:13:09 ack ryla 16:13:34 Katie: Ok with splitting in two. 16:13:44 ack davi 16:15:04 David: When the user agent gets overridden. Only need to test for one override. Can you need to override. Responsible for all then you can go wrong. That creates non testability. 16:15:22 +1 to David (and use a sufficient technique with that one font that is best for testing) 16:15:26 ack waye 16:16:08 q? 16:16:13 ack way 16:16:16 Wayne: I think we can compromise on the fonts. There are rules for typography for legibility. We need to think about other languages. Then we can specifically test for these 16:16:31 ... have a list of accessible fonts 16:16:34 ack steve 16:16:34 steverep, you wanted to suggest we stick to the AA proposal as the AAA is not necessarilty suported by the LVTF 16:16:36 What about the most common legible font in each language? 16:16:53 Steve: can we just talk about AA proposal 16:16:54 +1 to that. 16:17:13 are all of these proposals are trying to do the same thing 16:17:36 +1 16:17:45 What about using the wording the say "2 (or 3) most common legible fonts" in each language? 16:17:56 Against the AAA requirement, better to let the user do this and doesn't gain anything. What is needed is AA 16:18:00 +1 16:18:07 q+ 16:18:10 Steve, that would be for closed systems. 16:18:18 Josh: comes down to scoping the change 16:18:36 Can we say that this is going in the right direction 16:19:09 ack james 16:19:10 David: can we ask if people can get consensus 16:19:33 James: when we talk about overriding something.. is it anything or a specific method 16:19:53 Laura: talking about a number of different options 16:20:04 David: it is just one 16:20:06 Joshue108, you asked to be pinged at this time 16:20:11 +1 to just one 16:20:27 James: if I tell you this is how you can change it, does this meet the SC 16:20:33 Answer is yes 16:20:35 q+ 16:20:50 should be "a mechanism" 16:21:10 +1 to David's comments 16:21:11 I like Proposal E 16:21:27 q+ 16:21:28 James: it needs to be up to the author to decide what method is used 16:21:33 I also like proposal E...:-) 16:21:35 not the user 16:21:41 q+ 16:21:59 I agree that the conformance claim has to specify at least one mechanism that allows overriding author formatting while keeping the page completely functional. 16:22:03 ack awk 16:22:05 Josh: mechanism implies a thing 16:22:16 q+ 16:22:50 Andrew: it is one thing for a user to create a stylesheet and a different thing for user to change about this list of things 16:23:01 I am not a fan of mechanism 16:23:24 Laura: mechanism language is the problem 16:24:34 Andrew: if an author says that we meet the SC since told the user that they can change this by setting a list of things. On a small website this may be a short list but could be more on a larger site. This would not be acceptable 16:24:57 James: we would want to exclude somethings such as icon fonts 16:25:09 ack wayne 16:25:16 Wayne: i have thought about this for a long time 16:25:39 you have tokens that are user defined 16:25:59 we need to identify the things that the user can change it 16:26:29 want the author to verify that the content can be changed 16:27:07 Josh: isn't this just talking about passing if using CSS 16:27:11 Wayne: no sometimes blocks 16:27:41 ack steve 16:27:49 zakim, close queue 16:27:49 ok, Joshue108, the speaker queue is closed 16:28:18 This SC is inherently about a premier a11y tenet - the separating the content from its presentation ..... 16:28:47 Steve: the main comment from the user perspective the mechanism to do this is a few and when it breaks it really breaks. If there were a finite list of things that the author was doing to prevent this then it could be scoped that way 16:28:49 +1 ryladog 16:29:01 ... have given up trying to figure out the list of things 16:29:10 q+ 16:29:16 Josh: may be approaching this the wrong way 16:29:32 it is a handshake between the the developer and the user 16:30:17 Laura: we should leave out mechanism to narrow it some 16:30:27 E may be better 16:31:22 q+ 16:31:34 Josh: basically saying don't get in the way of user stylesheets 16:32:46 q? 16:32:50 ack jason 16:33:36 JW: The assumption around this language is that the mechanism succeeds. 16:34:20 JW: James question is interesting, and raises the issue that no mechanism is required but is assuming there is one that works and is limiting the consequese. 16:34:40 JW: This does raise the question - that when this falls down to AT in the end. 16:34:56 JW: Do we assume they can make the changes - it is all about consquence. 16:35:04 JW: and what the author can do etc. 16:35:06 Jason: There is not a lot of functionality is the assumtion succeeds and when it suceeds then we want to limit the consequences. If I understand the language correctly. It assums that one exists and it limits the consequences. The issue goes away but it assums that assistive technology exists. It succeeds on making the canges. What the author could or could not do. 16:35:11 LC: Whats your fave Jason? 16:36:07 refresh the vote results 16:36:18 RESOLUTION: Needs more discussion. 16:36:27 Suggest including some CSS language to it 16:36:41 ChrisLoiselle has left #ag 16:36:46 +1 to MC 16:37:32 bye 16:37:38 trackbot, end meeting 16:37:38 Zakim, list attendees 16:37:38 As of this point the attendees have been jasonjgw, AWK, Kathy, allanj, Joshue108, KimD, Laura, JF, kirkwood, Makoto, Lauriat, adam_lund, Melanie_Philipp, bruce-bailey, MikeGower, 16:37:42 ... steverep, Glenda, MichaelC, Greg_Lowney, marcjohlic, jeanne, Katie_Haritos-Shea, Wayne, jamesn, Pietro 16:37:46 RRSAgent, please draft minutes 16:37:46 I have made the request to generate http://www.w3.org/2017/04/11-ag-minutes.html trackbot 16:37:46 Wayne has left #ag 16:37:47 RRSAgent, bye 16:37:47 I see no action items