14:58:44 RRSAgent has joined #wai-wcag 14:58:44 logging to http://www.w3.org/2013/09/24-wai-wcag-irc 14:58:46 RRSAgent, make logs public 14:58:46 Zakim has joined #wai-wcag 14:58:48 Zakim, this will be WAI_WCAG 14:58:48 ok, trackbot; I see WAI_WCAG()11:00AM scheduled to start in 2 minutes 14:58:49 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:58:49 Date: 24 September 2013 14:59:13 Kathy has joined #wai-wcag 14:59:44 David has joined #wai-wcag 14:59:45 Good morning / afternoon. I'll be on the call in a moment... 14:59:45 WAI_WCAG()11:00AM has now started 14:59:52 + +1.978.443.aaaa 15:00:02 zakim, aaaa is me 15:00:02 +Kathy; got it 15:00:32 AWK has joined #wai-wcag 15:00:33 +[Adobe] 15:00:35 + +1.650.506.aabb 15:00:40 Chair: AWK 15:00:42 Zakim, aabb is Peter_Korn 15:00:44 +Peter_Korn; got it 15:00:47 Zakim, Adobe is AWK 15:00:47 +AWK; got it 15:01:04 Zakim, who is on the phone? 15:01:04 On the phone I see Kathy, AWK, Peter_Korn 15:01:40 +David_MacDonald 15:01:51 + +1.703.861.aacc 15:01:52 Joshue108 has joined #wai-wcag 15:02:00 Regrets: Cherie 15:02:30 Zakim, aacc is Katie 15:02:30 +Katie; got it 15:02:43 +[IPcaller] 15:03:00 Zakim, IPcaller is Joshue 15:03:00 +Joshue; got it 15:03:01 zakim, [IPcaller] is Joshue 15:03:02 sorry, Joshue108, I do not recognize a party named '[IPcaller]' 15:04:01 Regrets: Alan 15:04:06 + +1.703.225.aadd 15:04:17 regrets: Kerstin 15:04:24 Zakim, aadd is Sailesh 15:04:24 +Sailesh; got it 15:05:13 Zakim, who is on the phone? 15:05:13 On the phone I see Kathy, AWK, Peter_Korn, David_MacDonald, Katie, Joshue, Sailesh 15:05:24 SaileshP has joined #wai-wcag 15:05:45 ScribeNick: Joshue 15:06:16 agenda + WCAG review of Techniques Task Force: ARIA techniques for 10 September 2013 (We need to do #4, #5, #8 only) 15:06:16 https://www.w3.org/2002/09/wbs/35422/WCAGTechs20130910/ 15:06:16 +??P4 15:06:27 agenda + 2) Review of Techs comments and ARIA techniques for September 22, 2013 15:06:27 https://www.w3.org/2002/09/wbs/35422/20130922comments/ 15:06:27 https://www.w3.org/2002/09/wbs/35422/WCAGTechs20130910/ 15:06:41 Loretta has joined #wai-wcag 15:06:58 agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2013JulSep/0140.html 15:07:17 +[IPcaller] 15:07:31 zakim, take up item 1 15:07:31 agendum 1. "WCAG review of Techniques Task Force: ARIA techniques for 10 September 2013 (We need to do #4, #5, #8 only)" taken up [from Joshue108] 15:07:39 zaki, IPCaller is Loretta 15:07:55 AWK: Lets look at the first survey. 15:08:06 zakim, mute me 15:08:07 Joshue should now be muted 15:08:25 AWK: Lets look at number 4 using aria landmarks to identify regions of a page. 15:08:38 AWK: Loretta, I'm not sure how many of these have been looked at. 15:08:53 DMacD: I've taken care of most of these, so I'm happy to discuss. 15:09:00 AWK: Ok, lets start then. 15:09:30 Loretta has joined #wai-wcag 15:09:45 DMacD: First comment from Kathleen, and I agree about using only one main region, but the spec actually doesn't require that. 15:09:54 q+ 15:10:13 DMacD: There are cases, for portals etc and may be valid use cases, would like others opinions. 15:10:35 q- 15:10:38 SP: Yes, I agree with your comment and raised it with you, and saw this covered in spec, so I agree with your change to the technique. 15:10:47 AWK: Kathy, as commenter - what do you think? 15:11:04 q+ 15:11:10 KW:I'm fine with that, for the most part there should only be one but I guess there are situations where it may happen. 15:11:24 marcjohlic has joined #wai-wcag 15:11:27 KW: I'd like the suggestion that there should only be one tho. 15:11:39 15:11:40 +Marc_Johlic 15:12:44 PK: I'm curious, is it possible to enumerate the situation that point directly to where you can have more than one, portals etc. Other samples would be useful. 15:13:12 PK: There could be iframes and times when you have a sigle URI eg. 15:13:23 DMacD: That may limit use cases. 15:13:39 PK: I'd worry about confusion amongst users where there are multiple names etc.. 15:13:42 q- 15:13:55 PK: You could point to the section of the spec maybe? 15:14:06 DMacD: Ok, I could do that. 15:14:16 DMacD: Other thoughts? 15:14:55 AWK: It sounds like its new enough, and support is still underdeveloped etc but it could be something we need to keep an eye on and maybe create failures that identify bad use cases. 15:15:00 PK: I agree, that would be nice. 15:15:26 DMacD: 15:15:55 AWK: The first part of the change sounds good. 15:16:07 DMacD: Sounds like a failure technique is a plan. 15:16:30 AWK: Lets look at Michaels comment. 15:17:39 DMacD: agrees with Michaels suggestion. 15:18:09 q+ 15:18:13 AWK: Sounds good, Michael is saying kinda what we have with headings, that they reflect the reality of the page content. 15:18:28 AWK: So the landmarks should reflect the page content. 15:19:34 DMacD: People are looking for how to do landmarks properly, so I can modify the technique and cross reference appropriate techniques etc. Yes? 15:20:04 AWK: Ok, do other people have the concern that the labelling is tangential? Or is it what you need to know to do landmarks effectively? 15:20:09 KW: I think its critical. 15:20:17 Zakim, who is on the queue? 15:20:17 I see Kathy on the speaker queue 15:20:21 ack kathy 15:20:50 AWK: David, do you think this is easy to do? 15:20:58 DMacD: Yup. 15:21:23 KW: One of the things I recommend is to make sure all of the content in the page is actually in a landmark. 15:21:48 KW: If there isn't content in a section that this functionality is being used, then they may miss it. 15:22:15 DMacD: MarcJ had mentioned this in the past, Michael was opposed to this IIRC. 15:22:39 MJ: Yes, we should include a note on this if we can - we do this inhouse in IBM. 15:22:58 DMacD: Ok, I'll do that. Anything else? 15:23:48 DMacD: We do mention SR users in the next paragraph, so don't agree with Joshs comment. 15:23:52 +q 15:23:59 zakim, unmute me 15:23:59 Joshue should no longer be muted 15:24:04 q+ 15:24:28 q+ 15:24:32 ack j 15:24:59 ack me 15:24:59 zakim, mute me 15:25:00 Joshue should now be muted 15:25:08 ack k 15:25:18 ack awk 15:25:22 JOC: I'm with the 'this is for SRs' school at the moment. 15:25:37 KW: Screen Magnifiers support it, so I don't want to narrow the definition. 15:26:16 AWK: So this is a little like headings, in that native browser support is poor but there are plug ins. This is reasonable and beneficial. 15:26:29 AWK: David you were asking for Marcs thoughts? 15:26:41 MJ: David Todd wrote the plug in! 15:27:03 MJ: There are use cases for it being used by more than SRs. Does it hurt if we don't say this? 15:27:12 ack Sa 15:27:21 DMacD: We say it in the next sentence anyway. 15:28:06 Landmark roles (or "landmarks") break the page into easy to navigate sections. Landmarks help assistive technology (AT) users orient themselves to a page and help them navigate easily to various sections of a page. 15:28:09 SP: Instead of SRs you can say its exposed to AT used by vision impaired users - Dragon doesn't get the landmarks etc. There is also a note about browser plugs but in the resources section there should be a link to one of those. 15:28:20 DMacD: Ok, I have a link here. 15:28:32 AWK: You do have a link to the browser plug? 15:28:40 DMacD: Yup, we're good? 15:28:48 AWK: Are others happy? 15:29:06 KW: It only helps those that support landmarks. 15:29:17 DMacD: Maybe we should say some. 15:29:35 LGR: When i see that I think it reads that landmarks won't help them. 15:29:46 KW: You should have other techniques at work. 15:29:54 LGR: Thats a whole AT discussion! 15:30:15 AWK: If we wanted to call it out..we could say refer to UA notes for current support. 15:30:18 LGR: + 1 15:30:26 DMacD: I'll do that. 15:30:36 zakim, queue? 15:30:36 I see no one on the speaker queue 15:30:52 DMacD: 15:31:08 AWK: Lets skip to Lorettas comment. 15:31:18 AWK: Thats already dealt with. 15:32:03 DMacD: Region mapping in JAWS has been fixed IIRC. 15:32:20 LGR: I'm reading the text and it talks about region NOT being a landmark. 15:32:36 LGR: From our technique.. 15:32:45 DMacD: Ok. 15:33:07 LGR: It's like we are throwing region in with the rest and it not sure why we doing that.. 15:33:18 DMacD: Delete sentence? 15:33:31 LGR: One of our examples uses region.. 15:33:43 DMacD: Region is technically not a landmark? 15:33:58 AWK: 15:34:15 DMacD: Sounds like its not a landmark. 15:34:40 AWK: Definitely not, I commented along these lines. We may need seperate sufficient techniques etc. 15:34:57 AWK: I don't think this technique looses out by removing it. 15:34:57 Zakim, who is on the queue? 15:34:57 I see no one on the speaker queue 15:35:06 DMacD: Ok, I'll edit that. 15:35:24 regrets + Kerstin 15:35:40 AWK: So you're going to take out example 5? 15:35:52 LGR: Also look at 4. 15:36:35 +James_Nurthen 15:36:42 MJ: Before we remove it, under the roles model - it is saying that if none of the other landmarks fit you can use it an mark it up. 15:36:48 "When defining regions of a web page, authors are advised to consider using standard document landmark roles. If the definitions of these regions are inadequate, authors can use the region role and provide the appropriate accessible name." 15:36:49 jamesn has joined #wai-wcag 15:36:56 rrsagent, make minutes 15:36:56 I have made the request to generate http://www.w3.org/2013/09/24-wai-wcag-minutes.html jamesn 15:37:00 LGR: This is where we wrote it up and could list it as related techniques. 15:37:18 15:38:15 JN: If content isn't replaced, its a UA bug. 15:38:50 JN: aria-labelledby, aria-label then native semantics, then child content if role defined as such, then title and CSS subs. 15:39:08 DMacD: Would that change stuff for us? 15:39:26 q 15:39:41 DMacD: I've refreshed it is the example ok now for everyone? 15:39:50 yup. 15:40:11 DMacD: The test procedure needs to reflect the change? 15:40:33 AWK: Yes, we should modify the test procedure. 15:40:43 DMacD: Suggestion? 15:40:53 15:41:05 zakim, queue? 15:41:05 I see no one on the speaker queue 15:41:35 AWK: If example 3, was in a page that didn't have primary, secodary etc - would be regard that as sufficient? 15:41:40 JN: Can't see why not. 15:41:48 AWK: Ok. 15:41:59 JN: Not as wrong but not as good etc. 15:42:20 DMacD: I've added some text, let me know if ok? 15:42:25 15:42:30 AWK: Ok, thats that. 15:43:03 AWK: There was another comment about using Skip - instead of navigate from Kerstin. 15:43:15 DMacD: At some stage there may be sufficient support for that. 15:43:26 AWK: Ok, I don't feel too strong about it either way. 15:43:51 DMacD: I can change that to navigate, will have something to show in ~ 10 mins. 15:44:25 AWK: I suggest if comments are address that we accept it as amendened pending DMacDs changes. 15:44:35 AWK: Any objection? 15:44:50 JN: What was conclusion on region? 15:44:59 AWK: We are doing a seperate technique for that. 15:45:03 JN: Perfect. 15:45:12 AWK: Hearing no objection - done. 15:45:41 15:45:50 AWK: James do you want an action. 15:46:05 JN: Give me a sample technique title 15:46:10 15:46:39 http://www.w3.org/WAI/GL/wiki/index.php?title=Using_the_region_role_to_identify_a_region_of_the_page&action=edit&redlink=1 15:46:44 AWK: Ok, next techniques- re invisible labels. 15:47:00 AWK: TF people, have you a sense of how many comments have been addressed? 15:47:10 LGR: I don't know who owns this! 15:47:21 LGR: Do we agree on the disposition of the comments? 15:47:39 AWK: Lets have a look. 15:48:04 AWK: Most agreed, except one ref to linked docs in the works. 15:48:59 http://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks_to_identify_regions_of_a_page 15:49:31 http://www.w3.org/WAI/GL/wiki/Using_aria-label_to_provide_an_invisible_label_where_a_visible_label_cannot_be_used 15:49:42 AWK: We're on number 5. 15:49:56 David_ has joined #wai-wcag 15:50:01 AWK: Do people not like the other examples. James, you don't like contenteditable? 15:50:12 JN: Its tricky. 15:50:19 +q 15:50:30 zakim, unmute me 15:50:30 Joshue should no longer be muted 15:51:11 zakim, mute me 15:51:11 Joshue should now be muted 15:51:34 JOC: I've found support on desktop for contenteditable and aria-label to be good. 15:51:41 JN: Yes, not so hot on mobile. 15:51:45 ack me 15:51:51 zakim, mute me 15:51:51 Joshue should now be muted 15:52:14 JN: We should put ' on mobile operating systems'. 15:52:32 AWK: Then example 2, do we have concerns? 15:52:55 JN: For me this is a little weird. 15:52:56 Zakim, who is on the queue? 15:52:56 I see Sailesh on the speaker queue 15:53:05 ack sa 15:53:46 SP: Yes, regarding these buttons - we need to be clear what kind of buttons they are - if an image then alt may be best - if a button with a value, say its name then aria-label may be better. 15:54:12 SP: So if input type = button and you need more than the generic value for AT users then the label may work ok. 15:54:20 AWK: In example 2 right? 15:54:22 SP: Yes. 15:54:38 15:55:13 SP: It could be button text, then yes - the aria-label may work. The other instance is examping on the value attribute. 15:55:21 JN: Which is what this is. 15:55:42 SP: So regarding the visual content, then the plus sign is rendered by the AT. 15:56:16 15:56:36 KW: I don't use aria-label on a button - the title att works better. 15:56:49 JN: Notes spec definition. 15:56:55 KW: We have role button there. 15:57:18 zakim, unmute me 15:57:18 Joshue should no longer be muted 15:57:50 -Peter_Korn 15:57:57 AWK: I don't like putting role= button just to make up for AT limitations. 15:58:30 AWK: If we do leave it, we need a note to say these controls have role=button added to make up for lack of support in AT. 15:58:39 JN: We don't have that in example 1, which is similar. 15:58:45 zakim, mute me. 15:58:45 Joshue should now be muted 15:58:46 korn has left #wai-wcag 15:59:06 AWK: So Kathy and others, do we need this example with others to make it good enough. 15:59:10 KW: Don't think so. 15:59:32 AWK: Discusses Bruces comments, may have been addressed. 16:00:00 zakim, unmute me 16:00:00 Joshue should no longer be muted 16:00:37 zakim, mute me 16:00:37 Joshue should now be muted 16:00:43 scribe: Kathy 16:00:49 ScribeNick: Kathy 16:02:20 AWK: Michael asks whether CSS is required 16:02:47 James: Not necessary 16:02:52 agree to removing, simplifying the CSS. 16:03:06 AWK: as long as we have the live examples, it is fine 16:03:25 Zakim, who is on the queue? 16:03:25 I see Sailesh on the speaker queue 16:03:42 James: Remove the extra stuff in example 1 16:04:40 AWK: does that make example 1 and example 2 the same 16:04:52 Sailesh: The examples are the same 16:05:01 James: Should we remove #2 16:05:07 AWK: any objections? 16:05:22 Yes 16:05:23 James: I will remove example 2 and edit example 1 16:06:04 David: Have code examples is good 16:06:17 AWK: live examples are available with the code 16:06:21 Zakim, who is on the queue? 16:06:21 I see Sailesh on the speaker queue 16:06:24 ack sa 16:06:49 Michael: The two paragraphs are not swapped but it is ok 16:07:14 q+ 16:07:18 AWK: it would make sense to switch them 16:08:44 q+ 16:08:51 Sailesh: Support for the title, sometimes the label and title will be spoken. The aria-label is the only thing that gets announced. Title will provide tooltip so that may be a better candidate in some cases 16:09:58 AWK: That gets into more nuanced discussion. This is something that you may need to do in some instances. This is sufficient. Worry about over complicating with the if then scenario 16:10:04 q+ 16:10:14 ack s 16:10:21 Zakim, who is on the queue? 16:10:21 I see David, jamesn, Loretta on the speaker queue 16:10:25 Sailesh: You would need to explain the scenarios about non-sighted and sighted users 16:11:29 David: two things. We need to add to the description about the aria-label overriding the label on the form field. It is a common error. 16:11:44 AWK: we had some text that we can pop in here 16:12:23 David: The first example, the window cannot be closed with ESC key. Suggest that we add this to the example 16:12:44 James: not required by WCAG 16:12:54 David: right, but it is a best practice 16:13:24 David: suggesting adding it to just the live example. People grab the code and expect it to be right 16:13:43 James: We would need to write a library of JavaScript code 16:13:56 AWK: we can provide maintenance on these 16:14:10 s/we can/nor can we 16:14:12 James: If we can use JQuery UI but we would need to test 16:14:27 David: I will back off on this point 16:14:44 q- 16:14:45 -Joshue 16:15:20 Zakim, who is on the queue? 16:15:20 I see David, jamesn on the speaker queue 16:15:26 ack david 16:15:27 James: Getting back to title, if needed for a sighted example, that would be a different success criteria. Also not correct according to the ARIA specs 16:15:27 q- 16:15:31 ack james 16:15:59 Sailesh: There is a success criteria for title 16:16:23 James: That one does not use aria-label. Here we are just talking for this example 16:17:31 Sailesh: Different types of buttons have different types of attributes. If you have a button with no text and a sighted user need to mouse over it to find out what it is 16:17:43 James: That will not pass with other success criteria 16:18:21 Sailesh: Sometimes you need to use link anchor with role="button". There are many different ways 16:18:34 James: there are other techniques to cover this 16:19:16 Sailesh: Here we should have a cautionary note that in some situations aria-label works best but in other cases title may be best 16:19:24 AWK: Where would that go? 16:19:31 Sailesh: Description 16:19:35 q+ to say should this technique also apply to 4.1.2? 16:20:32 Loretta: ironic that we are recommending the title attribute since there is issues for keyboard users 16:21:13 AWK: Not sure about title attribute. Maybe a note that aria-label is not the solution for every situation 16:21:24 Loretta: That is true of most techniques and ARIA 16:21:59 Sailesh: For most techniques, the situation is listed. That is what I am recommending here 16:22:41 AWK: Do you think the first paragraph indicate that? 16:22:51 Sailesh: yes 16:23:08 AWK: does that address all the comments, Sailesh? 16:23:12 Sailesh: Yes 16:23:34 Zakim, who is on the queue? 16:23:34 I see Loretta on the speaker queue 16:23:42 AWK: Not fond of example 3 16:24:04 AWK: maybe we should add telephone example 16:24:15 David: That is a good idea. I see that a lot 16:24:23 James: Does anyone have one 16:24:34 AWK: Let's add that 16:24:50 AWK: Add a placeholder and if someone has one we can insert it 16:26:02 AWK: success criterion 3.3.2 related 16:26:11 James: 4.1.2 16:26:47 AWK: 1.3.1 because it is information conveyed through presentation. The X is clear visually but not if it is read as X. 16:26:58 Loretta: 1.1.1 16:27:07 AWK: The X is text 16:27:11 Zakim, who is on the queue? 16:27:11 I see Loretta, Sailesh on the speaker queue 16:27:27 Loretta: gets nervous about putting it under 1.3.1 16:27:37 ack l 16:27:37 Loretta, you wanted to say should this technique also apply to 4.1.2? 16:27:37 AWK: fine with putting it under 4.1.2 16:27:45 ack sa 16:28:40 Sailesh: another example is to have multiple buttons that are the same, but for non-sighted users you may want to make this descriptive with aria-label 16:29:42 Sailesh: You could also use aria-labelledby 16:29:53 David: I would use aria-describedby 16:30:13 Sailesh: This to expose the name on the button so it should not be aria-describedby 16:30:26 better would be aria-labelledby="add4 lap4" 16:31:24 http://mars.dequecloud.com/demo/form-markup.htm#lap4 16:31:51 http://www.w3.org/WAI/GL/wiki/Using_aria-labelledby_to_concatenate_a_label_from_several_text_nodes 16:32:31 AWK: we have an example that is similar 16:32:38 AWK: we will leave this one open 16:32:52 James: if someone has a telephone example 16:33:46 AWK: we need to figure out how to accelerate through these 16:34:09 James: can we use SSN instead 16:34:11 Kathy: yes 16:34:28 AWK: if you did not respond to the second survey, please do 16:34:55 AWK: will send a note to see if your comments have been addressed later this week 16:34:57 -Sailesh 16:34:59 -Loretta 16:34:59 -Marc_Johlic 16:35:01 -James_Nurthen 16:35:26 zakim, list attendees 16:35:26 As of this point the attendees have been +1.978.443.aaaa, Kathy, +1.650.506.aabb, Peter_Korn, AWK, David_MacDonald, +1.703.861.aacc, Katie, Joshue, +1.703.225.aadd, Sailesh, 16:35:30 ... Michael_Cooper, Loretta, Marc_Johlic, James_Nurthen 16:35:30 -Katie 16:35:36 RRSAgent, make minutes 16:35:36 I have made the request to generate http://www.w3.org/2013/09/24-wai-wcag-minutes.html AWK 16:37:28 -Kathy 16:39:40 -David_MacDonald 16:39:56 Zakim, who is on the phone? 16:39:56 On the phone I see AWK, Michael_Cooper 16:42:56 -Michael_Cooper 16:42:57 -AWK 16:42:57 WAI_WCAG()11:00AM has ended 16:42:57 Attendees were +1.978.443.aaaa, Kathy, +1.650.506.aabb, Peter_Korn, AWK, David_MacDonald, +1.703.861.aacc, Katie, Joshue, +1.703.225.aadd, Sailesh, Michael_Cooper, Loretta, 16:42:57 ... Marc_Johlic, James_Nurthen