15:38:59 RRSAgent has joined #wai-wcag 15:38:59 logging to http://www.w3.org/2016/11/29-wai-wcag-irc 15:39:01 RRSAgent, make logs public 15:39:04 Zakim, this will be WAI_WCAG 15:39:04 ok, trackbot 15:39:04 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 15:39:04 Date: 29 November 2016 15:39:20 bruce_bailey has joined #wai-wcag 15:39:28 Chair: Joshue 15:40:51 shadi has joined #wai-wcag 15:41:36 MyNickname has joined #wai-wcag 15:43:02 is Joshue108 15:43:21 MyNickname is Joshue108 15:44:39 Joshue108 has joined #wai-wcag 15:46:10 agenda+ COGA feedback requested https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/  15:46:15 zakim, agenda? 15:46:15 I see 2 items remaining on the agenda: 15:46:16 6. Survey: https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results [from AWK] 15:46:16 7. COGA feedback requested https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/  [from Joshue108] 15:46:48 agenda+ DPUB business 15:49:04 zakim, clear agenda 15:49:04 agenda cleared 15:49:23 agenda+ New SCs https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results 15:49:34 agenda+ COGA feedback requested https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/  15:49:40 agenda+ DPUB business 15:55:06 AWK has joined #wai-wcag 15:55:14 Zakim, agenda? 15:55:14 I see 3 items remaining on the agenda: 15:55:15 1. New SCs https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results [from Joshue108] 15:55:15 2. COGA feedback requested https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/  [from Joshue108] 15:55:15 3. DPUB business [from Joshue108] 15:55:21 Wilco has joined #wai-wcag 15:55:24 Zakim, who is on the phone? 15:55:24 Present: AWK, Srini, alastairc, Tzviya, mattg, Greg_Lowney, marcjohlic, DavidMacDonald, Avneesh, JF, kirkwood, bruce_bailey, jeanne, Glenda, Wilco, Kathy, Joshue108, steverep, 15:55:27 ... George, JaEunJemmaKu, Katie_Haritos-Shea, KimD, MikeGower 15:55:43 Present: AWK 15:55:44 Zakim, who is on the phone? 15:55:44 Present: AWK 15:56:15 tzviya has joined #wai-wcag 15:56:45 present+ Joshue 15:57:23 Chair: Joshue 15:57:29 present+ Wilco 15:58:00 Srini has joined #wai-wcag 15:58:27 clapierre has joined #wai-wcag 15:58:37 Greg has joined #wai-wcag 15:59:25 present+ Bruce_Bailey 16:00:15 present+ Greg_Lowney 16:00:17 resent+ Laura 16:00:56 Avneesh has joined #wai-wcag 16:00:56 Jim_S has joined #wai-wcag 16:01:09 Present+ Srini 16:01:11 present+ Laura 16:01:13 present+ Avneesh 16:01:18 steverep has joined #wai-wcag 16:01:26 gowerm has joined #wai-wcag 16:01:27 present+steverep 16:01:27 present+ Charles_LaPierre 16:01:29 Joshue108 has joined #wai-wcag 16:01:29 Scribe: Jeanne 16:01:47 present+ Tzviya 16:01:49 Makoto has joined #wai-wcag 16:01:58 present+ Mike_Gower 16:02:10 present+ Joshue108 16:02:24 Put me down for december 13th :) 16:02:33 present+ Makoto 16:02:37 present+ Jim_S 16:02:38 Lauriat has joined #wai-wcag 16:02:47 I can take one 16:02:48 Present+ Lauriat 16:02:48 Glenda has joined #wai-wcag 16:02:58 present+ jeanne 16:03:03 Jan 3 16:03:16 present+ Glenda 16:03:18 kirkwood__ has joined #WAI-WCAG 16:03:28 present+ MichaelC 16:03:52 present+ kirkwood 16:04:20 zakim, agenda? 16:04:20 I see 3 items remaining on the agenda: 16:04:21 1. New SCs https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results [from Joshue108] 16:04:21 2. COGA feedback requested https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/  [from Joshue108] 16:04:21 3. DPUB business [from Joshue108] 16:04:39 scribenick: jeanne 16:04:44 zakim, who is on the phone? 16:04:44 Present: AWK, Joshue, Wilco, Bruce_Bailey, Greg_Lowney, Srini, Laura, Avneesh, steverep, Charles_LaPierre, Tzviya, Mike_Gower, Joshue108, Makoto, Jim_S, Lauriat, jeanne, Glenda, 16:04:44 zakim, take up item 2 16:04:47 ... MichaelC, kirkwood 16:04:47 agendum 2. "COGA feedback requested https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/ " taken up [from Joshue108] 16:04:53 George has joined #wai-wcag 16:05:22 KimD has joined #wai-wcag 16:05:23 JO: this is a heads-up from COGA for feedback on their success criteria 16:05:23 present+ George 16:05:38 +KimD 16:05:39 https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/ 16:06:09 ... please have a look and give feedback 16:06:13 I can access 16:06:14 jamesn has joined #wai-wcag 16:06:16 https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/ 16:07:28 present+ David_Macdonald, James_Nurthen 16:07:38 ... this is the first request, there will be more in the next few weeks. 16:07:45 zakim, take up item 3 16:07:45 agendum 3. "DPUB business" taken up [from Joshue108] 16:08:01 https://www.w3.org/2002/09/wbs/35422/ACT_DPUB_Review_Nov_2016/results 16:08:28 regrets+ Alastair_Campbell, JohnF, Kathy_Wahlbin 16:08:30 JO: I don't have a firm agenda for this topic. I want to wrap up the issues left over from the previous meetings. 16:08:42 ... I want to make sure we have resolutions and next steps. 16:08:50 q? 16:08:56 jon_avila has joined #wai-wcag 16:09:05 present+jon_avila 16:09:23 Tzviya: We had a DPUB meeting yesterday. We had a mini-agenda based on our discussion in the meeting with WCAG last week 16:09:25 marcjohlic has joined #wai-wcag 16:09:31 present+ marcjohlic 16:09:47 https://www.w3.org/TR/WCAG20/#set-of-web-pagesdef 16:09:52 ...1) the WCAG concept as a "set of web pages" which David had suggested might fit. 16:10:10 ... we talked about adding an additional example to the definition 16:10:10 Example: A publication is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages. 16:10:17 DavidMacDonald has joined #wai-wcag 16:10:27 ... Matt Garrish proposed some language (above) 16:10:30 MoeKraft has joined #wai-wcag 16:10:47 Present+ DavidMacDonald 16:10:58 ... this way ok with the DPUB group. It's intentionally broad. 16:11:13 +1 16:11:24 +1 16:11:25 present- David_Macdonald 16:11:46 Mike_Elledge has joined #wai-wcag 16:11:46 +1 16:11:49 q+ 16:11:49 +1 16:12:08 ack awk 16:12:38 Ryladog has joined #wai-wcag 16:12:56 Present+ Katie_Haritos-Shea 16:12:59 q+ 16:13:22 q+ 16:13:22 q+ 16:13:45 AWK: Just so I'm clear. You are proposing that the line become a part of the existing definition. If we think that the current definition already covers this, I would prefer that it be handled in the Understanding doc, so it doesn't change people's interpretation of the definition. 16:13:46 ack ryla 16:13:51 https://www.w3.org/TR/WCAG20/#set-of-web-pagesdef 16:13:52 https://www.w3.org/TR/WCAG20/#set-of-web-pagesdef 16:14:23 q+ 16:14:29 Present+ Mike Elledge 16:14:40 Katie: Why would we not add it to the definition? We are adding it to 2.1, it is backwards compatible, and we are only adding an example. 16:14:49 ... I think we should include it. 16:15:12 Rachael has joined #wai-wcag 16:15:16 ack me 16:15:23 web page definition included examples 16:15:25 https://www.w3.org/TR/WCAG20/#webpagedef 16:15:54 present+ Rachael 16:16:05 q- 16:16:07 Tzviya: the proposal is to add this example to the existing definition. 16:16:24 ack dav 16:16:27 Josh: Adding it to the defintion would be a more public endorsement. 16:16:45 q? 16:16:47 s/defintion/definition 16:17:14 q+{ 16:17:16 q? 16:17:19 David: I think it is good to add it as an example. It doens't change the definition. The words are the same. It shows that we are embracing a new thing. The Understanding document doesn't get as much. 16:17:23 ack jon 16:17:32 q+ to say that it does change the normative meaning 16:17:38 ack { 16:17:38 ack { 16:17:48 ack awk 16:17:48 AWK, you wanted to say that it does change the normative meaning 16:17:55 JonA: Is this for the definition of page, or set of pages? 16:18:03 Josh: Set of pages 16:18:31 q+ 16:19:04 AWK: I don't agree, there is no where in WCAG that it says that Notes or Examples are not normative. I want to be careful because it is normative. I can go either way, I just want to be careful that there are specific and real benefits to doing so. There are also some costs. 16:19:28 https://www.w3.org/TR/WCAG20/#set-of-web-pagesdef 16:19:33 Josh: Michael? Do you see any way that it is changing the mormative definition? 16:19:34 set of Web pages collection of Web pages that share a common purpose and that are created by the same author, group or organization Note: Different language versions would be considered different sets of Web pages. 16:19:52 s/mormative/normative 16:20:06 Example: A publication is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages. 16:20:47 q+ 16:20:56 ack mike 16:21:15 Josh: There seems to be broad consensus, but it will need to be a survey to the larger group. 16:21:35 q+ 16:21:47 q+ 16:21:55 Mike: This seems to be a sweeping decision to add digital publishing. Is there any conflict with the WCAG applying to the digital publishing world? 16:22:37 Katie: The US government is including electronic documents to add WCAG. I don't see how it breaks backward compatibility. 16:23:11 q+ 16:23:29 ack steve 16:23:37 Mike: I just raise it because it raises a broad set of standards to apply to specifically to digital documents. I can't think of anything off the top of my head that is a problem. 16:24:20 Steve: I have no objection. I'm looking at the existing defintion, which is already broad. I think that if you put one example, you should have more examples to keep the definition broad. 16:24:38 Josh: We have other definitions elsewhere. 16:25:05 Steve: But one example focuses a broad defintiion down to a narrow. 16:25:16 ack david 16:25:25 Josh: Are there other areas where we have definitions that need more examples? 16:26:50 q? 16:27:05 David: We aren't making new defintions, it always applied to a set of pages. We used set of pages because we couldn't define a "web site" because we couldn't define where is started and stopped. This adds some clarity to it. We could add more examples, but we have plenty of definitions that only have one example. It's the best fit for digital publishing. 16:27:16 ack avneesh 16:28:07 Avneesh: Clarifications: We have already done the ePub accessibility publications. Most other things in WCAG that apply to dPub. Everything in WCAG applies to digital publishing. 16:28:54 ... books are ready online and offline. The strategy of W3C to apply to digital publishing. It is the best first example to get into the WCAG. This is the first step. 16:29:44 AWK made Issue 72 for this: https://github.com/w3c/wcag21/issues/72 16:29:57 1+ for all of Avneesh's comments and this was our Gap analysis from DPUB http://w3c.github.io/dpub-accessibility/ 16:30:13 RESOLUTION: To route Issue-72 for approval 16:30:43 Tzviya: 2) Metadata: I know there was a lot of discussion on how to treat metadata 16:30:49 https://schema.org/accessibilityFeature 16:31:00 http://pending.schema.org/ 16:31:27 ... Schema.org includes accessibility features already. The pending schema.org features will be approved in a few weeks, before the FPWD of 2.1. 16:31:30 q+ 16:32:12 q+ 16:32:15 ... DPUB is proposing these are included in WCAG 2.1 in some way. We propose including them as a Best Practice, Technique or AAA success criteria. We want consensus today on the best way to include them. 16:32:23 ack ryla 16:33:24 https://www.w3.org/TR/UNDERSTANDING-WCAG20/appendixC.html 16:33:35 Katie: I want to do an update to the Metadata Appendix that was written in 2006. I haven't been able to meet with the people yet, but hopefully we will have something we can go forward with. 16:33:55 Josh: Tzviya, do you have a preference? 16:34:26 Katie: A Technique has to support a success criteria, and I don't think you have success criteria to attach it too. 16:34:57 Josh: I was going to say that I don't think Techniques will work. Tzviya, how do you feel about this being a Best Practice? 16:35:13 q+ 16:35:22 q+ 16:35:29 Tzviya: we were ok with Best Practice, but I understood from last week that we dont' have a category of Best Practice. 16:35:37 https://www.w3.org/TR/UNDERSTANDING-WCAG20/appendixC.html 16:36:00 Katie: Chaas McCathie Neville said he would like to see it as a level AA success criteria 16:36:02 ack davi 16:36:18 https://www.w3.org/wiki/WebSchemas/Accessibility 16:36:23 David: I was looking at accessibility features that have already been approved. 16:36:47 ... theere is a certain amount of overlap, there are checklist-type things. 16:37:19 q+ 16:37:24 ... if there is a metadata tag for WCAG-conforming and the level. That would fit in with what we already have 16:37:56 ... the technologies relied on would also helpful. I don't think we can require it. 16:38:08 Josh: I don't think it could be a best practice. 16:38:23 Katie: It would be multiple 16:38:29 +1 aaa success criteria 16:38:29 ack awk 16:38:38 ... let's agree on AAA success criteria 16:39:20 q+ 16:39:25 AWK: Which issue in the repository -- which metadata would apply to existing success criteria. If we can establish, "no that's not the case" then we can talk about AAA success criteria. 16:39:46 https://github.com/w3c/wcag21/issues/17 16:40:15 Katie: resource discovery would be alternative. This would deal with 1.2, 2.2 16:40:29 Request to consider inclusion of accessibility metadata #16 https://github.com/w3c/wcag21/issues/16 16:41:25 Metadata for Resources Discovery, could have Techiques are 1.1.1 Long Descriptions, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5 16:41:36 Jim_S has joined #wai-wcag 16:41:37 Avneesh: These two are most useful. Others are access mode (audio, visual, tactile) 16:41:56 Charles: The other is accessibility hazards 16:42:07 https://www.w3.org/wiki/WebSchemas/Accessibility 16:42:29 existing schema.org accessibitlity features: https://schema.org/accessibilityFeature 16:42:47 pending features http://pending.schema.org/ (search on accessibility) 16:43:11 Katie: Resource discovery for tactical map. That's additional. What are you talking about for tactile? 16:43:27 For Hazards this is the link https://schema.org/accessibilityHazard 16:43:41 q+ 16:43:52 ack ry 16:44:04 Avneesh: We see tactile in several forms. There is a requirement for alternative content. We want to help with discovery. A publication could be availalbe totally in braille, for example. 16:44:30 ack steverep 16:44:40 Tzviya: The accessibiltiy feature can have a value of MathML, so someone can discover that the resource includes math, or braille, for example 16:45:32 q+ 16:45:37 q- 16:45:49 q+ to say do we have a draft technique for this? 16:46:06 Steve: THis is the kind of success criteria that would allow people to search on specific types of content, like on YouTube. This is a success criteria that describes pre-termined information to the user. 16:46:32 ack wilco 16:46:47 ... it would need some work in the definition, e.g. a document described as MathML wouldn't be entirely MathML, so the defintiion would need some work. 16:48:02 q+ 16:48:07 ack 16:48:07 Wilco: It sort of conforms to WCAG, but not exactly. I think this introduces confusion. For example, if we say it is keyboard accessible, does that mean it passes "2.1, 2.2 or 2.3" Without more work on what maps where, we would be introducing confusion. We need it mapped to WCAG. 16:48:36 s/"2.1, 2.2 or 2.3"/"2.1.1, 2.1.2 or 2.1.3" 16:48:46 Completely agree, but that's a schema.org issue and why it should be advisory at first 16:49:10 ack me 16:49:10 Joshue, you wanted to say do we have a draft technique for this? 16:49:11 George: I do believe it is very valuable in discovery. The human readable description can clarify what is there. In tactile, having a link to the 3D model or swelling paper and having that information in the metadata is very valuable. 16:50:00 Josh: Have we got a Technique for this? Could you put together a sample Success Criteria 16:50:15 The value I've heard mentioned seems to be largely linked to available content at a macro level: CC, audio description... That makes sense to possibly include as a AAA for those SC that deal specifically with content 1.2.1-1.2.5. But most WCAG SC are not so macro-content related. 16:50:16 It can't be a sufficient technique unless it allows you to pass a success criteria 16:50:17 Tzviya: I can write something, I just need to know what to write. 16:50:25 Katie: We can do it in the next week. 16:50:43 q? 16:50:46 Josh: It makes more sense to me as a success criteria. Let's see some proposals. 16:51:02 Katie: can we go beyond the Dec 1 date? 16:51:06 ack ge 16:51:15 Josh: I think so. It is important. 16:51:44 ack George 16:51:49 ack george 16:52:01 ack tzviya 16:52:13 SC XXXX Metatdata: Metadata is provided which describes the accessibility characteristics of the content 16:52:32 Thank you Josh, I have been waiting for the last 3 weeks to talk about low vision success criteria 16:52:48 Thanks David! 16:52:58 Tzviya: For those concerned about wording on Schema.org wording. The DPUB group controls that wiki. If you have concerns about wording, send them to me or Matt Garrish and we will work something out. 16:53:40 ReSOLUTION: Katie to work on text for proposed success criteria metadata with others. 16:54:10 Tzviya: We want to update Appendix C 16:54:16 https://www.w3.org/TR/UNDERSTANDING-WCAG20/appendixC.html 16:54:25 rrsagent, make minutes 16:54:25 I have made the request to generate http://www.w3.org/2016/11/29-wai-wcag-minutes.html jeanne 16:54:36 accessibilityFeature: levelWCAG2 16:54:45 rrsagent, make logs public 16:54:51 accessibilityFeature: levelWCAG2-1 16:55:10 Katie: The information for Schema.org wasn't available then, and it needs to be updated. 16:55:11 accessibilityFeature: levelWCAG2v1 16:55:44 q? 16:55:58 accessibilityFeature: levelWCAG2-A 16:56:08 accessibilityFeature: levelWCAG2-AA 16:56:12 accessibilityFeature: levelWCAG2-AAA 16:56:13 Glenda has joined #wai-wcag 16:56:14 zakim, agenda? 16:56:14 I see 3 items remaining on the agenda: 16:56:15 1. New SCs https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results [from Joshue108] 16:56:15 2. COGA feedback requested https://www.w3.org/2002/09/wbs/35422/COGA_Feed1/  [from Joshue108] 16:56:15 3. DPUB business [from Joshue108] 16:56:30 zakim, take up item 1 16:56:30 agendum 1. "New SCs https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results" taken up [from Joshue108] 16:57:42 https://www.w3.org/2002/09/wbs/35422/NewSC_20161122/results 16:58:20 TOPIC: New SC proposal - Issue 10: Interactive Element Contrast (Minimum) 16:58:32 https://github.com/w3c/wcag21/issues/10 16:59:27 Yep 17:00:19 Josh: In terms of votes, 5 have accepted it. 9 accepted with changes. 1 Do not accept. 17:00:24 Request forbidden by administrative rules. 17:01:14 Wilco: I posted several issues in Github which are already posted. It seems like there are loopholes that need to be addressed before we progress. 17:02:07 Josh: In the broaders sense, can we work things out or are there things that are show-stoppers that are completely wrong. 17:02:22 Wilco: I think all these things can be worked out. 17:02:37 q+ to talk about the disabled items 17:02:49 Katie: These are new and need to have details that need to be worked out. 17:02:58 Thank you, Wilco. 17:03:29 Josh: So if you think it is totally off-base we need to know. We will discuss improvements. 17:03:47 Wilco: I didn't approve with changes because it needs so much work. 17:03:52 q+ 17:03:55 q? 17:04:03 ack jame 17:04:03 jamesn, you wanted to talk about the disabled items 17:04:08 Josh: I see that no one has commented on the GH issues. 17:04:47 We need to find other ways to communicate disabled items 17:04:57 ack glen 17:05:02 q+ 17:05:02 JamesN: The major thing that needs to be worked out is "disabled items". It makes them look like non-disabled items. This adds a great deal of confusion. I think it is a non-starter unless it has a low contrast which is also a non-starter. 17:05:07 +1 lower contrast threshhold for disabled item 17:05:31 Glenda: Thank you to Wilco for making all these comments 17:05:33 q+ 17:05:48 q+ 17:05:50 +1 on disabled, that was one of my points as well 17:06:17 Disabled items are there to give you clues about what is available and what might be options. People with low vision should have access to that information 17:06:19 Glenda: Wilco and I will work together on a specific proposal. 17:06:22 ack ryla 17:06:57 Katie: We need to have discussion on making a decision to change the paradigm. 17:06:59 +1 to developing concensus on disabled items and suitable contrast 17:07:13 ... everyone should put their informaiton in Github issue 17:08:08 Josh: Do you mean not to put comments in WBS? 17:08:24 Katie: No, I just mean to put comments in GH. 17:08:44 ack jon 17:08:59 q+ 17:09:56 JonA: We need to think how disabled items can be conveyed more effectively. It is valuable information that people iwth low vision need. There is text, there is other content to help you get it un-dsiabled. We need to think beyond what has always been done. 17:10:14 Josh: We welcome paradigm-busting and new ideas. 17:10:15 ack mike 17:10:15 +1 to jon avila 17:10:31 +1 to jon 17:10:40 ack gow 17:10:45 +1 to jon 17:11:05 MikeG: I want to echo what Jon has said. There are a lot of content out there which would be non-conforming if we changed this. 17:11:31 ... I want to suggest a 3rd level of ratio that covers disabled item that is lower than 3.1 17:11:34 q+ 17:11:38 + 17:11:46 q+ 17:11:55 ack glen 17:12:04 ... you can't always see what is in disabled field, but it is at least a trigger that more needs to be discovered. 17:12:28 What about an icon to indicate disabled? 17:12:39 Yes David 17:12:59 Glenda: Wayne Dick said that we need to see the disabled control. It is an old paradigm. I think about unavailable ?? are marked as ?? 17:13:03 q+ to ask if SC 1.4.3 AA 4.5 ratio "Incidental: Text or images of text that are part of an inactive user interface component ... have no contrast requirement." is in scope for 2.1? 17:13:08 That's lighthouse 17:13:14 Lighthouse 17:13:30 4.5 was a negotiated value 17:13:31 ... who are the people who established the original people who worked on the ratios for the original 2.0 17:13:34 http://www.lcfvl.org/ 17:13:38 ack Laur 17:13:57 Katie: Gregg Vanderheiden 17:14:13 ack ry 17:14:35 Shawn: We need some other way, just because it was always done this way doesn't mean it should continue. 17:14:41 ack bruce 17:14:41 bruce_bailey, you wanted to ask if SC 1.4.3 AA 4.5 ratio "Incidental: Text or images of text that are part of an inactive user interface component ... have no contrast 17:14:44 ... requirement." is in scope for 2.1? 17:14:52 Katie: It would be backward compatible 17:15:04 q+ 17:15:08 Fair enough, Katie. 17:15:21 s/?? are marked as ??/unavailable airline seat are marked with an X 17:15:41 ack david 17:15:43 Bruce: My question is answered by Katie, I wondered if changing the minimum contrast ratio would break backward compatibility. 17:16:03 q+ 17:16:04 David: I like JonA's idea of a new paradigm. Perhaps a new icon. 17:16:14 ack steve 17:16:17 q+ 17:17:15 Josh: Has anyone reached out to the COGA group to see if they are working on it? 17:17:25 Glenda: I will reach out. 17:17:35 John: I am on the COGA TF. 17:18:09 +q 17:18:52 Mike: I am concerned with the meaning of "perimeter". WE need to distinguish between the inner and outer edge. If you have a white border on a black outline. If the focus indicator example, you need to distinguish between the inner and outer indicator. 17:19:34 ... a lower contrast ratio than 3:1, we need more ability to distinguish between the focus indicator, @@, and @@. 17:19:39 A bit of history... originally in WCAG we ddid not have an exception for disabled items. SAP negotiated that into WCAG in the last year 17:20:21 Josh: Who on LVTF on the call is going to take responsibility for adapting the feedback from this call? 17:20:29 Glenda: I volunteer to be responsible. 17:21:02 q? 17:21:06 ack gower 17:21:10 Alex Li of SAP (now at Microsoft) nogotiated the exception for disabled items. 17:21:43 AWK: Once these proposals are submitted, they are the WCAG WG's responsibility. We may need to ask questions of the task force, but I expect that everyone on the call should be taking responsibility to engage on these issues. 17:21:46 s/nogotiation/negotiation 17:22:28 s/nogotiated/negotiated 17:22:34 Josh: Now the working group owns these success criteria, so share your knowledge and expertise and wade in on the issues and comments. 17:22:39 q+ to ask about issues within issues in git hub 17:22:51 ack glenda 17:23:54 ack bruc 17:23:54 bruce_bailey, you wanted to ask about issues within issues in git hub 17:24:30 RESOLUTION: Glenda to work on an updated proposal on Disabled Item Success Criteria proposal 17:24:52 Bruce: I am concerned about issues within issues in Github. There used to be better tools. 17:25:30 Josh: It gets time to get used to, but I encourage you to start using the tools and be a part of the discussion. 17:25:49 TOPIC: New SC proposal - Issue 9: Informational Graphic Contrast (Minimum) 17:25:57 https://github.com/w3c/wcag21/issues/9 17:26:14 Laura: I started that proposal and Alastair picked up on it. 17:26:36 Josh: Mostly approvals and a few comments. 17:27:09 Wilco: Most of the same issues as the previous issue 17:27:26 Josh: Is there anything that is way off, that you can't work with. 17:27:35 Wilco: it needs another pass at it. 17:27:51 q+ to ask about photographs and paintings in LVTF discussions 17:28:24 ack bruce 17:28:24 bruce_bailey, you wanted to ask about photographs and paintings in LVTF discussions 17:28:35 Laura: I can collaborate with Alastair to revise the proposal based on the comments in the WBS and this meeting 17:29:01 RESOLUTION: Laura and Alistair to work on an updated proposal on Informational Graphic Contrast (Minimum) 17:29:23 Bruce: How does the LVTF address paintings and photographs? It is not clear that they are exempted from 9 & 10. 17:29:57 Glenda: I thought it was covered by "Important Information" but we need to have a specific exemption for that. 17:30:08 rrsagent, make minutes 17:30:08 I have made the request to generate http://www.w3.org/2016/11/29-wai-wcag-minutes.html jeanne 17:30:37 by all! 17:30:52 bye 17:31:18 Bye 17:31:45 KimD has left #wai-wcag 18:00:59 clapierre has joined #wai-wcag 18:39:20 clapierre has joined #wai-wcag 19:13:17 clapierre1 has joined #wai-wcag 20:16:57 clapierre has joined #wai-wcag 20:18:16 clapierre has joined #wai-wcag 23:03:24 clapierre has joined #wai-wcag