14:31:02 RRSAgent has joined #wai-wcag 14:31:02 logging to http://www.w3.org/2015/04/21-wai-wcag-irc 14:31:04 RRSAgent, make logs public 14:31:04 Zakim has joined #wai-wcag 14:31:06 Zakim, this will be WAI_WCAG 14:31:06 ok, trackbot; I see WAI_WCAG()11:00AM scheduled to start in 29 minutes 14:31:07 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:31:07 Date: 21 April 2015 14:31:22 zakim, agenda? 14:31:22 I see nothing on the agenda 14:32:08 agenda+ Extension model - what do we want to express with extensions? What kind of guidance to do want to give? 14:32:44 agenda+ Group and and prioritise items from the post-WCAG wiki https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 14:33:04 Review the current WCAG 2.0 requirements doc http://www.w3.org/TR/wcag2-req/ 14:33:26 Joshue has joined #wai-wcag 14:33:36 agenda+ Review the current WCAG 2.0 requirements doc http://www.w3.org/TR/wcag2-req/ 14:34:06 trackbot, start meeting 14:34:08 RRSAgent, make logs public 14:34:10 Zakim, this will be WAI_WCAG 14:34:10 ok, trackbot; I see WAI_WCAG()11:00AM scheduled to start in 26 minutes 14:34:11 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:34:11 Date: 21 April 2015 14:34:17 zakim, agenda? 14:34:17 I see 3 items remaining on the agenda: 14:34:18 1. Extension model - what do we want to express with extensions? What kind of guidance to do want to give? [from Kenny] 14:34:18 2. Group and and prioritise items from the post-WCAG wiki https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 [from Kenny] 14:34:18 3. Review the current WCAG 2.0 requirements doc http://www.w3.org/TR/wcag2-req/ [from Kenny] 14:34:34 Chair: Joshue 14:35:50 regrets+ Alan, Kathy, Christophe 14:36:23 Scribe list: https://www.w3.org/WAI/GL/wiki/Scribe_List 14:44:44 Makoto has joined #wai-wcag 14:55:19 WAI_WCAG()11:00AM has now started 14:55:26 +[IPcaller] 14:55:27 zakim, [IPcaller] is Joshue 14:55:27 +Joshue; got it 14:56:37 +[IPcaller] 14:56:44 +AWK 14:57:00 zakim, [IPcaller] is Makoto 14:57:00 +Makoto; got it 14:59:12 AWK has joined #wai-wcag 14:59:25 Zakim, who is on the phone? 14:59:25 On the phone I see Joshue, Makoto, AWK 14:59:46 Zakim, agenda? 14:59:46 I see 3 items remaining on the agenda: 14:59:47 1. Extension model - what do we want to express with extensions? What kind of guidance to do want to give? [from Kenny] 14:59:47 2. Group and and prioritise items from the post-WCAG wiki https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 [from Kenny] 14:59:47 3. Review the current WCAG 2.0 requirements doc http://www.w3.org/TR/wcag2-req/ [from Kenny] 15:00:30 +David_MacDonald 15:01:40 +??P9 15:02:23 zakim, call EricE-Skype 15:02:23 ok, yatil; the call is being made 15:02:25 +EricE 15:02:40 zakim, nick yatil is EricE 15:02:40 ok, yatil, I now associate you with EricE 15:02:42 zakim, mute me 15:02:42 EricE should now be muted 15:03:17 +Kenny 15:03:30 David has joined #wai-wcag 15:03:42 https://www.w3.org/2002/09/wbs/35422/21stApril2015/results 15:03:58 jon_avila has joined #wai-wcag 15:04:01 -EricE 15:04:08 zakim, call EricE-Skype 15:04:08 ok, yatil; the call is being made 15:04:10 +EricE 15:04:19 zakim, nick yatil is EricE 15:04:19 ok, yatil, I now associate you with EricE 15:04:22 zakim, mute me 15:04:23 EricE should now be muted 15:04:39 + +1.703.359.aaaa 15:04:45 zakim, I am aaaa 15:04:46 +jon_avila; got it 15:05:00 Loretta has joined #wai-wcag 15:05:20 https://www.w3.org/WAI/GL/wiki/Scribe_List 15:05:23 https://www.w3.org/WAI/GL/wiki/Scribe_List 15:05:31 -Kenny 15:05:38 +Kenny 15:05:38 scribe: jon_avila 15:05:51 +[IPcaller] 15:06:01 zakim, IPcaller is Loretta 15:06:01 +Loretta; got it 15:06:03 zakim, take up item 2 15:06:03 agendum 2. "Group and and prioritise items from the post-WCAG wiki https://www.w3.org/WAI/GL/wiki/Post_WCAG_2" taken up [from Kenny] 15:06:43 MoeKraft has joined #wai-wcag 15:07:19 jo: important page because it captures potential gaps in WCAG and issues and people's perception of WCAG -- it's a brain dump 15:07:24 +MoeKraft 15:07:31 q+ would like to hear from Makoto on the item in his response. Not sure that it is actually an answer to the survey question but want to understand 15:07:56 jo: feel free to look at doc and edit as you see fit. 15:08:35 +[IPcaller] 15:08:55 awk: we need to talk about extension and what is on the table for them. What things do we have existing comments on from the post WCAG wiki -- do those fit into a grouping for cognitive or mobile? Is there another extension that we may need based on looking at these. 15:09:25 q? 15:09:59 awk: no comments on this survey question -- but wanted to get Makoto to talk about his comment so we can discuss. 15:10:46 makoto: using the same set of criteria WCAG 2.0 - JIS is national standard. Also have same conformance claim requirements. 15:11:33 adam_solomon has joined #wai-wcag 15:12:07 makoto: need clarification on third party items and how they fit into conformance. Difference in how people interpret third party items. Would like answer from WCAG WG. 15:12:26 jo: Is this a general query or is it related to extensions? 15:12:36 makoto: not sure where it should go. 15:13:17 jo: should log this in Github as an issue. Is that possible for you to input that as a comment into Github? 15:13:43 makoto: Need correct answer by September. 15:13:47 marcjohlic has joined #wai-wcag 15:13:56 +Marc_Johlic 15:14:03 jo: be happy to talk about it now. Relevant topic. 15:14:09 q? 15:14:14 ack Dav 15:14:40 + +1.650.464.aabb 15:14:47 david: clarifying -- this about social media and partial conformance claims 15:15:01 makoto: yes 15:15:02 Zakim, who is on the phone? 15:15:02 On the phone I see Joshue, Makoto, AWK, David_MacDonald, Michael_Cooper, EricE (muted), Kenny (muted), jon_avila, Loretta, MoeKraft, [IPcaller], Marc_Johlic, +1.650.464.aabb 15:15:32 q+ 15:15:35 q+ 15:15:47 makoto: big differrenece if you can make a claim or partial claim. 15:16:13 makoto: no law in April of next year -- like ADA or DDA that will make it a requirement -- although not requirement yet. 15:16:17 zakim, mute me 15:16:17 Joshue should now be muted 15:16:54 ack me 15:16:58 david: So companies want to use social media but also want to be conformant. 15:17:03 kamoto: e.g. companies use buttons like Facebook like or pintrest 15:17:09 ack awk 15:17:48 awk: is social media where you are seeing these issues or is social media specifically called out? 15:18:09 kamoto: web content will be in scope of new law. Not clear yet what standards will be referenced. 15:18:42 q? 15:19:08 http://www.comm.twcu.ac.jp/~nabe/data/JIS-WAI/ 15:19:14 david: To be clear -- the links to the social media or feed to posting, etc. feedback, etc. that is what you are talking about? 15:19:36 david: some of those things can be fixed. 15:19:44 kamoto: sometimes they can and sometimes they can't be fixed. 15:19:53 q+ 15:20:00 ack jon 15:20:36 JA: Is a part of the problem content that you have no control over? 15:20:53 JA: Is there a choice, depending on hosting environments for example? 15:21:53 JA: Who is choosing the content? There is a destinction in where the responsibility lies? 15:21:56 q- 15:22:31 kamoto: pintrest button is invisible in high contrast mode. Can't be fixed. 15:23:09 JA: But that is your choice? 15:23:20 JA: If you choose it, are you not responsible? 15:23:29 JA: Shouldn't you provide an @alt? 15:23:39 q? 15:24:01 david: perhaps need to talk about what the partial conformance claim was meant to do. 15:25:10 JA: I wasn't referring to a text alternative but an alternative to that content 15:25:54 awk: Some redundancy between questions in the post WCAG wiki and those that are being raised by Kamoto 15:26:05 awk: We should look at this in structured way. 15:26:20 jo: It would be a good place to put it under the post WCAG section of the wiki 15:26:30 https://www.w3.org/WAI/GL/wiki/Post_WCAG_2 15:27:51 kamoto: thank you so much 15:28:59 awk: we don't need to discuss in detail but we need to talk on call about each item and the impact it would have. 15:30:18 awk: we aren't going through each article on call - we need to dish out actions for people to go through them (blog and article) to get granular details out of them to see if they are already represented or if something needs to be added. 15:31:03 jo: we need to link this in about the extention model as these topics are interconnected. Let's just walk through this document now. 15:32:04 jo: do we have volunteers to have people provide a brief abstract on each. 15:33:16 jo: We have ad hoc topics also such as meta data -- do we want to group these under potential extensions? 15:33:53 awk: there is a lot of information and we need to figure out how to approach this. 15:34:02 +James_Nurthen 15:34:06 jo: Document is not exhaustive either -- it's a starting point. 15:34:12 q? 15:34:21 -David_MacDonald 15:34:40 Suggested task for first 5 links. People need to read the article, then see if the issues mentioned in the blog post/article are already reflected in the other sections of the post-wcag wiki 15:34:53 jo: several of these topics could span multiple domains such as mobile and cognitive. 15:34:59 +David_MacDonald 15:35:31 jo: topic of CAPTCHAs spans multiple domains too. 15:35:55 jamesn has joined #wai-wcag 15:36:17 rrsagent, make minutes 15:36:17 I have made the request to generate http://www.w3.org/2015/04/21-wai-wcag-minutes.html jamesn 15:37:16 david: how would this work in legislation? 15:37:55 jo: down the road -- important question that but we are not there yet. 15:38:22 jo: questions are do we need failures, techniques, success criteria, or anti-patterns. 15:38:29 david: suggest success criteria 15:39:00 q? 15:39:28 q+ 15:39:32 david: if SC already exists -- perhaps we can manage by adding techniques to current WCAG 15:39:56 jo: only mint new SC when there isn't one covered. 15:40:04 david: why does it need to be in an extension at all. 15:40:16 ack awk 15:40:19 jo: extension could be a collection of techniques 15:40:43 awk: not the way I see it. Extension is not normative. 15:41:07 awk: extension allows us to add something that doesn't exist and modify something that is there that needs adjustment or clarity. 15:41:22 awk: extensions could also remove something. 15:41:38 awk: need to have a solid set of identified issues. 15:41:56 s/Extension is not normative./Extension is normative. 15:42:11 q+ 15:42:33 s/Extension is normative./Extension is normative. Techniques are not. 15:42:44 jo: extension models are short. May find that in large part WCAG may apply but need clarification. 15:42:50 q+ 15:42:55 q+ 15:43:04 ack Lore 15:43:06 david: I would nervous about adding something that would remove a WCAG requirement. Could be very confusing. 15:43:34 - +1.650.464.aabb 15:43:36 lgr: Extensions are being proposed because people are finding problems that aren't covered by the existing success criteria 15:44:11 ack me 15:44:15 lgr: Thought that we were saying WCAG is stable and we would make things backward compatible. 15:44:56 ack micha 15:45:02 jo: yes, that is a concern. 15:45:48 MC: Explore whether how extension could modify WCAG 2.0. Argument is only legitimate if WCAG gives permission. WCAG doesn't give permission to do that as we didn't think of that. 15:46:21 MC: Perhaps we fix urgent issue with SC by adding extension and then we build list of other issues for next version of guidelines. So something can't be solved by extensions. 15:46:58 MC: Nowhere in WCAG does it say that extensions can be created to change anything in WCAG. That violations normative requirements of WCAG and leads to confusions that people are expressing. 15:47:07 ack me 15:47:46 awk: Does the HTML spec give permission for extensions? e.g. longdesc 15:48:14 q+ 15:49:20 ack me 15:49:24 awk: high bar that original spec will see that it can be replaced. Do we need permission of a 7 year old document to write something different? 15:50:18 HTML5 says "Work on extending this specification typically proceeds through extension specifications which should be consulted to see what new features are being reviewed." 15:50:25 MC: Looking at HTML spec -- it doesn't say one way or another in normative way about extension. Status section does mention extension. Points to working group discussion. This gets into lawyer type stuff -- issues with interpretation, etc. 15:50:43 q? 15:50:45 q+ 15:51:37 MC: just being a messenger about the challenges Good to be cautious because sites that could cause harmonization issues for extensions that remove WCAG requirements 15:52:19 awk: Same issue could applies to HTML5 conformance with longdesc. 15:52:44 MC: longdesc adds a feature that was removed. 15:52:46 q? 15:53:35 awk: don't object to core idea that we need to be very careful. I want to make sure that we have a good sense of what we want to do and what others want us to do and the implications of those things as we build out the plan of how we do it. What does backwards compatible actually mean? 15:54:41 jo: we have flexibility on how we scope out extension. Longdesc adds a feature that was previously there. If we allow extension to alter perceived standard of WCAG SC that could be a real problem. 15:54:41 +1 15:54:46 q+ 15:55:18 ack j 15:55:20 jo: we could define that extension don't override existing SC but complement or add to them but not override or nullify 15:55:34 q+ 15:55:43 ack dav 15:56:10 q+ 15:56:21 david: I would oppose anything that alters WCAG. If we want to override WCAG then we need to go to WCAG 3. 15:56:22 q- 15:57:03 q+ 15:57:08 ack jon 15:57:28 JA: The work the mobile TF is doing could be an extension. 15:58:17 JA: There are other things in teh current SCs where we could be adding failures or new SCs. Not just one or the other. 15:58:24 q? 15:58:53 JOC: Would that not just be WCAG 3.0? 15:58:58 q+ 15:59:01 JA: I'm not suggesting that. 15:59:17 JA: Don't want too much of the mobile stuff just to extensions. 16:00:11 JA: We need to document things clearly. 16:00:13 q? 16:00:15 ack me 16:00:15 ack awk 16:00:18 q- 16:01:03 awk: agree that mobile work will be extension and techniques that fall under the current SC. 16:01:48 awk: what in your mind (David) is different between WCAG 3 and an extension? Small changes through an series of extensions could get wrapped into a new big thing. 16:03:07 david: e.g. if I add a coat to my clothes that extends. If I change my undershirt from cotton wool and then put on the coat -- that is actually changing my clothes not just extension them. I don't mind add layers even though there is risk to that. 16:04:19 q+ to say that adding an extension doesn't change a country's law that referenced WCAG 2.0 until the law changes to be WCAG 2.0 + extension. 16:04:28 david: don't mind discussing everything -- but best to keep WCAG solid but just add things. Yes, that may add contrived things. 16:05:06 q+ 16:05:26 ack Lor 16:05:31 jo: Don't think we change WCAG 2.0 at all. 16:05:45 s/Don't think we change WCAG 2.0 at all./Don't think we can change WCAG 2.0 at all. 16:06:26 lgr; content that conformance to wcag plus extension and if you remove extension content still conforms to WCAG. This allows you to make stricter requirement. Upward compatible 16:06:28 Could we have content that conforms to the extension and not WCAG 2.0? 16:06:59 lgr: WCAG 3 would just throw the door wide open to change level of SC. 16:07:25 lgr: moving something from Level AA to A would fit extension model while move Level AA to AAA would not fit the extension model. 16:08:08 consistent extension, like it 16:08:56 q? 16:09:29 ack awk 16:09:29 AWK, you wanted to say that adding an extension doesn't change a country's law that referenced WCAG 2.0 until the law changes to be WCAG 2.0 + extension. 16:09:32 JN: extension could be free to create a Level A contrast SC because there is no contrast requirement at level A. 16:10:25 awk: Reason why I want us to be familiar with post WCAG items is because some of these will and some won't fit into the model that LGR discussed 16:11:23 awk: If we have an extension that modifies WCAG and a country has a policy on that -- doesn't effect them until the adopt extension. 16:11:59 awk: Extension doesn't operate in changing adopted standards. 16:12:07 q? 16:14:10 jo: positive use case for extension to use as a framework for organizing 16:14:11 ack jon 16:14:16 q+ 16:14:33 JA: One other difference would be how we get gov to adopt extensions sooner? 16:14:52 JA: We hope they would do that more easily than adopting a WCAG 3.0. 16:15:05 JA: That is intersting to stakeholders, but there is a lack of awareness. 16:15:08 q+ to talk about the potential complexity issue of all this 16:15:26 JA: Agencies are free to accept additional a11y standards. 16:15:50 JA: This would fall under the 508 refresh, and is a nice flexible model, so +1. 16:16:03 JA: Even with WCAG 3.0, there will still be a need for extensions! 16:16:11 JA: Right now, I support this. 16:16:13 q? 16:16:18 ack marc 16:17:04 marc: what if something can't be done or doesn't apply for mobile, how does that fit in? 16:17:35 marc: trying to think of something like that -- would that be ok? For example, something doesn't apply? 16:18:13 JN: If something doesn't apply isn't it out of scope and automatically applies? 16:18:40 q? 16:19:05 ack james 16:19:05 jamesn, you wanted to talk about the potential complexity issue of all this 16:19:18 marc: just wondering what wording we would use for situations where something does apply. 16:19:39 JN: Or perhaps there is a better way. e.g. a thought control interface but not a keyboard interface. 16:20:06 q+ to say we will need clear requirements and explainers 16:20:19 JN: Like extension idea -- but concerned about complexity of having these additional items on top could be problematic. Also concerned with multiple extensions and conflicts between the two? 16:20:26 ack me 16:20:27 MichaelC, you wanted to say we will need clear requirements and explainers 16:20:28 ack micha 16:21:15 MC: Valid warning on extension working together. Will need good guidance and explainer document. Regarding conflicts -- important issue. 16:21:39 MC: Perhaps we could forbid extensions that conflict with each other. That is a decision we will have to make. 16:22:01 q? 16:22:08 MC: we don't allow we will need to be on top of observing conflicts and work them out before acceptance. 16:22:17 jo: Fantastic information here in the call. 16:24:11 q? 16:24:13 jo: we will need a framework for extensions to make sure we have unique but consistent requirements 16:24:18 jo: Any other questions? 16:24:34 *thanks 16:24:36 -[IPcaller] 16:24:40 -AWK 16:24:40 zakim, list attendees 16:24:42 As of this point the attendees have been Joshue, AWK, Makoto, David_MacDonald, Michael_Cooper, EricE, Kenny, +1.703.359.aaaa, jon_avila, Loretta, MoeKraft, [IPcaller], Marc_Johlic, 16:24:42 ... +1.650.464.aabb, James_Nurthen 16:24:42 -Joshue 16:24:44 -Michael_Cooper 16:24:46 -Kenny 16:24:48 -James_Nurthen 16:24:49 -Loretta 16:24:49 -MoeKraft 16:24:51 -David_MacDonald 16:24:52 RRSAgent, make minutes 16:24:52 I have made the request to generate http://www.w3.org/2015/04/21-wai-wcag-minutes.html jon_avila 16:24:53 -Makoto 16:24:55 -Marc_Johlic 16:25:11 trackbot, end meeting 16:25:11 Zakim, list attendees 16:25:11 As of this point the attendees have been Joshue, AWK, Makoto, David_MacDonald, Michael_Cooper, EricE, Kenny, +1.703.359.aaaa, jon_avila, Loretta, MoeKraft, [IPcaller], Marc_Johlic, 16:25:14 ... +1.650.464.aabb, James_Nurthen 16:25:19 RRSAgent, please draft minutes 16:25:19 I have made the request to generate http://www.w3.org/2015/04/21-wai-wcag-minutes.html trackbot 16:25:20 RRSAgent, bye 16:25:20 I see no action items