14:29:49 RRSAgent has joined #wai-wcag 14:29:49 logging to http://www.w3.org/2015/09/08-wai-wcag-irc 14:29:51 RRSAgent, make logs public 14:29:53 Zakim, this will be WAI_WCAG 14:29:53 I do not see a conference matching that name scheduled within the next hour, trackbot 14:29:54 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:29:54 Date: 08 September 2015 14:30:00 zakim, agenda? 14:30:00 I see 1 item remaining on the agenda: 14:30:01 5. Github issues and work progress - survey item3,4,5,6 https://www.w3.org/2002/09/wbs/35422/Sept1st2015/ [from Kenny] 14:30:18 zakim, clear agenda 14:30:18 agenda cleared 14:30:48 agenda+ Announcements 14:30:57 agenda+ Techniques and understanding update 14:31:07 agenda+ Survey on https://www.w3.org/2002/09/wbs/35422/09082015/ 14:31:20 agenda+ Discussion on decision policy, see link on http://www.w3.org/WAI/GL/decision-policy 14:31:27 zakim, agenda? 14:31:27 I see 4 items remaining on the agenda: 14:31:28 1. Announcements [from Kenny] 14:31:28 2. Techniques and understanding update [from Kenny] 14:31:28 3. Survey on https://www.w3.org/2002/09/wbs/35422/09082015/ [from Kenny] 14:31:29 4. Discussion on decision policy, see link on http://www.w3.org/WAI/GL/decision-policy [from Kenny] 14:55:49 AWK has joined #wai-wcag 14:56:36 zakim, agenda? 14:56:36 I see 4 items remaining on the agenda: 14:56:37 1. Announcements [from Kenny] 14:56:37 2. Techniques and understanding update [from Kenny] 14:56:37 3. Survey on https://www.w3.org/2002/09/wbs/35422/09082015/ [from Kenny] 14:56:38 4. Discussion on decision policy, see link on http://www.w3.org/WAI/GL/decision-policy [from Kenny] 14:56:50 Chair: AWK 14:57:16 Scribe: Bruce_Bailey 15:01:45 present+ Laura 15:02:06 present+ Bruce_Bailey 15:02:25 present+ AWK 15:02:37 regrets+ Louis_Cheng 15:02:48 Present+ David_MacDonald 15:05:20 jon_avila has joined #wai-wcag 15:05:30 present+ EricE 15:05:33 present+ Kenny 15:05:41 AWK: welcome 15:05:46 present+jon_avila 15:06:03 s/present+jon_avila/present+ jon_avila/ 15:06:36 AWK: appologies for late agenda 15:06:51 zakim, take up next item 15:06:51 agendum 1. "Announcements" taken up [from Kenny] 15:07:14 http://w3c.github.io/wai-wcag-quickref/ 15:07:17 Erik: talking about quick ref 15:07:24 adam_solomon has joined #wai-wcag 15:07:36 DanielFrank has joined #wai-wcag 15:07:38 EricE: lots of changes under hood 15:07:45 taking up UI 15:08:00 what you cannot see is tagging, look at footer tab 15:08:12 rough preview for now 15:08:27 hoping for less text 15:08:35 https://github.com/w3c/wai-wcag-quickref/wiki/tagging-success-criteria 15:08:38 multiple working groups provinging input 15:08:51 githup wiki page provided for input please 15:09:27 request for wg members take look at list, think of other text and tags that could be useful 15:09:43 q+ to ask if you´re maintaining the tags independently or if you want them in the sources - soon, or eventually 15:09:44 are any tags redundant? are they properly associated? 15:10:08 current some tags only associated with single sc -- so we may not be keeping that tag 15:10:47 MC: tags look good, but are you keep separate track of tags? 15:10:58 Kathy has joined #wai-wcag 15:11:06 EE: currently externally managed, but we may want to roll into jason 15:11:07 present+ 15:11:25 present+ 15:11:26 EE: would be helpful to incorporate into Json 15:11:37 MC: Other peoples opinion? 15:11:49 present+ Kathy 15:11:55 MC: Majority view is what folks want. 15:12:02 present+ adam_solomon 15:12:16 AWK: Could see tags getting added ad hoc, so need capability to edit 15:12:46 AWK: Would want to consolidate, that would editorial. Need to keep tags in mind as we go forward 15:12:55 EE: tags just for SC at present 15:13:11 EE: very much tags are under control of group 15:13:27 MC: tags for techniques might be useful in future 15:13:49 MC: we would want list of tags so typos do not accidently introduce new tags 15:14:02 zakim, queue? 15:14:02 I see MichaelC on the speaker queue 15:14:06 EE: understood, again tags just for SC for now 15:14:08 ack mi 15:14:08 MichaelC, you wanted to ask if you´re maintaining the tags independently or if you want them in the sources - soon, or eventually 15:14:23 David M: Q about tab order on new layout page 15:14:51 Eric and David resolve behavior 15:15:27 EricE: Future item is some inconsistences with sources, flagging for Michael 15:15:40 https://github.com/w3c/wai-wcag-quickref/issues/26 15:15:44 As Eric notices, forwards to editors 15:16:13 EricE has created a list (link above), asks others to add if they notice issues. 15:16:32 Nice job eric. 15:16:34 AWK: Anythink else? 15:16:49 AKW: Kudos 15:16:52 s/Anythink/Anything/ 15:17:24 AWK: Also unders announcements, charter still under development 15:17:33 Resolving open comments on charter 15:17:54 Hopefully next week. 15:18:13 WG still operating under extended charter for next few weeks. 15:18:27 AWK: Anything else? 15:18:50 David_M: Asks if more discussion beyond WCAG extensions? 15:19:32 AWK: Commenters raised. Further work with ATAG and UAAG also under discussion. 15:19:49 Lots of questions still, more questions than answers at the moment. 15:20:41 MC: Exploring options. Significant administrative issued. Major change would mean revisiting charter yet again. 15:21:32 MC: Plan for now is proceed as we had discussed, but think more about how to incorporate more ideas for Charter and future scope. 15:22:17 This is third proposed charter, so we really don't want forth attempt. We want to give all due consideration for future ideas. How does that sound? 15:22:27 DavidM: Sounds good. 15:22:56 Jon Availa: Points out how much could be added to future guidelines, but we need mobile extensions now. 15:23:27 s/Availa/Avila 15:23:49 MC: The more feedback we get from task forces, the better idea we have how to incorporate ideas and suggestions from tast forces. 15:24:11 A discussion paper on turning advice to Success Criteria in mobile http://w3c.github.io/Mobile-A11y-TF-Note/TouchProposal_Discussion.html 15:24:30 MC: Mobile is ahead of other groups, but even there we do not have concrete fix. One problem is indentified. 15:24:58 Kathy shared TF notes so far 15:25:38 DavidM: Some language looks like it could be phrased as SC but there is still a lot of controversy 15:26:29 DM: Discussion is still going on with regard to how universal mobile SC are, as compared to current SC. So they may be more like best practices. 15:26:44 DM: Changing the WCAG model would not be a good thing. 15:27:41 AWK: People like what Michael has been saying. We seem to have consensus to keep moving current charter through, look more or different in future. 15:27:55 Josh on-line, checks in. 15:28:48 AWK: Reviewing options for charter. One option for future charter is to get away from extensions. 15:29:33 DavidM: Could also work in recommendations from task force into techniques documents. That would be closer to normative. 15:30:03 MC: Reminds group that techniques are not normative, and we do not want contrived mappings. 15:30:29 DavidM: There may still be oportunities to work taskforce advice into techniques. 15:30:49 AWK: Work will continue on Charter. 15:31:31 AWK: Working group approval would be needed for any non-editorial changes, including a 3rd charter vote. 15:31:44 AKW: Expect some editorial. 15:31:57 zakim, next item 15:31:57 agendum 2. "Techniques and understanding update" taken up [from Kenny] 15:32:24 jon_avila has joined #wai-wcag 15:32:38 zakim, list attendees 15:32:38 As of this point the attendees have been EricE, Laura, AWK, Srinivasu_Chakravarthula, Kathy, jon_avila, kenny, adam_solomon, David_MacDonald, Katie, Haritos-Shea, MichaelC, 15:32:41 ... Bruce_Bailey 15:32:43 s/into techniques/into failure techniques 15:32:54 s/AKW/AWK 15:33:02 AWK: Check w/ MC on schedule for publishing. 15:33:40 MC: Held up on coordinating announcements, which need an approval cycle, initiating this week. 15:33:53 present+ Josh 15:34:13 Ryladog has joined #wai-wcag 15:34:18 AWK: From a working group perspective, could be anytime. Wording on announcement more complicated than edits this time around. 15:34:28 zakim, next item 15:34:28 agendum 3. "Survey on https://www.w3.org/2002/09/wbs/35422/09082015/" taken up [from Kenny] 15:34:28 Present+ Katie Haritos-Shea 15:34:33 https://www.w3.org/2002/09/wbs/35422/09082015/results 15:35:18 AWK: Survey was a little late. Only one item looks completed. 15:35:28 Work through as we go on call. 15:35:30 https://github.com/w3c/wcag/issues/110#issuecomment-131810378 15:35:43 TOPIC: Issue 110 Technice G65 15:36:13 Issue 110: Update G65 breadcrumb technique to follow the HTML5 pattern? 15:36:47 Laura asked to summarize. 15:37:02 Mic problems agian. 15:37:19 G65: http://www.w3.org/TR/WCAG20-TECHS/G65.html 15:38:01 AWK: In description asks to add arrow to last paragraph of description and providing an example 3 as shown git hub page 15:38:17 Uses aria lable for breadcrumb and new resource. 15:38:33 AWK: Only survey comment is to add indent for readabiltiy. 15:38:53 s/readabiltiy/readability/ 15:39:07 Katike H: Likes it. 15:39:28 AWK: Notes new example is quite a bit more detailed than other. 15:40:04 New example is just for 248. Does not seem like a major change. Calls for objections? 15:41:03 RESOLUTION: Accept as proposed (including code indentation) 15:41:08 s/248/SC 2.4.8 15:41:15 Thank you. 15:41:28 https://www.w3.org/2002/09/wbs/35422/09082015/results#xq8 15:41:54 ISSUE: 114 Example #2 of F22 seems to stretch SC 3.2.5 requirement 15:41:54 Created ISSUE-45 - 114 example #2 of f22 seems to stretch sc 3.2.5 requirement. Please complete additional details at . 15:42:32 AWK: Salish had question, AKW clarified in response and change. Salish liked it. 15:43:18 AWK: Clarify that just because a user clicks on a link, that *could* be a change in context 15:44:00 s/ISSUE: 114 /TOPIC: #114 / 15:44:02 TOPIC survey 2nd question 114 Example #2 of F22 seems to stretch SC 3.2.5 requirement 15:44:19 trackbot, close issue-45 15:44:19 Closed issue-45. 15:44:23 rrsagent, make minutes 15:44:23 I have made the request to generate http://www.w3.org/2015/09/08-wai-wcag-minutes.html MichaelC 15:44:28 DavidM: adds some context that originally some discussion 15:44:33 s/Katie Haritos/Katie_Haritos 15:44:57 Some people assert that clicking a link that brings up new window is change in context 15:45:10 AWK: Other institutional memory on this? 15:45:27 AWK: Notes that current wording mentions change of view port 15:45:33 h+ 15:45:39 q+ 15:45:43 q+ 15:46:02 MichaelC: Remembers Ben arguing case. 15:46:16 MichaelC: Recalls notification 15:46:58 Bruce recalls that is where advance notice to user is required. 15:47:13 ack ry 15:47:45 KatieH: Wanted notice to users if behavior was not clear 15:47:48 q- 15:48:49 AWK: Asks David if link opening new window in 3.2.5 was not a problem. 15:49:21 DavidM: Consensus at time was to live with it because screen reading software announces new link. 15:49:50 AWK: Who benefits if this is interpreted as new requirement? 15:50:42 DavidM: Advance notice helps screen reader users, as well as people with cognitive disabilties. Nice for everyone. 15:51:16 DavidM: Example Eric uses with wikipedia off-site icon -- but indicated new window. 15:51:20 q+ 15:51:49 AWK: what about low vision user? Screen reader use case heavily discussed 15:52:11 Bruce asks to check WCAG text 15:52:41 Jon Availa: Some consensus 3.2.5 applies 15:53:06 s/Availa/Avila 15:53:20 AWK: There is A A A item for this -- so implies is not requirement for A A 15:53:57 JonA: No failure associated with no advance notice of new window 15:54:39 MichaelC: Recalls that SC got morphed to capture tabbing through page 15:54:59 Katie: Definition of link captures this. 15:55:30 AWK: Asks for clarification if 3.2.2, want to keep conversation on 3.2.5 15:56:06 MichaelC: Thinks David is correct, at A A A need advance notice. 15:56:32 At A A with 3.2.5 link opening new window is permitted 15:57:16 Specific wording on 3.2.5 does not explicit notice that link will be new window. 15:57:53 DavidM: New window opening is not good, but not prohibited 15:58:51 MichaelC: We do not have text in techniques that behavior is okay maybe because we did not want to encourage it. 15:59:26 AWK: New technique text seems to contradict earlier conclusion that new window is tolerated. 15:59:34 F22: http://www.w3.org/TR/2015/NOTE-WCAG20-TECHS-20150226/F22 16:00:20 MichealC: Technique documents reflect intent at the time written, could be rewritten to address confusion. 16:00:36 JonA: If we make this edit, we need to change the name. 16:01:01 MichealC: Could also make new technique, but we should defer on that. 16:01:19 http://www.w3.org/TR/2015/NOTE-UNDERSTANDING-WCAG20-20150226/consistent-behavior-no-extreme-changes-context.html 16:01:46 AWK: Current proposal under discussion is to change technique in Understanding document for F22. 16:02:05 AWK: quotes new text 16:02:35 AWK: This is a clarification within understanding document 16:02:39 text I read comes from: https://github.com/w3c/wcag/issues/114#issuecomment-135866669 16:03:01 MichaelC: Think we can work this out. 16:03:43 AWK: Does everyone agree at A A A user needs advance notification? 16:03:54 No objections. 16:04:13 s/MichaelC: Think we can work this out./DavidM: Think we can work this out./ 16:04:24 q+ 16:04:54 Bruce checks for 3.2.5 and A A A 16:05:20 MichaelC: Wording is complex, but does say what we want. 16:06:07 JonA: This raises some questions with 3.2.2. Making it explicit for 3.2.5 makes the poor behavior okay for 3.2.2 16:06:17 rrsagent, make minutes 16:06:17 I have made the request to generate http://www.w3.org/2015/09/08-wai-wcag-minutes.html MichaelC 16:06:55 DavidM: Thinks other examples with form fields makes this change okay. User has feedback where they are changing things. 16:07:09 changes of context definition: http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.html#context-changedef 16:07:38 AWK: As Katie mentioned, selecting links not invoking 3.2.2 16:08:13 JonA: So long as we are making distinction with regards to settings helps this. We may need to add that to 3.2.2 16:08:59 Katie: Problem is that what is perceived as link nowadays has morphed quite abit from when 3.2.2 was first written. Overlays come into effect. 16:09:33 AWK: Cites from understanding for 3.2.2 that mentions controls in contrast to links 16:09:48 JonA: Still a little ambiguous 16:10:14 DavidM: Gives example with forms where you know you have initiated activity 16:11:29 JonA: On a link and press enter invokes modal dialog box, is that not a change of context without opening a new widow? It is a new viewport. Understanding says that not all changes of content are changes of context. 16:12:14 DavidM: Mentions 2008 context, users were still prepared that they were is some kind of dialog box with changes related to that. 16:12:34 JonA: Asks why is this different for 3.2.5? 16:13:13 Josh: Distinction between initated and non-initiated changes of context seem like a continuim 16:13:59 DavidM: At 3.2.5 need advance notice, while 3.2.2 can be infered from being on a link. 16:14:48 AWK: Resonable question, but should we taking something out of 3.2.5? Really doubt there would be consensus for that. Could revisit that later, after new charter. 16:14:58 JonA; Agree to differ. 16:15:08 s/JonA;/JonA:/ 16:15:32 DavidM: Agree we can defer larger conversation. Safe to make clarification now. 16:16:08 AWK: Agrees that proposed text is complex, but all discussion seems like we can keep it. Any objections as proposed? 16:16:52 RESOLUTION: Accept issue 114 as proposed. 16:17:43 TOPIC: issue 99 16:17:53 https://www.w3.org/2002/09/wbs/35422/09082015/results#xq9 16:18:04 Issue 99: Update PDF14 to be in sync with PDF/UA and also ensure footer information is available in other means 16:18:41 AWK: JonA has good point about links in footer. 16:18:55 AWK: Bruce had editorial suggestion. 16:19:33 AWK: Asks DavidM (technique author) about artifacting footers with links. Is current wording a problem? 16:20:17 DavidM: Thinks that is okay, failure is to UA, not WCAG SC 16:21:18 DavidM: We are encouraging artifacts, and we can catch other failures 16:21:37 JonA: What should we say about links in footers? 16:22:08 DavidM: Do we need to list out things PDF/UA might not catch? 16:23:03 AWK: Could be different opinions. What about running footers with link? 16:23:43 DavidM: PDF/UA just says to artifact headers and footers, so it can be too broad 16:24:19 JonA: PDF/UA may not have considered edge cases, so links in footers may be overlooked. 16:24:42 JonA: There are updates expected soon for PDF/UA 16:25:37 JonA: Some of the problems come down to UA issues -- it would be nice if UA gave selective access to running footers in PDF. 16:26:18 AWK: Could be a future issues to revisit PDF technique 14. Do we like what we have here well enough? 16:27:27 AWK: Should be a fairly simple failure: You have followed advice in PDF/UA and made footer invisible to AT and have footer information available elsewhere (e.g., page numbers) 16:27:44 Here is pdf14 rewrite 16:27:47 JonA: Asks for clarification that this applies only to running footers? 16:28:25 here is 14 https://github.com/DavidMacDonald/wcag/commit/a98f5313076676730c07cdb3110ce28b9e3e44e7 16:28:33 AWK: Proposed text does not specify running or no. Just says if hidden and not otherwise available, then a failure. 16:28:47 JonA: Seems reasonable as written then. 16:29:31 AWK: Asks for objections 16:30:08 DavidM: Checks that this rendering is not available as formated HTML. 16:30:24 AWK: New work flow has this artifact 16:31:05 s/artifcact/effect that final formal not in HTML/ 16:31:23 [12:31] s/artifact/effect that final formal not in HTML/ 16:31:51 RESOLUTION: Leave open 16:32:19 AWK: Since a pull-request we need text cleaned up completely before accepting. 16:32:29 bye 16:32:42 trackbot, end meeting 16:32:42 Zakim, list attendees 16:32:42 As of this point the attendees have been EricE, Laura, AWK, Srinivasu_Chakravarthula, Kathy, jon_avila, kenny, adam_solomon, David_MacDonald, Katie, Haritos-Shea, MichaelC, 16:32:45 ... Bruce_Bailey, Josh 16:32:50 RRSAgent, please draft minutes 16:32:50 I have made the request to generate http://www.w3.org/2015/09/08-wai-wcag-minutes.html trackbot 16:32:51 RRSAgent, bye 16:32:51 I see no action items