14:26:11 RRSAgent has joined #wai-wcag 14:26:11 logging to http://www.w3.org/2016/07/05-wai-wcag-irc 14:26:13 RRSAgent, make logs public 14:26:15 Zakim, this will be WAI_WCAG 14:26:15 ok, trackbot 14:26:16 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:26:16 Date: 05 July 2016 14:26:25 zakim, agenda? 14:26:25 I see 1 item remaining on the agenda: 14:26:26 5. WCAG codename Survey (from last week : [from Joshue108] 14:26:33 zakim, clear agenda 14:26:33 agenda cleared 14:26:39 Chair: Joshue 14:27:21 Scribe List: https://www.w3.org/WAI/GL/wiki/Scribe_List 14:28:35 agenda+ New Task Force Exchange 14:28:49 agenda+ SC Numbering proposals team/work. 14:28:56 agenda+ Success Criteria acceptance criteria. 14:29:06 agenda+ Submitting new SCs (non-group) 14:52:05 allanj has joined #wai-wcag 14:53:47 laura has joined #wai-wcag 14:55:15 alastairc has joined #wai-wcag 14:59:00 Greg has joined #wai-wcag 14:59:22 Makoto has joined #wai-wcag 15:03:01 present+ Laura 15:03:16 Scribe: Laura 15:03:23 present+ Makoto 15:03:53 Rachael has joined #wai-wcag 15:05:14 Sarah_Swierenga_ has joined #wai-wcag 15:05:34 JF has joined #wai-wcag 15:05:48 Zakim, next item 15:05:48 agendum 1. "New Task Force Exchange" taken up [from Joshue108] 15:06:20 Present+ JF 15:06:31 https://www.w3.org/WAI/GL/wiki/Task_Force_Exchange 15:06:35 JOC: New hub for TF work 15:06:41 present+ Joshue108 15:06:48 Present+ Rachael 15:06:53 present+ alastairc 15:06:57 Present+ Greg_Lowney 15:07:10 davidmacdonald has joined #wai-wcag 15:07:10 present+ Sarah_Swierenga 15:07:22 present+ Davidmacdonald 15:08:06 AC: Where is the SC map? 15:08:12 kirkwood has joined #wai-wcag 15:08:41 present+ jeanne 15:08:45 JOC: we don’t have a map. They are scattered now. They will end up on this page. 15:08:54 + kirkwood 15:09:00 LV: http://w3c.github.io/low-vision-a11y-tf/requirements.html 15:09:31 Mobile: https://w3c.github.io/Mobile-A11y-Extension/ 15:10:07 LVTF: Gap 15:10:11 COGA: https://rawgit.com/w3c/coga/master/gap-analysis/ 15:10:14 https://w3c.github.io/low-vision-a11y-tf/WC-UA-alignment.html 15:10:16 q? 15:10:54 JF: listed 3 URLS 15:11:24 Faciliators will update that page 15:11:28 q? 15:12:06 AC: Should we be reviewing them? 15:12:13 JOC: Yes. 15:12:47 JOC: SC don’t need Techniques. 15:13:02 q? 15:13:19 Zakim, next item 15:13:19 agendum 2. "SC Numbering proposals team/work." taken up [from Joshue108] 15:13:47 https://www.w3.org/WAI/GL/wiki/WCAG_2.1_SC_Numbering 15:14:11 JOC: Suggestion to have a team look at this. 15:14:25 JF: Go to that URL. 15:14:34 q 15:14:37 q? 15:14:40 LVTF: SC in development, changes weekly. https://github.com/w3c/low-vision-SC/issues 15:16:37 JF: Concern regarding Policy numbering. 15:16:55 q? 15:16:57 …Kim has provided guidiance. 15:17:22 present+ MichaelC 15:17:27 Legislative approach: https://www.w3.org/WAI/GL/wiki/WCAG_2.1_SC_Numbering#Legislative_approach_.28or_.E2.80.9Cwhen_to_try_and_assign_numbers.E2.80.9D.29 15:17:48 JF: Should read Legislative approach. 15:17:51 Ryladog has joined #wai-wcag 15:18:01 q? 15:18:15 Present+ Katie_Haritos-Shea 15:18:23 -1 to making a binding discussion yet, before we´ve even seen the set of SC we´re likely to need to incorporate 15:18:27 q+ 15:18:59 JOC: good feedback. 15:19:26 AC: We were leaning toward #2 15:19:46 +1 to Alastair 15:20:31 q? 15:20:38 q- 15:20:38 JOC: Model 2 less likely to break stuff. 15:21:32 I am also leaning towards model 2 15:21:41 JF: May want to rework some of the exixting SC. Kim’s would accommodate that. 15:22:47 …minimise impact to legislation. 15:22:53 q+ 15:23:07 adam_solomon has joined #wai-wcag 15:23:11 JOC: seems to be most robust. 15:23:38 …would like to walk though models. 15:23:39 q? 15:24:18 MC: may be premature for formal decisions. 15:24:40 ack ryla 15:24:48 JOC: no decisions now. We are just discussing. 15:25:14 q? 15:25:18 q+ 15:25:40 ack me 15:26:08 present+ adam_solomon 15:26:37 JOC: Let’s look at model. 15:26:59 …(Model 1) 4 tier numbering 15:27:55 …Pros: Can keep and view the basic structure of the numbering in WCAG. 15:28:16 …Cons: Four layers seems a bit inelegant, and may confuse newcomers 15:28:31 …There may be a feeling that the forth level is kind of a second class citizen 15:28:45 …In statutes and regulations, adding another level of numbers generally indicates that the new section 15:28:51 q? 15:28:51 q+ 15:29:04 JF: Seems like a partial solution. 15:29:18 ack greg 15:29:23 …maybe a subsection. 15:29:48 Greg: May have impact on tools. 15:30:55 q? 15:31:29 JF: not a major show stopper. 15:32:07 JOC: (Model 2) Add a new section to the end of each existing Guideline that will have new SCs 15:32:24 …Put all the new SCs at the end of their respective Guidelines 15:32:29 Tools that track, reference, or mirror the standards may have the assumption that each level has a consistent meaning, and that all items of the same meaning will have the same syntactic level. That is, all GL would have two fields, while all SC have three. Adding a fourth level would require changes to those tools. 15:32:58 …Wonder about mapping. 15:33:16 MC: There is an implicit mapping 15:33:19 Q+ 15:33:55 ack JF 15:34:29 q+ 15:34:46 JF: Filtering could address levels. 15:35:08 q+ to say that anecdotally people outside the WG do not realize that they are organized by level. 15:35:14 ack me 15:35:18 MC: No expicit mapping. 15:35:59 JOC: nubering seems arbitrary. 15:36:19 JF: that’s the point. 15:36:43 …filtering will solve the issue. 15:37:17 q+ 15:37:44 q+ 15:38:03 …like’s that everything new is added to the bottom 15:38:41 JOC: Pros There are advantages to sticking with 3 levels of numbers. 15:38:53 new Success Criteria numerically as part of an expanding list allows for easier identification of new SC 15:39:14 …Cons - have some new AA SCs which come AFTER the AAA SCs from 2.0 15:39:23 … may be a tendency to disregard the new SCs that appear AFTER the AAA's 15:39:38 …We do not want that. 15:40:09 … new SCs should not be disregarded 15:40:18 q? 15:40:19 q? 15:40:37 DM: This is my preferred one. 15:40:52 ack jeanne 15:40:52 jeanne, you wanted to say that anecdotally people outside the WG do not realize that they are organized by level. 15:41:44 +1 to Jeanne 15:41:50 JS: Asked around about this. No one new about levels. 15:42:08 +1 to Jeanne 15:42:22 …Changing numbering would be a problem. 15:42:59 q+ 15:43:36 Q+ 15:43:51 …thought that they were in the order developed. Did not want renumbering. 15:43:56 lost connectivity, comming back 15:43:56 back 15:43:57 ack rayla 15:44:00 ack ry 15:44:11 Katie: Think we should document. 15:44:50 ack greg 15:44:59 If items are not in numeric order, readers would have to use a software Search function to find a specific SC, and those who are reading on paper could have great difficulty. It may also trick readers into thinking an SC doesn’t exist, when they can’t find it where they expect it to be. 15:45:09 Greg: Don’t greatly dislike #3 15:45:29 +1 to Jeanne's comment: people don't tend to remember/recognise multiple layers of categorisation. The principle categorisation is by POUR, secondary categorisation is less (not?) important. 15:45:30 …may need to use a search function. 15:46:12 …a lot of people don’t think ordering important. 15:46:29 Think we should document in model 2 under Cons that "We understand that most accessibility assessment reports today are delivered as a document of some kind - but we feel filtering will be able to address this when moved to automated systems" 15:46:39 q? 15:46:46 ack rach 15:47:32 Rachael: benefit in knowing what is a new SC 15:47:43 …advantave to #1 15:47:45 +1 to identifying new SC as 2.1, regardless of the numbering scheme chosen 15:47:50 ARIA 1.1 does that 15:48:37 MC: would be complementary. 15:49:19 q? 15:49:22 Katie: add an identifier. 15:49:22 ack JF 15:49:32 zakim, queue? 15:49:32 I see no one on the speaker queue 15:49:37 zakim, agenda? 15:49:37 I see 3 items remaining on the agenda: 15:49:38 2. SC Numbering proposals team/work. [from Joshue108] 15:49:38 3. Success Criteria acceptance criteria. [from Joshue108] 15:49:38 4. Submitting new SCs (non-group) [from Joshue108] 15:50:35 JF: We look at the levels. Webdevs don’t do the severity levels. 15:51:08 I prefer Model2 as it doesn't change the existing numbering. In Japan, we will keep using WCAG 2.0 until WCAG 2.1 will be approved as ISO standard. But global companies maybe use both. So I don't want renumbering. 15:51:33 JOC: Model 4) Introduce a level marker to SC numbers 15:51:54 …would change things dramatically. 15:52:13 …Causes a renumbering of all the SC from WCAG 2.0 15:52:27 JOC: Model 5) Renumber all the SC 15:52:53 …Not practical. 15:53:41 q? 15:53:59 MC: Wouldn’t discard this model. 15:54:17 …could do a mapping. 15:54:46 …has a precendent and has value. 15:54:53 Q+ 15:55:29 …SC have both handles and ID’s 15:55:50 …numbers don’t mean much. 15:56:26 q+ 15:56:27 JOC: Model 6) Remove SC numbers altogether 15:56:44 I could see removing numbers in Silver, but I would be opposed to removing numbers in 2.1 15:56:49 JF: I don’t like it. Not backwards comatable. 15:57:40 q? 15:57:45 ack jf 15:57:57 MC: numbering is just a label. 15:58:23 MC: Think we should consider it. 15:58:30 q? 15:58:35 ack greg 15:59:13 Greg: Removing numbering potentially difficult for international and non-English communication that use localized handles 15:59:58 MC: IDs are English centic. 16:01:05 JF: Would be alot of work to change all support materials that include numbers. 16:01:35 …we have attached importance to numbers. 16:01:39 Some take aways are 1* Model 2 is popular 2* If there was an identifier for new SCs this would be helpful 3* There may be value in renumbering all together, this is not off the table. 16:01:57 q? 16:02:06 Zakim, next item 16:02:06 agendum 3. "Success Criteria acceptance criteria." taken up [from Joshue108] 16:02:48 Thanks to all who have contributed. 16:02:56 https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria 16:03:49 JOC: Walk though. 16:04:03 …7 items. 16:04:08 jamesn has joined #wai-wcag 16:04:11 … Success criteria are testable. 16:04:20 rrsagent, make minutes 16:04:20 I have made the request to generate http://www.w3.org/2016/07/05-wai-wcag-minutes.html jamesn 16:04:28 …Success criteria describe the specific condition required to meet the criteria 16:04:35 Success criteria must apply across technologies 16:04:42 …Ensure that the conformance requirements are written as simply as possible. 16:04:50 … Success criteria will utilize the WCAG 2.0 A/AA/AAA level structure 16:04:54 q+ 16:05:00 …Success criteria need to be as broad as possible 16:05:11 …Success criteria must be applicable to all content, unless specific exceptions are included 16:05:20 Q+ 16:05:29 q+ to say these are overall requirements for SC, but think we need more specific acceptance criteria about how SC should be structured, how wordy, use of bullets, notes and if they´re normative, etc. 16:05:36 ack mich 16:05:37 MichaelC, you wanted to say these are overall requirements for SC, but think we need more specific acceptance criteria about how SC should be structured, how wordy, use of bullets, 16:05:37 ... notes and if they´re normative, etc. 16:05:43 q+ 16:05:58 …Are these coherent? 16:06:38 MC: these are overall requirements for SC, but think we need more specific acceptance criteria about how SC should be structured, how wordy, use of bullets, notes and if they´re normative, etc. 16:06:47 q+ to ask how we want to handle definition changes. 16:08:19 MC: Not sure if notes are normative. 16:09:03 JOC: can you flesh these our in the Wiki. 16:09:09 MC: Yes. 16:09:10 ack JF 16:09:25 q+ 16:10:16 JF: Maybe some SC may have to be tech dependant. 16:10:33 Success criteria need to be as broad as possible, but specific enough not to become a 'catch-all' for any given requirement. 16:10:39 ack rylado 16:10:44 Katie: suggestion for #6. 16:11:08 Q+ to say I'd also like to see a definition of what "Content" actually means 16:11:18 … will update Wiki. 16:11:20 ack jeanne 16:11:20 jeanne, you wanted to ask how we want to handle definition changes. 16:12:18 JS: How to handle defiinition changes? ie points to pixels 16:13:40 JOC: Good question. We will have to think about it. 16:14:00 ACTION: On Josh to discussion need for definition changes in WCAG at editors meet. 16:14:00 Error finding 'On'. You can review and register nicknames at . 16:14:18 ACTION: On Josh to discussion need for definition changes in WCAG at editors meet. 16:14:18 Error finding 'On'. You can review and register nicknames at . 16:14:18 ACTION: Joshue to discuss need for definition changes in WCAG at editors meet. 16:14:18 Created ACTION-328 - Discuss need for definition changes in wcag at editors meet. [on Joshue O Connor - due 2016-07-12]. 16:14:40 q? 16:14:42 https://www.w3.org/TR/WCAG20/#guidelines 16:14:42 ack dav 16:15:00 ACTION: Josh and AWK to work out a way to deal with definition changes. 16:15:01 Created ACTION-329 - And awk to work out a way to deal with definition changes. [on Joshue O Connor - due 2016-07-12]. 16:15:10 DM: Notes are normative. 16:15:56 JOC: Maybe they shouldn’t be. 16:16:03 JOC: Should these notes be normative at all? 16:16:38 MC: Notes are normative. But some confusion. 16:16:57 …need to look at it. 16:17:21 q+ 16:17:33 ack jf 16:17:33 JF, you wanted to say I'd also like to see a definition of what "Content" actually means 16:17:35 MC: Would like to propose no notes. 16:17:35 ack jf 16:18:16 JF: What does “content” actually mean? 16:19:04 content (Web content) 16:19:06 information and sensory experience to be communicated to the user by means of a user agent, including code or markup that defines the content's structure, presentation, and interactions 16:19:32 MC: we need to disscuss it. 16:19:51 JOC: Silver discussion. 16:20:26 ack david 16:20:40 DM: we have a definition of content. 16:21:16 q+ 16:21:44 MC: SC’s may change. 16:22:06 JF: Will need to call it out. 16:22:23 ack me 16:22:37 JOC: They could well change. 16:22:58 …as long as we don’t reduce requirements. 16:23:21 MC: many won’t change. 16:23:38 JOC: We should address needs. 16:23:55 …numbering is secondary. 16:23:58 q? 16:24:06 Zakim, next item 16:24:06 agendum 4. "Submitting new SCs (non-group)" taken up [from Joshue108] 16:25:14 JOC: How do we make it easier for people? 16:25:27 q+ 16:25:32 JF: Suggest a form. 16:25:50 JOC: Let’s think about it. 16:26:03 ack dav 16:28:16 q+ 16:28:34 DM: doesn’t seem to be a huge interest in using previous forms form outside folks. 16:28:37 ack me 16:29:20 zakim, close queue 16:29:20 ok, Joshue108, the speaker queue is closed 16:29:33 MC: process may be difficult. We should be open to SC from outside WCAG. 16:29:56 JOC: maybe Github. 16:31:06 rrsagent, make minutes 16:31:06 I have made the request to generate http://www.w3.org/2016/07/05-wai-wcag-minutes.html laura 16:31:12 thanks Laura for scribing! 16:31:25 Youre welcome, Josh 16:31:32 trackbot, end meeting 16:31:32 Zakim, list attendees 16:31:32 As of this point the attendees have been JF, steverep, alastairc, kirkwood, Laura, marcjohlic, Kathy, Joshue108, MichaelC, KimD, jeanne, Katie_Haritos-Shea, jon_avila, Makoto, 16:31:35 ... Rachael, Greg_Lowney, Sarah_Swierenga, Davidmacdonald, adam_solomon 16:31:40 RRSAgent, please draft minutes 16:31:40 I have made the request to generate http://www.w3.org/2016/07/05-wai-wcag-minutes.html trackbot 16:31:41 RRSAgent, bye 16:31:41 I see 4 open action items saved in http://www.w3.org/2016/07/05-wai-wcag-actions.rdf : 16:31:41 ACTION: On Josh to discussion need for definition changes in WCAG at editors meet. [1] 16:31:41 recorded in http://www.w3.org/2016/07/05-wai-wcag-irc#T16-14-00 16:31:41 ACTION: On Josh to discussion need for definition changes in WCAG at editors meet. [2] 16:31:41 recorded in http://www.w3.org/2016/07/05-wai-wcag-irc#T16-14-18 16:31:41 ACTION: Joshue to discuss need for definition changes in WCAG at editors meet. [3] 16:31:41 recorded in http://www.w3.org/2016/07/05-wai-wcag-irc#T16-14-18-2 16:31:41 ACTION: Josh and AWK to work out a way to deal with definition changes. [4] 16:31:41 recorded in http://www.w3.org/2016/07/05-wai-wcag-irc#T16-15-00