15:55:18 RRSAgent has joined #html-a11y 15:55:18 logging to http://www.w3.org/2011/03/20-html-a11y-irc 15:55:20 RRSAgent, make logs world 15:55:20 Zakim has joined #html-a11y 15:55:22 Zakim, this will be 2119 15:55:22 ok, trackbot; I see WAI_(A11YF2F)11:30AM scheduled to start 25 minutes ago 15:55:23 Meeting: HTML Accessibility Task Force Teleconference 15:55:23 Date: 20 March 2011 15:55:34 rrsagent, do not start a new log 15:56:13 silvia has joined #html-a11y 15:56:33 zakim, this is 2119 15:56:33 ok, MichaelC; that matches WAI_(A11YF2F)11:30AM 15:56:42 Sean_ has joined #html-a11y 15:57:52 mkobayas has joined #html-a11y 15:58:07 present: John_Foliot, Rich_Schwerdtfeger, Mike_Smith, Silvia_Pfeiffer, Eric_Carlson, Judy_Brewer, Mastaomo_Kobayashi, Janina_Sajka, Sean_Hayes, Frank_Olivier, Cynthia_Shelly, Michael_Cooper 15:58:11 richardschwerdtfe has joined #html-a11y 15:59:30 +Gregory_Rosmaita 15:59:44 present+ Gregory_Rosmaita 15:59:50 you be on mute? Ha! 16:04:13 JF_ has joined #html-a11y 16:04:29 MikeSmith has joined #html-a11y 16:04:40 scribe: Rich 16:05:34 Topic: Video Examples with TTS control of audio descriptions 16:05:47 First example: use ARIA live region 16:05:59 RRSAgent, make minutes 16:05:59 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 16:06:31 RRSAgent, make logs public 16:07:21 Example renders extended description using TTS 16:08:11 mkobyyas: We can change the speed of the audio description 16:08:53 q? 16:09:11 mkobyyas: Can also use TTS server 16:09:31 -Gregory_Rosmaita 16:10:00 mkobyyas: Sends text to server and returns audio 16:10:28 eric: How do you synchronize this with the video? 16:10:32 mkobayas: time update 16:11:23 q? 16:12:32 +Gregory_Rosmaita 16:13:47 rich: Summary: Get text, send to server, get audio file, play it, wait for next timed text call 16:13:59 q? 16:14:06 q+ richardschwerdtfe 16:14:17 sean: pause on exit seems like the wrong thing 16:15:00 RRSAgent, make minutes 16:15:00 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 16:15:33 eric: he is correct. 16:16:12 sylvia, can you show how it works? 16:16:47 q? 16:16:53 ack richardschwerdtfe 16:17:55 Topic: Demo Sean Hays 16:18:20 niet 16:19:19 Sean: I created a script called trakks.js 16:20:05 sean: I have three different tracks one for captions, two for descriptions 16:20:22 Sean: That make you allowed to do the track markup 16:20:47 Sean: the idea is that you can do other things. I have an Iframe pointing to the same TTML file that is styled as ... 16:21:00 Sean: I am actually using the track API 16:21:02 janina has joined #html-a11y 16:22:01 http://www.cwmwenallt.com/access/player.html 16:22:17 sean: This demo is on Safari 16:22:36 sean: if I look at in FF or IE it looks the same 16:22:50 sean: there are 4 levels of navigation in the file 16:22:58 sean: if I drill down I can skip along ... 16:23:14 sean: so I can skip along at the various levels 16:23:25 sean: If I skip up a level then the section level changes 16:23:36 sean: So, that is doing navigation based on the XML file 16:23:45 very nice tab navigation for the player with exposed text being spoken 16:23:50 sean: so this is TTML turning up as captions 16:23:56 i'm testing with IE9 16:24:25 sean: I turn on audio descriptions. So, rather than generating the audio. ... 16:24:26 hmm, can tab navigate the controls, but can't get them to activate 16:24:48 sean: so, this is using the caption file as captions as well as descriptions. It also points to the audio files 16:25:06 sean: the media tracks shows the signing 16:25:19 sean: the signing is a separate video file that is synched 16:25:35 sean: so I switched the source 16:25:44 silvia: so it is burned in 16:25:47 sean: yes 16:26:04 sean: the access to the pixels does not work on all the browsers 16:26:19 eric: do you support alpha in 2.64 16:26:25 frank: no 16:26:36 q? 16:26:37 eric: do you support ping - a compression format 16:26:41 frank: no 16:27:17 sean: new demo 16:27:29 sean: I can import an scc file 16:27:53 sean: now that I can support that fxp file ... 16:28:23 secan: In this one the fxp is transparent 16:28:29 s/fxp / dfxp 16:28:36 thanks 16:28:56 silvia: how much of the dfxp have you implemented 16:29:06 sean: all of it except for the obscure timing stuff 16:29:44 sean: If I edit the .dfxp file ... 16:30:03 nobody speaking just now 16:30:11 RRSAgent, make minutes 16:30:11 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 16:30:18 sean: the styles in here map to CSS files 16:30:28 silvia: so you can also do bold and italic: 16:30:41 sean: yes. all of the classes get mapped to class Q 16:31:07 sean: you can overwrite them can't you 16:31:24 silvia: you implement to different regions - one for the speaker 16:31:56 sorry: sean: you implement to different regions - one for the speaker 16:32:14 style sheet for sean's demo: http://www.cwmwenallt.com/access/style/jquery-ui-1.8.9.custom.css 16:32:16 sean: so there the top region is separate from the bottom one. 16:32:32 sean: two different navigation regions. keyboard navigable 16:32:42 sean: I tested with NVDA and both get working. 16:33:02 sean: I tried aria-live but does not work across all browser 16:33:06 can access UI with IE9, but can't play (to be expected, no?) 16:33:35 sean: If I were using the TTS engine you could simply send the text and generate the audio on the fly 16:34:07 sean: I did not find out about the bing translator until just now. I might have a go at that 16:34:24 what is the bing translator? 16:34:41 converts text to audio (server based) 16:35:29 found it: http://www.microsofttranslator.com/ 16:35:29 sean: I will try to find a link to that 16:35:32 there 16:35:49 Demo: Silvia 16:36:05 http://blogs.msdn.com/b/translation/ 16:37:02 silvia: so this is a build of Chromium which is a build of webkit code 16:37:21 Topic: Silvia Demo on chromium 16:38:03 silvia: this is a build by one of the people in Google (not myself) doing text track on chromium 16:38:12 silvia: it is implemented in the browser 16:38:36 silvia: it's been built into the framework of how video works 16:39:25 eric: so what she has done is add a generic track element to webkit and a number of classes to read the data from the track to decode it. The whole thing is done in a very generic way and it is not a big deal to put in a generic parser 16:39:51 eric: it was done as a text track. Binaries would be more work. Basic plumbing is in webkit f4 16:39:56 s/f4/4/ 16:40:12 eric: we just got code from the person doing this on Friday 16:40:25 eric: it is a simple matter of finishing this on Sarari 16:40:33 s/Sarari/Safari/ 16:40:37 q? 16:40:43 silvia: there is a lot more to do 16:41:15 silvia: we are on the way and we are getting there. It fits with the other stuff in video. That basically states what we have designed so far can be implemented. 16:41:51 RRSAgent, make minutes 16:41:51 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 16:41:54 sean: the styling you had on that caption, where did that come from ... so you are not hooked up to the CSS 16:42:11 silvia: this is a very, very early pre-release thing but the first thing is done 16:42:19 mike: is the build available publicly 16:42:25 silvia: no 16:42:53 eric: I am working with her but she is a new webkit contributor. The plan is to get it into shape to get it into the tree 16:43:07 eric: the point is it will be in there to play around with 16:43:22 frank: what was the trickiest thing to implement so far? 16:43:26 eric: the architecture 16:43:48 silvia: one thing to note the styling ... 16:43:59 eric: it is done with an element in the shadow dom 16:44:18 frank: we are considering doing a similar thing 16:44:29 silvia: how do you do the controls? 16:44:34 frank: custom draw them 16:44:40 silvia: cool 16:45:05 eric: hooking this up to CSS is no work at all as it is in the shadow DOM. ... hours of work 16:46:13 chair: Janina_Sajka, MikeSmith 16:46:22 eric: Since Webkit is open source. We have to get the architecture and the code submitted. I don't know how far off it is. It will take a week or so to get it all checked in. As it is an early draft it will take 3-5 weeks 16:46:39 silvia: I would say at least a month. soonish 16:46:44 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html oedipus 16:47:16 silvia: the spacial markup for WebVTT 16:47:33 silvia: deciding if to use generic HTML markup in queues 16:47:45 frank: we would like that. CSS ... 16:47:57 silvia: pseudo selector support to get to the shadow DOM 16:48:00 q? 16:48:20 Mike: running a little bit over. The next thing we want to do is do a review of yesterday's minutes 16:48:20 http://www.w3.org/2011/03/19-media-minutes.html 16:48:28 Topic: review media minutes 16:48:44 cyns has joined #html-a11y 16:49:00 MichaelC: Review issue 147 and talk about drag and drop 16:49:07 -> http://www.w3.org/2011/03/19-media-minutes.html minutes of media subteam breakout from March 19 16:49:25 MichaelC: the minutes are by date 16:49:40 Mike: Issue 147 16:49:55 Topic: Issue 147 16:49:58 http://dev.w3.org/html5/status/issue-status.html 16:50:13 Mike: this is the playback rate thing 16:50:17 Issue 147 http://www.w3.org/html/wg/tracker/issues/147 16:50:36 silvia: frank did you put that in ? 16:50:38 frank: yes 16:51:37 frank: It seems prudent that you know where you are in live streaming such as if you are behind. It also seems prudent to tell the author if there are issues with playing back at a certain rate. 16:52:00 frank: we want to have something that does not change and ship what we have today in the spec. 16:52:42 silvia: the playback rate tells you the rate it is playing back. If playing backwards it is negative. That is what playback rate does and you can adjust it in JavaScript 16:52:49 q? 16:53:06 eric: this is a javascript API. The text in the spec. says the user sets it and the browser plays it 16:53:47 mike: where we are at is we have a bug and Hixie says won't fix. 16:54:00 mike: we are going to adopt this unless someone introduces a counter proposal 16:54:19 silvia: it is overloaded as the browser can tell you what it has done. 16:54:30 silvia: I introduced a change proposal 16:54:47 mike: the next thing to do is put out a survey 16:55:07 mike: the bug triage team said this does not have any relation to accessiblity concerns 16:55:29 silvia: I would think Janina might be concerned about a playback rate 16:56:05 eric: the spec. tells you play at the rate the browser told to play 16:56:22 eric: Hixie says if the browser can't perform it sucks 16:56:57 janina: my mother who is not a native English speaker so she would want to see things slown down 16:57:10 sean: it is a mainstream thing too 16:57:27 silvia: Ian regards the playback rate as a vehicle to tell the browser what to do 16:58:05 silvia: he thinks the browser's ability to convey what it was able to do would be good. 16:58:13 q? 16:58:18 silvia: Ian wants to see the reporting 16:58:51 silvia: Hixie did not like my proposal 16:59:22 silvia: there is a whole discussion on statistics but there is no concrete proposal on the table yet and I would like to pull what was said together 16:59:36 silvia: Hixie wants us to assemble all the statistics 16:59:54 eric: Phillip said adding an attribute for the actual rate is insufficient 17:00:23 eric: what is implemented in Webkit is a script that tells us to change the rate and a signal is generated when the rate has changec 17:00:40 eric: leave it the way it is 17:01:08 mike: from the task forces perspective we need to decide to whether to endorse a specific proposal 17:01:15 janina: we should discuss at the next telecon 17:01:18 link to Bing translator http://msdn.microsoft.com/en-us/library/ff512404.aspx 17:01:26 thanks Sean 17:01:47 action: Michael(tm) to add an agenda item for next week's telcon for discussion of issue 147 17:01:47 Sorry, couldn't find user - Michael(tm) 17:01:58 action: Mike to add an agenda item for next week's telcon for discussion of issue 147 17:01:59 Could not create new action (failed to parse response from server) - please contact sysreq with the details of what happened. 17:01:59 Could not create new action (unparseable data in server response: local variable 'd' referenced before assignment) - please contact sysreq with the details of what happened. 17:02:33 Mike: we wanted to do summaries of yesterdays discussions 17:02:40 http://www.w3.org/2011/03/19-html-a11y-minutes.html 17:02:57 Mike: we talked about text alternatives a bit 17:03:16 Mike: Laura is not in complete agreement with those in the task force 17:03:59 Mike: Cynthia did you have the discussion on text alternatives 17:04:24 Cynthia: Steve was supposed to send a draft last night but I did not get one 17:04:48 Mike: We saw an Opera plug-in that makes longdesc discoverable 17:05:06 John: there was a jquery plug-in 17:05:11 http://www.w3.org/WAI/PF/HTML/wiki/Verbose_desc_reqs 17:05:12 Mike: that is new info 17:05:29 Mike: you took an action item to fold that into the change proposal 17:05:37 http://www.d.umn.edu/~lcarlson/research/ld.html 17:06:06 John: Steve Faulkner also provided draft text 17:06:15 http://www.html5accessibility.com/tests/img-longdesc.html#long 17:06:30 HTML WG Bug 10853: HTML5 lacks a verbose description mechanism http://www.w3.org/Bugs/Public/show_bug.cgi?id=10853 17:07:09 mike: the summary on longdesc is we made some progress on long desc. and we got wider support of retaining longdesc 17:07:33 Mike: ARIA lexical processing 17:08:16 http://www.w3.org/2011/03/19-html-a11y-minutes.html#item03 17:08:23 http://dev.w3.org/html5/spec/content-models.html#annotations-for-assistive-technology-products-aria 17:08:27 richardschwerdtfe: we need a means to detect clickable regions… 17:08:35 eric_carlson has joined #html-a11y 17:08:40 … so that authors can assign events to regions 17:08:41 http://www.html5accessibility.com/tests/aria-changes.html 17:08:48 … gives you the bounding rectangle 17:08:59 … satisfies an authoring need 17:09:07 … ties input back to the actual DOM 17:09:59 http://dev.w3.org/html5/status/issue-status.html 17:09:59 Mike: The last open issues 17:10:01 http://www.w3.org/html/wg/wiki/ChangeProposals/CaretSelection 17:10:31 MikeSmith: we are good to go on the relevant accessibility issues 17:10:48 MikeSmith: We will talk about drag and drop 17:10:54 http://dev.w3.org/html5/spec/dnd.html#dnd 17:11:05 MikeSmith: summaries? 17:11:10 http://www.w3.org/2011/03/19-media-minutes.html 17:11:21 silvia: need Mark Watson but is not around 17:11:33 q+ don't we still have a LOT of outstanding issues with TABLE markup and algorithms (what wendy was working on) 17:11:42 q+ to say we still have a LOT of outstanding issues with TABLE markup and algorithms (what wendy was working on) 17:11:44 silvia: don't think they know how to dial in 17:12:15 q? 17:12:57 silvia: As a summary we started out with the use cases (3). In band tracks 17:13:12 silvia: One resource mentioned int the source attribute of the video element 17:13:31 silivia: we have external tracks as slaves to the main track 17:13:49 silivia: we have equivalent video elements that are synchronized 17:14:27 silvia: we need support for the second one with the slaved timeline. This will be very important for sign languages video and audio descriptions 17:14:40 silvia: that was the key agreement on which we based the design work 17:14:46 http://www.w3.org/WAI/PF/HTML/wiki/Media_Multitrack_Media_API#.2810.29_HTML_Accessibility_Task_Force_proposal_.28.22The_San_Diego_Solution.22.29 17:15:01 silivia: this is option 10 on our wiki page 17:15:10 Sean has joined #html-a11y 17:15:18 silvia: we focused on our first use case - inband tracks 17:15:47 silvia: on our agenda we are a little bit behind but we are making good progress 17:15:50 http://lists.w3.org/Archives/Public/public-html-a11y/2011Mar/0131.html 17:16:09 silvia: we just did the JavaScript API. We don't believe that needs more work 17:16:18 silvia: we need to look into rendering and CSS 17:16:36 silvia: I think we can finish this today but not far beyond that 17:16:40 ack oe 17:16:40 oedipus, you wanted to say we still have a LOT of outstanding issues with TABLE markup and algorithms (what wendy was working on) 17:16:50 we should, at least, review/re-assign outstanding TABLE issues while we are in plenary session -- i have summary as element http://www.w3.org/html/wg/wiki/ChangeProposals/summary_element 17:16:59 gregory: we have issues with table that have not been addressed in months 17:17:13 gregory: we should review or reassign these issues 17:17:19 q? 17:17:49 cynthia: we had not decided to address this as last call 17:17:52 +q 17:18:28 ack JF 17:18:31 janina: we have summary and longdesc to come back to. 17:18:50 JF: there was a resolution to keep as HTML 4 17:19:02 q? 17:19:06 http://www.w3.org/2002/09/wbs/40318/issue-32-objection-poll/ 17:19:11 MikeSmith: I had a question about the track element 17:19:16 silvia, http://www.w3.org/2011/03/19-media-minutes.html 17:19:44 oedipus, thanks! 17:19:54 MikeSmith: Hixie's position is to limit eternal timed text formats but others are not satisfied with that. Hixie will need to be flexible 17:20:01 eric: we will have a proposal tomorrow 17:20:07 silvia: yes 17:20:12 q? 17:21:32 Mike: what do you need form Mark Watson? 17:21:48 eric: I don't think he will have an issue but Mozilla might 17:22:08 eric: Mozilla may supply a separate change proposal 17:22:20 Silvia: Ian will supply a change proposal 17:22:37 silvia: we may get another 3 change proposals by Tuesday 17:22:42 eric: it is a very complex issue 17:22:53 silvia: it needs a lot more discussion 17:23:09 MikeSmith: we just need to get things submitted on time 17:23:25 http://dev.w3.org/html5/spec/dnd.html 17:23:30 MikeSmith: Status on drag and drop 17:24:08 i/MikeSmith: Status on drag and drop/TOPIC: Drag and Drop in HTML5/ 17:24:25 MikeSmith: the deal with drag and drop is it has been kind of an open discussion. However Hixie made significant changes to the spec. by introducing a dropzone 17:24:26 http://lists.w3.org/Archives/Public/public-html-a11y/2011Jan/0298.html 17:24:49 http://dev.w3.org/html5/spec/dnd.html#the-dropzone-attribute 17:24:55 MikeSmith: Gez reviewed but the issue of keyboard accessibility is resolved. 17:25:04 http://dev.w3.org/html5/spec/dnd.html#the-dragevent-interface 17:25:49 MikeSmith: Rich wants to view conflicts with ARIA. 17:26:13 Rich: I will reopen after a review 17:26:27 "All HTML elements may have the dropzone content attribute set. When specified, its value must be an unordered set of unique space-separated tokens that are ASCII case-insensitive. The allowed values are the following:" 17:26:29 "copy: Indicates that dropping an accepted item on the element will result in a copy of the dragged data." 17:26:30 "move: Indicates that dropping an accepted item on the element will result in the dragged data being moved to the new location." 17:26:32 "link: Indicates that dropping an accepted item on the element will result in a link to the original data 17:26:51 MikeSmith: we had a break scheduled at 10:30 17:26:58 q? 17:27:43 Judy: I think it was back at 10:03 your time I saw Rich Schwerdtfeger minute that Laura was not in full agreement with the task force discussion on the taskforce discussion on longdesc 17:28:05 Judy: it looks like she further tweeked her proposal on longdesc. 17:28:52 http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElementSurveyConformaceChoices 17:29:31 Mike: I think it is fair to say the position she has taken on the change proposals is such that the issue is relative to text alternatives 17:29:43 Juday: In looking back I see that. ok 17:29:52 s/Juday/Judy/ 17:30:05 Janina: she created change proposals for other people's positions 17:30:23 Janina: it may be attributed to other items such as longdesc 17:30:34 Issue 122 change proposal drafted by GJR in fulfillment of an action item assigned at HTML WG F2F at TPAC 2010: http://www.w3.org/html/wg/wiki/ChangeProposals/purely_decorative_images 17:30:36 MikeSmith: it would be good to get Laura on a phone call 17:30:48 Judy: has a personal issue she needs to address 17:31:13 GJR has action from TF yesterday to reply to survey on ISSUE 122 on behalf of TF -- circulated proposed comment to facillitators and staff 17:31:13 Judy: I am also trying to get more coordination. So, probably won't happen this weekend 17:31:30 MikeSmith: I think we can get the issue addressed very quickly if addressed in real time 17:31:53 RRSAgent, make minutes 17:31:53 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 17:32:01 big thanks to Rich for scribing 17:32:03 -Judy 17:32:15 -Gregory_Rosmaita 17:32:31 s/personal issue she needs to address/family issue at the moment/ 17:34:52 s/the taskforce discussion on longdesc/the taskforce discussion on longdesc, but in the communication i saw, she said it looked like the group made good progress. 17:38:11 silvia1 has joined #html-a11y 17:46:59 MikeSmith has joined #html-a11y 17:47:20 richardschwerdtfe has joined #html-a11y 17:47:25 yw 17:48:03 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html oedipus 17:49:28 WAI_(A11YF2F)11:30AM has ended 17:49:29 Attendees were Judy, Gregory_Rosmaita 17:58:03 silvia has joined #html-a11y 17:58:27 WAI_(A11YF2F)11:30AM has now started 17:58:34 +??P0 17:58:40 zakim, ??P0 is FtF 17:58:40 +FtF; got it 17:59:08 +Gregory_Rosmaita 17:59:47 http://www.w3.org/WAI/PF/HTML/ftf_2011-03 18:00:17 TOPIC: ARIA Integration 18:00:26 scribe: MikeSmith 18:00:51 cyns has joined #html-a11y 18:00:52 richardschwerdtfe: as far as I know, about ARIA integration, we are waiting for the edits 18:01:17 MichaelC: we wanted to talk about the mapping document 18:01:26 cyns: we need more people helping on this 18:01:33 -> http://dev.w3.org/html5/html-api-map/overview.html HTML API mapping document 18:01:40 richardschwerdtfe: yeah 18:01:55 Steve: I have started to work on it again 18:02:42 Steve: two big tables in this doc 18:03:04 … pretty much done, but so far with input only for a couple people 18:03:17 … so it obviously needs scrutiny 18:03:26 http://dev.w3.org/html5/html-api-map/overview.html#api-role 18:03:31 http://dev.w3.org/html5/html-api-map/overview.html#api-att 18:03:43 cyns: when I generated the original table, I did it based on looking at existing browsers 18:03:52 RRSAgent, make minutes 18:03:52 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 18:03:59 richardschwerdtfe: do you have events in here? 18:04:12 janina has left #html-a11y 18:04:37 note: there is a relatively new version of IA2 at http://a11y.org/ia2-spec 18:05:07 RRSAgent, make minutes 18:05:07 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 18:05:51 Steve: I looked at placeholder, and how it's being mapped 18:06:08 janina_lurker has joined #html-a11y 18:06:36 zakim, who's on the phone? 18:06:36 On the phone I see FtF, Gregory_Rosmaita 18:06:45 … looking at how the accessible name is handled 18:07:29 Steve: there are differences between how Firefox and Webkit implement this 18:08:26 Steve: the way that placeholder vs title is handled in some browsers does not seem right 18:08:37 http://dev.w3.org/html5/html-api-map/overview.html#calc 18:08:52 cyns: I'm not sure that wrapping it around is per spec 18:09:02 MichaelC: it is, though not recommended 18:10:13 cyns: there are a lot of cases where people don't put labels on selects 18:11:14 Steve: there is a need for this document, because browsers are not handling it interoperably 18:11:23 q? 18:11:44 Steve: I've been talking with Alex Sirkov 18:12:03 … and he has claimed that the FF is right per the ARIA name calculations 18:12:16 MichaelC: it does include some HTML rules, but… 18:12:30 cyns: it says, "title always loses" 18:12:33 s/Sirkov/Surkov 18:12:48 MichaelC: and placeholder is not in the ARIA spec, because we were working from HTML4 18:14:24 ;) 18:15:00 Steve: you can see that there are still lots of TODOs in this document still 18:15:28 … you can see I started to work on the description of how to handle the summary and details elements 18:15:50 cyns: we need to finish the ARIA implementors' guide 18:16:02 … discuss with David Bolter, others 18:16:34 Steve: the idea is to get some stuff into the document even if it's not all been agreed on yet, so that we have something to start with 18:16:37 http://www.w3.org/WAI/PF/aria-implementation/ 18:17:17 Steve: e.g., the summary element should be a button element 18:17:29 s/button element/button role/ 18:17:58 Steve: details and summary are being implemented now 18:18:07 … Chrome has an implementation 18:18:17 … and there are JS implementations of this 18:19:03 … one thing we need to look at is, it seems more logical to have the open/closed state on on the actual summary 18:19:17 cyns: but buttons don't have that 18:19:49 Steve: all of the action occurs on the disclosure widget itself 18:20:04 cyns: do you have range and menu and command? 18:20:21 Steve: feel free to edit :) 18:20:32 cyns: I need to get my CVS access working 18:20:42 MikeSmith: I can help with that at lunchtime 18:21:04 RRSAgent, make minutes 18:21:04 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 18:21:44 Steve: do we need a role=video? 18:21:54 cyns: could just do it as a landmark 18:22:03 richardschwerdtfe: do you have a control pattern? 18:22:07 role=video makes sense, and has precedent: role=math 18:22:15 cyns: don't think we have one in UAG yet 18:24:41 cyns: I think it could be confusing for people if we end up duplicating information from the ARIA implementor's guide? 18:24:55 Steve: maybe we should have an ARIA+HTML guide 18:25:21 cyns: actually, we went to a lot of trouble to make the ARIA implementor's guide to be language-agnostic 18:25:37 cyns: we need to tread carefully to avoid redundancy 18:26:06 cyns: great work on this so far, Steven 18:26:17 plus one: great work SteveF 18:26:28 richardschwerdtfe: yeah, and we still need to address canvas handling 18:27:21 Steve: yeah, there is obviously overlap, and we need to resolve that 18:27:37 richardschwerdtfe: PF really needs to review UAG 18:27:41 http://www.w3.org/WAI/PF/aria-implementation/ 18:28:00 cyns, do you want the UAWG to review http://www.w3.org/WAI/PF/aria-implementation/ 18:28:09 cyns: sorry, yeah, I'm talking about the ARIA implementation guide 18:29:48 ARIA comments have public view and all of the ARIA editors' drafts are public 18:48:40 scribe: cyns 18:48:45 topic: keyboard access 18:48:54 cyns: what about keyboard access? 18:49:15 having infrastructural problems please standby 18:49:25 http://www.w3.org/WAI/PF/HTML/wiki/Access/HTML5_Accesskey_Bugs 18:50:12 how is user to decide what accesskeys to use: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10775 status: the HTML Accessibility Task Force needs to review the following quotes from the 18 March 2011 Editor's Draft which follow to ensure that this bug has been adequately addressed; of pariticular concern is that there is no stipulation that when a UA or user chooses a set of accesskeys, that... 18:50:14 ...that set of accesskeys will be uniformly applied (no mixing of accesskey strings: once a set of accesskeys is chosen, the user agent must them limit the accesskey values to those that match the position of the initially chosen accesskey) 18:51:09 GR: bug 10775. you can have a space-delimited list of accesskeys. how can user figure out what to use. 18:51:20 GR: my proposal was to make that a cascade. 18:51:59 GR: what's currently in the spec is examples that use multiple access keys. There's nothing in the spec that says which to use 18:53:04 Stevef has joined #html-a11y 18:53:15 GR: Say I have a search field. accesskey="S 0". you can get that accesskey by typing alt+S or alt+0, but if you have each accesskey assigned more than one value, that you have a cascade. 18:53:56 GR: so if you have S used somewhere else, it would fall back to 0. Otherwise, you can only use S, not both 18:54:09 GR: how do you get to that second key of accesskeys. 18:54:47 MS: Ian says that you don't expose those to users. UA makes the selection, and only exposes the selected key to the user. multiple values are not exposed to the user. 18:55:17 GR: i have an inherent distrust of UA chosing for me. I want to choose if I want to use alpha or other user accesskeys 18:55:51 MS: so bug should say that if there are multiple accekeys exposed to the user, so the user can choose. The current spec assumes that's not something users need. Need to provide a use case. 18:56:45 MS: looking at the status on this, hixie moved it to rejected, but you commented, then hixie made a spec change, to add informative text to give an explaination and posted a dif, bug triage said in January that the change addressed the original issue. 18:57:00 MS: if that's not the case, you need to re-open the bug or make a new one. 18:57:01 M 18:57:07 GR: I guess I do. 18:57:43 MS: new bug should challenge assumption in the spec that users don't need to have the full list of accesskeys exposed to the user. 18:58:13 GR: discoverability is a problem. author proposes user disposes. 18:58:23 MS: create a use case. 18:58:55 GR: what hixie wrote is very nebulous. UA will decide what to do based on capabilities of device. 18:59:56 GR: UA might pic numberic keyboard on a phone or alpha on a full keyboard. User should be able choose. 19:00:21 CS: would configurability be enough? could make for very complex UI 19:00:40 GR: how many accesskeys are likely? 19:00:50 MS: this is a problem in earlier versions of HTML 19:01:04 MS: previous spec for accesskey only allowed one value, right? 19:01:06 GR: right 19:01:24 MS: there were other ways, such as through scripting 19:02:00 CS: sort of. not declaratively 19:02:16 MS: previous spec was less precise on what UA behavior should be. 19:02:45 GR: right. so if we're paving the cow path, let's do a good job. make sure that it's discoverable. 19:03:24 MS: frame the discusision instead as... great, now we have a standard way to define multiple access keys, and now we need to refine that for the case where someone might want to choose which key 19:03:54 MS: better to close this bug, and create a new one that refines the behavior 19:04:03 RRSAgent, make minutes 19:04:03 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 19:04:09 RS: is teh behaivor on a non-alpha keybaord defined? 19:04:14 CS: yes. 19:04:25 RS: so waht is that you are looking for? 19:04:53 GR: user should be able to choose whether they want the first token for every value, second token, etc. 19:05:31 MS: this is a bigger issue, or needs to be framed differently. describe the use case and go from there. you don't have anything in the use case. need to explain why the user wants to do this 19:05:34 GR: ok 19:06:02 HTML WG Bug 10773 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10773 - accesskey should chosen from document's declared charset marked RESOLVED WONTFIX status: the HTML A11y TF must decide if this is an important point of clarification; this reviewer thinks it is and needs to be added to the current text 19:08:06 GR: accesskey should be chosen from documents declared character set. for example, if I'm using a doc that's english, I shouldn't have a character that's not english 19:08:17 CS: aren't most web pages UTF-8 now? 19:08:30 MS: no, lots of Japanese and Korean are not 19:08:43 MS: TF bug team thought Ian's fix was ok 19:08:47 GR: don't agree 19:09:05 MS: write an email to TF to discuss, put on telecon agenda. 19:09:24 GR: I will prepare 2-3 a week to work thoruhg 19:09:59 MC: TF bug team may have said that because we thought the whole team doesn't need to be invovled. Gregory can do it himslef. 19:10:10 MS: Need use cases. 19:10:48 GR: I will bring them to task force, and they can decide if we will address it or if Gregory should do it on his own. 19:11:02 MS: TF may need to work on that. Bring use cases, and what should change. 19:12:30 breaking for lunch 19:14:06 -Gregory_Rosmaita 19:19:37 -FtF 19:19:38 WAI_(A11YF2F)11:30AM has ended 19:19:40 Attendees were FtF, Gregory_Rosmaita 19:28:48 richardschwerdtfe has joined #html-a11y 19:57:11 richardschwerdtfe has joined #html-a11y 19:58:19 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html oedipus 20:19:17 ok, thaniks 20:19:37 janina_lurker: big thanks to Microsoft and to Cynthia in particular for sponsoring the meeting 20:19:43 RRSAgent, make minutes 20:19:43 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 20:20:08 the non-media breakout folks are now adjourned 20:20:15 s/ok, thaniks// 20:20:35 RRSAgent, make minutes 20:20:35 I have made the request to generate http://www.w3.org/2011/03/20-html-a11y-minutes.html MikeSmith 20:28:20 Zakim has left #html-a11y 20:31:36 MikeSmith has joined #html-a11y 20:33:38 MikeSmith has joined #html-a11y 21:10:04 I see 2 open action items saved in http://www.w3.org/2011/03/20-html-a11y-actions.rdf : 21:10:04 ACTION: Michael(tm) to add an agenda item for next week's telcon for discussion of issue 147 [1] 21:10:04 recorded in http://www.w3.org/2011/03/20-html-a11y-irc#T17-01-47 21:10:04 ACTION: Mike to add an agenda item for next week's telcon for discussion of issue 147 [2] 21:10:04 recorded in http://www.w3.org/2011/03/20-html-a11y-irc#T17-01-58