20:01:02 RRSAgent has joined #html-techs-tf 20:01:02 logging to http://www.w3.org/2013/05/02-html-techs-tf-irc 20:01:42 Zakim has joined #html-techs-tf 20:01:59 MichaelC has joined #html-techs-tf 20:02:05 jamesn has changed the topic to: HTML5 & ARIA techniques for WCAG TF 20:02:34 zakim, list conferences 20:02:34 I see Team_(eme)19:16Z, WAI_WCAG()4:00PM active 20:02:35 also scheduled at this time are WAI_(GALLERY)3:00PM, UW_POI(POIWG)4:00PM 20:02:42 zakim, this is wai_wcag 20:02:42 ok, MichaelC; that matches WAI_WCAG()4:00PM 20:02:43 zakim, this is WAI_WCAG 20:02:44 jamesn, this was already WAI_WCAG()4:00PM 20:02:44 ok, jamesn; that matches WAI_WCAG()4:00PM 20:02:50 +Cooper 20:03:11 trackbot, associate this channel with #wai-wcag 20:03:11 Associated this channel with #wai-wcag. 20:05:00 regrets+ Marc_Johlic, Detlev_Fischer 20:05:13 +Loretta_Guarino_Reid 20:07:11 https://www.w3.org/2002/09/wbs/35422/20130502tfaria/results 20:10:55 Loretta has joined #html-techs-tf 20:11:03 scribe:Loretta 20:11:09 Introductions all around. 20:13:30 James: suggest putting this in the not-needed-for-first-release category 20:13:51 James: focus on more important techniques for first release 20:14:40 adam_solomon has joined #html-techs-tf 20:14:56 +[IPcaller] 20:15:13 zakim, IPcaller is Adam_Solomon 20:15:13 +Adam_Solomon; got it 20:15:22 great 20:15:33 Michael: changing category to "Techniques, Postponed" and moving this technique there. 20:16:14 Michael: updating status to capture pointer to these survey comments. 20:20:48 Topic: Using WAI-ARIA range attributes... 20:21:53 James editing description of how native spinbuttons work , for example 1. 20:23:00 Discussion of button mark-up including role=presentation and alt attribute. 20:23:11 Michael suggests omitting alt attribute. 20:23:30 James suggests alt="" and removing role presentation. 20:24:09 James: Who can activate these buttons? 20:24:53 Michael: there is no input field, so screen reader users will need to use buttons. 20:25:03 James: users should use up and down arrow keys. 20:25:10 Paul: will users know that? 20:25:54 Loretta: should we be using the Open Ajax example? Sounds like there are issues. 20:26:19 Should the user be able to type in the value? Or only up and down arrow keys. 20:26:56 Michael: something needs to change. 20:27:38 Michael: enabling the user to type a value isn't a requirement for a spinbutton, but do we want to show an example that doesn't do this? 20:28:35 Discussion of proposed changes.... 20:30:21 Screen reader user can't use buttons, must use arrow keys. 20:31:50 Paul: trying a spin button with VoiceOver Utility app, Native control supports focus on control, not individual up and down buttons. 20:32:36 Michael: what is the point of the technique? range attributes 20:33:57 Michael: if want to talk about minimizing errors, it is a very different technique. 20:34:38 Michael: need to talk about why to use attributes from a WCAG perspective. 20:35:49 proposal: drop error usage of range attributes for later (only advisory anyway). 20:36:41 James: looking for better example of an aria spinbutton 20:37:31 paul: jquery mobile range sliders? they don't have up down buttons. 20:38:10 Loretta: alternative is that we write our own live example. But I can't do that. 20:40:01 Loretta: I'm leary of techniques for complete widgets. 20:40:31 James: the ARIA best practices document is looking for a new home. 20:41:38 Loretta: and I worry about whether, by providing one sample implementation of a widget, people conclude that is the only acceptable implementation. 20:43:55 Loretta: I'm fine with moving this to postponed. But because scripting is so intrinsic to the use of ARIA, I think this issue will keep recurring. 20:44:07 Paul: seems like we should make our own example. 20:44:14 James: yes, if we have the time. 20:44:52 james: can we host our own example at W3C? 20:45:02 Michael: yes, we already do this for other techniques. 20:45:20 Jamse: can we use libraries like jquery? 20:45:50 James: who has the code expertise to write their own live examples? 20:45:54 James: yes 20:46:02 Paul: maybe 20:46:29 Adam: I thought we didn't want to put all the details into the technique. Are we changing that? 20:46:58 James: I think our scripting would be simpler than open ajax. 20:47:47 Loretta: I still think that we need a complete live example, but only want to include the relevant snippets in the technique. 20:48:01 James: for this example, we should include the javascript for changing the value 20:48:33 James: Detlev could probably also write live examples. 20:49:19 James: need a strategy meeting for live examples. will put on the agenda for next week. 20:50:38 James: we will move this technique to the postponed section of the wiki 20:51:29 http://www.w3.org/WAI/GL/wiki/Techniques/ARIA 20:51:33 http://www.w3.org/WAI/GL/wiki/Techniques/ARIA 20:51:54 Agenda item: which SC does active-descendant meet? 20:52:12 Adam: does active-descendant apply to 2.1.1? 20:52:27 rrsagent, make minutes 20:52:27 I have made the request to generate http://www.w3.org/2013/05/02-html-techs-tf-minutes.html MichaelC 20:52:28 Adam: take example of combo-box. 20:52:52 rrsagent, make log world 20:52:53 Adam: as you navigate through the list, the active-descendant is changing. 20:53:11 rrsagent, make minutes 20:53:11 I have made the request to generate http://www.w3.org/2013/05/02-html-techs-tf-minutes.html MichaelC 20:53:15 James: it is letting a screen reader know where the focus is, but it isn't letting the keyboard user know. 20:53:35 If you take out active-descendant, the combobox will still work for the keyboard user. 20:53:42 Adam: because of the scripting? 20:53:54 James: right. 20:54:06 James: and that is why we concluded that this was a 4.1.2 technique. 20:54:20 Adam: of course active-descendant isn't the true focus. 20:54:31 James: right, but it communicates it to the screen reader. 20:55:09 meeting: HTML and ARIA Techniques Task Force 20:55:12 chair: James_Nurthen 20:55:23 James: additional complication: CSS4 (not yet available in any browser) has a new feature that lets you meet focus-visible with active-descendant. 20:55:34 agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2013AprJun/0036.html 20:56:22 James: but this is in the future; spec'd but not in last call and not implemented anywhere yet. But it will be cool when it works. 20:56:38 Adam: can we conclude that active-descendant will only be for 4.1.2 20:56:54 James, Loretta, Paul: yes 20:57:22 Adam: do we wnat to take out the open ajax example? Ar we talking about removing all of them? 20:57:47 James: we don't have to take out all open ajax examples, only when we think they are confusing things (or if we can write our own really quickly) 20:58:23 Adam: I will tentatively leave the examples in, and the group can review whether they are suitable when the technique is ready for review. 20:58:35 James: this example seems less controversial. 20:59:27 Next week's agenda: finish this survey, handle the next survey, and discuss providing live examples. 20:59:42 -Adam_Solomon 20:59:50 -Cooper 20:59:52 -Paul_Adam 20:59:56 zakim, please part 20:59:56 leaving. As of this point the attendees were James_Nurthen, Paul_Adam, Cooper, Loretta_Guarino_Reid, Adam_Solomon 20:59:56 Zakim has left #html-techs-tf 21:00:18 rrsagent, make minutes 21:00:18 I have made the request to generate http://www.w3.org/2013/05/02-html-techs-tf-minutes.html jamesn 21:02:19 I have made the request to generate http://www.w3.org/2013/05/02-html-techs-tf-minutes.html jamesn 21:02:36 http://www.w3.org/2013/05/02-html-techs-tf-minutes.html,text 21:03:42 marcjohlic has joined #html-techs-tf 21:03:58 rrsagent, please part 21:03:58 I see no action items