16:00:52 RRSAgent has joined #html-a11y 16:00:52 logging to http://www.w3.org/2014/12/18-html-a11y-irc 16:00:54 RRSAgent, make logs world 16:00:54 Zakim has joined #html-a11y 16:00:56 Zakim, this will be 2119 16:00:56 ok, trackbot; I see WAI_PFWG(HTML TF)10:00AM scheduled to start 60 minutes ago 16:00:57 Meeting: HTML Accessibility Task Force Teleconference 16:00:57 Date: 18 December 2014 16:00:57 Sorry, chaals, I don't understand 'trackbot, wake up please'. Please refer to for help. 16:01:13 zakim, this is 2119 16:01:13 ok, chaals; that matches WAI_PFWG(HTML TF)10:00AM 16:01:43 +Adrian_Roselli 16:01:44 zakim, LJWatson is me 16:01:44 sorry, LJWatson, I do not recognize a party named 'LJWatson' 16:01:49 +ShaneM 16:01:49 aardrian has joined #html-a11y 16:01:58 zakim, who is here? 16:01:58 On the phone I see Judy, [IPcaller], Adrian_Roselli, ShaneM 16:01:59 zakim, [IPcaller] is me 16:02:00 On IRC I see aardrian, Zakim, RRSAgent, chaals, Judy, LJWatson, paulc, liam, ShaneM, janina, MarkS, cabanier, hober, sivoais, joanie, trackbot 16:02:00 +LJWatson; got it 16:02:03 +[IPcaller] 16:02:10 + +1.617.319.aaaa 16:02:22 IanPouncey has joined #html-a11y 16:02:35 zakim, aaaa is me 16:02:36 +MarkS; got it 16:02:58 zakim, agenda? 16:02:58 I see nothing on the agenda 16:02:59 +??P17 16:03:00 agenda+ alt note 16:03:01 agenda+ WishList: https://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Wishlist_for_HTML5.1 16:03:01 agenda+ Keyboard access - https://www.w3.org/WAI/PF/HTML/wiki/Accesskey 16:03:01 agenda+ First meeting of 2015: date? 16:03:01 agenda+ Any other business? 16:03:07 zakim, ??P17 is me 16:03:07 +janina; got it 16:03:11 zakim, [ip is me 16:03:11 +chaals; got it 16:03:25 zakim, who is here? 16:03:25 On the phone I see Judy, LJWatson, Adrian_Roselli, ShaneM, chaals, MarkS, janina 16:03:27 On IRC I see IanPouncey, aardrian, Zakim, RRSAgent, chaals, Judy, LJWatson, paulc, liam, ShaneM, janina, MarkS, cabanier, hober, sivoais, joanie, trackbot 16:03:43 +Joanmarie_Diggs 16:03:47 +Liam 16:04:15 zakim, what is the code? 16:04:15 the conference code is 2119 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), paulc 16:04:19 scribe: MarkS 16:04:31 zakim, agenda? 16:04:31 I see 5 items remaining on the agenda: 16:04:32 1. alt note [from chaals] 16:04:32 2. WishList: https://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Wishlist_for_HTML5.1 [from chaals] 16:04:32 3. Keyboard access - https://www.w3.org/WAI/PF/HTML/wiki/Accesskey [from chaals] 16:04:32 4. First meeting of 2015: date? [from chaals] 16:04:32 5. Any other business? [from chaals] 16:04:37 +[Microsoft] 16:04:44 zakim, [Microsoft] is paulc 16:04:44 +paulc; got it 16:04:51 zakim, take up first item 16:04:51 I don't understand 'take up first item', MarkS 16:05:01 zakim, take up item 1 16:05:02 agendum 1. "alt note" taken up [from chaals] 16:05:19 CN: Any other business? 16:05:30 +[IPcaller] 16:05:32 JS: Add a longdesc topic 16:05:37 Zakim, IPcaller is me 16:05:37 +IanPouncey; got it 16:05:48 agenda+ longdesc question 16:06:14 CN: RE: ALT Note, there are some bugs filed. 16:06:21 SM: That's were we are right now 16:06:36 CN: Any other bugs out there? 16:06:41 JS: yes, I have a few 16:06:44 SM: me too 16:07:31 LQ: Timeline? 16:07:56 SM: Updated doc by end of january is realistic 16:08:57 ...get bugs filed by jan 9 please 16:09:02 zakim, take up next item 16:09:02 agendum 2. "WishList: https://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Wishlist_for_HTML5.1" taken up [from chaals] 16:10:03 CN: 5.1 wish list. This is a tracking device. Prioritized by where the activity is. If you feel strongly about something, do work to push it along 16:10:22 ...anything else anyone wants to see on this list? 16:11:01 CN: I've heard discussions about how to handle panels, accordions, carousels, etc. 16:11:21 ...there has been discussions to spec these up in HTML 16:11:32 ...Leonie has done some work 16:11:44 ...right now it heavily relies on ARIA and interop is problematic 16:11:54 +1 16:12:54 MS: This is a very difficult thing to implement interoperable. Would like to discuss possible solutions further 16:12:58 CN: I will put in wiki 16:13:01 zakim, take up next item 16:13:01 agendum 3. "Keyboard access - https://www.w3.org/WAI/PF/HTML/wiki/Accesskey" taken up [from chaals] 16:13:23 CN: s/interoperable/interoperably 16:13:33 s/CN: s/interoperable/interoperably/ 16:13:40 s/interoperable/interoperably/ 16:14:08 CN: link to use cases and requirements in the wiki. what we are trying to achieve 16:14:42 ...accesskey is the motivating problem, has potential to clear up other lingering issues, tabindex, semantic elements with builtin interactions. 16:15:03 ...should we be working on this in isolation, or as a greater interaction issue 16:16:03 ...I would like to keep it simple, but we need to consider how any changes made in this space affect other interaction pieces of HTML 16:16:03 ...has anyone looked at these use cases lastly? 16:16:03 LW: I have 16:16:03 LQ: me too 16:16:17 ...think its worth looking into what HTML and browser people think about keybindings 16:16:39 ...just to see if it would be productive to work on interaction as a whole 16:16:53 q+ 16:17:23 CN: at yandex, we are thinking about this a lot. we would like it to be better in our browser and in our services. considering whether working with access key as it is is better than nothing... 16:17:35 LW: I think its very broken as it stands. 16:17:55 plh has joined #html-a11y 16:18:02 +Plh 16:18:05 CN: Paul, is the IE team interested in working on this problem at all? 16:18:27 PC is not santa clause 16:18:39 s/clause/claus/ 16:19:04 PC: I think you should ask cynthia about that 16:19:58 CN: I've been keeping the wiki page up to date. There are a list of bugs. 16:20:21 ...what happens if you have an accesskey on a random element? how does it affect role? not at all. 16:21:07 ...23612: script in there has an example, 16:21:17 ...think we should be changing that. 16:21:42 ...27654: the user should be in charge of what keys are available to use as access keys 16:21:56 ...provides an algorithm for UA to select available keys 16:22:06 ...I agree that the user should have some control over this 16:22:35 s/example,/example of who should inform who 16:23:17 ...next bug, privacy. Can increase the accuracy of fingerprinting users. Reveals too much info about who you are and track you 16:24:08 ...still not clear why we have accesskey label anyway. especially if the page shouldn't be telling the user how their browser should work 16:24:48 ...wonders if the screenreader would rely on the DOM or the AAPI in this case 16:25:06 JD: ORCA does everything through the AAPI, which gets most of its info from the DOM... 16:25:36 ...could expose this info without it being in the DOM, like with CSS generated content 16:25:42 CN: and that is the common approach, correct? 16:25:59 JD: that is my understanding, but I don't know about JAWS and other windows Screenreaders 16:26:08 s/ORCA/Orca/ 16:26:13 CN: Still work to do on this topic. 16:26:15 q? 16:26:18 ack jan 16:26:56 JS: Here's a crazy idea. I get nervous about anything keyboard centric since we are seeing more touch and voice interaction 16:27:53 ...if we are saying that the user supplies the keys, were not just talking about a standard web page, its pages the user uses frequently, like an app, where users would take advantage of such a shortcut. 16:28:13 q+ to shoot you down (not really…) 16:28:31 ...perhaps we leave it entirely up to the user, that they can add their own shortcuts to any focusable content 16:29:11 CN: the activation behavior, may be a gesture rather than a key, could also be a voice command. We need to be very careful. At the bottom of the page, there is a statement that hints at this. 16:29:18 ...can't just be a single key 16:29:35 ...need to support various interactions 16:30:19 ...agree that pages you are not likely to visit often, user won't hunt around for accesskeys. The approach of allowing the user to create their own bookmarks/shortcuts would be a UA feature, nothing to do with HTML 16:31:35 JS: I wonder if we made the automatic enumeration of elements, like Lynx did, you could port your shortcuts across environments 16:31:44 q+ 16:31:45 CN: like XPointer, but not something you would put in HTML spec. 16:31:53 ack me 16:31:53 chaals, you wanted to shoot you down (not really…) 16:31:55 ack li 16:31:55 liam, you wanted to support/ask-about more user control of access keys, e.g. rebinding 16:32:43 LQ: the web annotations working group is facing the problem of how to annotate a piece of the document. Associating text with a particular part of the page could be extending to supporting shortcuts 16:33:17 ...To what extent is user control of accesskeys available? Can you override them? 16:33:28 CN: only through extensions at this point, i believe. 16:33:40 ...support for access keys in general is poor to terrible. 16:34:04 ack pl 16:34:09 ...Opera mini probably has the best implementation of allowing users to overwrite 16:34:44 PLH: I wanted to agree with chaals, this is about getting the config from one UA to another. As soon as you start talking about making the config portable, its not within the realm of HTML 16:34:55 ...nice to have, I agree, but outside of HTML scope. 16:35:22 [Liam wonders where plh feels such a conversation _could_ occur (agree not HTML spec) ] 16:36:32 [sure, but don't we have a long list of things to tackle for HTML?] 16:36:38 CN: think we should look into a way of revealing what the shortcuts are. No JS API currently. 16:36:50 ...would be helpful to expose what the shortcuts are 16:37:32 JS: I like that idea a lot. I can see a l lot of applications that could benefit from that. 16:37:34 s/the shortcuts are/executable things are in the page and can they have an identifier/ 16:37:43 s/the shortcuts are/executable things are in the page and can they have an identifier/ 16:38:45 q+ 16:38:47 CN: is the obvious way to do this writing an extension spec, or file bugs on HTML? Paul? 16:38:54 ack ju 16:39:24 JB: I would think that the end goal would be to integrate solution into the HTML spec. Extension spec for development, but path back into HTML 16:39:42 ...consider tapping into tabindex at the same time 16:40:00 I suggest you talk to Robin about making the accesskey part of HTML5 (and other items like tabindex) into a "After HTML5" module so that it can be worked on following his new development methodology. 16:40:05 ...don't think a lot of incremental bugs is the most useful path. anyone else? 16:40:07 q+ 16:40:30 PC: I suggest talking to Robin about turning this topic into a module that people can start working on. 16:40:33 s/Extension spec/Potentially extension spec/ 16:40:40 ack pl 16:40:44 ...get it into github so people can start contributing and commenting 16:41:11 PLH: Should work it as a module, with possible integration later on. Agree that module is good idea and talking to robin 16:41:16 ack plh 16:41:23 The module should probably include some part of http://www.w3.org/html/wg/drafts/html/CR/editing.html#assigning-keyboard-shortcuts 16:41:25 ACTION: chaals to talk torobin about an accesskey (maybe etc) module for HTML 16:41:25 Created ACTION-294 - Talk torobin about an accesskey (maybe etc) module for html [on Charles McCathie Nevile - due 2014-12-25]. 16:41:37 zakim, take up next item 16:41:37 agendum 4. "First meeting of 2015: date?" taken up [from chaals] 16:42:10 CN: this is last meeting for 2014. What date should we resume in 2015? 16:42:11 january 8? 16:42:17 Thu Jan 8 would be the likely candidate for next meeting. 16:42:34 +1 16:42:36 Jan 1 is obvious the first Thu and is NOT a candidate. 16:42:37 +1 16:42:39 +1 16:42:44 +1 16:42:46 Jan 8 +1 16:42:59 CN: January the 8th will be next meeting then 16:43:06 RESOLUTION: next meeting january 8th 16:43:14 +ShaneM.a 16:43:21 +[IPcaller] 16:43:50 zakim, [ip is leonie 16:43:50 +leonie; got it 16:44:04 zakim, take up next item 16:44:04 agendum 5. "Any other business?" taken up [from chaals] 16:44:06 -ShaneM 16:44:09 zakim, take up item 6 16:44:09 agendum 6. "longdesc question" taken up [from chaals] 16:44:31 CN: longdesc, Janina? 16:44:33 janina? 16:45:21 -chaals 16:45:31 janina has joined #html-a11y 16:45:47 -janina 16:46:21 PLH: I think MIT is experiencing network issues 16:46:35 ...anyone dialing in over IP will likely have issues 16:47:18 -LJWatson 16:47:32 Happy Holidays to everyone. 16:48:39 JB: Reminder for those from Member orgs to comment on PR with regards to longdesc. Janina had a question, but since she is not here... 16:49:03 ...I propose we end the call 16:49:13 -Plh 16:49:21 -ShaneM.a 16:49:47 LW: Chaals just messaged us that he would like to thank everyone for the last 12 months of work and to have a happy holiday 16:49:52 rrsagent, make minutes 16:49:52 I have made the request to generate http://www.w3.org/2014/12/18-html-a11y-minutes.html MarkS 16:50:20 -paulc 16:50:29 -leonie 16:50:36 -MarkS 16:50:38 -Adrian_Roselli 16:50:40 -Joanmarie_Diggs 16:50:43 sivoais_ has joined #html-a11y 16:50:44 -Judy 16:50:47 -IanPouncey 16:50:48 LJWatson has left #html-a11y 16:51:00 zakim, who is on the phone? 16:51:00 On the phone I see Liam 16:51:04 -Liam 16:51:06 WAI_PFWG(HTML TF)10:00AM has ended 16:51:06 Attendees were Judy, Adrian_Roselli, ShaneM, LJWatson, +1.617.319.aaaa, MarkS, janina, chaals, Joanmarie_Diggs, Liam, paulc, IanPouncey, Plh, [IPcaller], leonie 16:51:08 rrsagent, make minutes 16:51:08 I have made the request to generate http://www.w3.org/2014/12/18-html-a11y-minutes.html MarkS 16:57:00 liam, i can take care of it :) 16:57:04 working on it now 17:06:15 thanks! 18:40:53 wow liam, you've been busy! 18:50:03 :) 18:50:09 well, i didn't write the document 18:50:10 s 19:22:38 sivoais has joined #html-a11y 20:10:11 chaals has joined #html-a11y