19:57:35 RRSAgent has joined #aapi 19:57:35 logging to http://www.w3.org/2014/02/25-aapi-irc 19:57:37 RRSAgent, make logs member 19:57:37 Zakim has joined #aapi 19:57:39 Zakim, this will be WAI_PF 19:57:39 ok, trackbot; I see WAI_PFWG(AAPI)3:00PM scheduled to start in 3 minutes 19:57:40 Meeting: Protocols and Formats Working Group Teleconference 19:57:40 Date: 25 February 2014 19:58:24 WAI_PFWG(AAPI)3:00PM has now started 19:58:31 +[GVoice] 19:58:39 zakim, GVoice is Joseph_Scheuhammer 19:58:39 +Joseph_Scheuhammer; got it 19:58:47 zakim, I am Joseph_Scheuhammer 19:58:47 ok, clown, I now associate you with Joseph_Scheuhammer 19:59:03 chair: Joseph_Scheuhammer 19:59:12 agenda: this 19:59:21 agenda+ Having a core UAIG, one specific to HTML, and one to SVG. Also, when to start edits to the UAIG 1.1 core document. 19:59:30 agenda+ ISSUE-645: Remove 'checkable' object attribute from aria-pressed mapping. 19:59:41 agenda+ ISSUE-481/ACTION-1368/ACTION-1369: (David, Cynthia) aria-live removal events should/must happen before object removal. 19:59:49 +joanie 19:59:52 agenda+ ISSUE-441/ACTION-1372: (Cynthia) Test case for incomplete use of aria-posinset/aria-setsize. 19:59:55 bgaraventa1979 has joined #aapi 20:00:02 agenda+ ISSUE-618/ACTION-1371: (Cynthia) Investigate how IE implements item de-selection in single selection container. 20:00:10 agenda+ ISSUE-635/ACTION-1372: (Cynthia) Create test case for rowgroup role. 20:00:22 agenda+ ISSUE-644: (All) Update ATK/AT-SPI mapping for aria-hidden="true" to reflect elements should not be exposed/mapped. 20:00:32 agenda+ 1.1 ISSUES and ACTIONS: (All) Start with ISSUE-540, https://www.w3.org/WAI/PF/Group/track/products/23 20:00:42 agenda+ be done. 20:00:48 zakim, agenda? 20:00:48 I see 9 items remaining on the agenda: 20:00:49 1. Having a core UAIG, one specific to HTML, and one to SVG. Also, when to start edits to the UAIG 1.1 core document. [from clown] 20:00:49 2. ISSUE-645: Remove 'checkable' object attribute from aria-pressed mapping. [from clown] 20:00:49 3. ISSUE-481/ACTION-1368/ACTION-1369: (David, Cynthia) aria-live removal events should/must happen before object removal. [from clown] 20:00:50 4. ISSUE-441/ACTION-1372: (Cynthia) Test case for incomplete use of aria-posinset/aria-setsize. [from clown] 20:00:52 5. ISSUE-618/ACTION-1371: (Cynthia) Investigate how IE implements item de-selection in single selection container. [from clown] 20:00:52 6. ISSUE-635/ACTION-1372: (Cynthia) Create test case for rowgroup role. [from clown] 20:00:52 7. ISSUE-644: (All) Update ATK/AT-SPI mapping for aria-hidden="true" to reflect elements should not be exposed/mapped. [from clown] 20:00:52 8. 1.1 ISSUES and ACTIONS: (All) Start with ISSUE-540, https://www.w3.org/WAI/PF/Group/track/products/23 [from clown] 20:00:56 9. be done. [from clown] 20:01:36 + +1.650.773.aaaa 20:02:47 Bryan Garaventa 20:03:06 zakim, aaaa has Bryan_Garaventa 20:03:06 +Bryan_Garaventa; got it 20:03:21 zakim, bgaraventa1979 is Bryan_Garaventa 20:03:21 sorry, clown, I do not recognize a party named 'bgaraventa1979' 20:03:34 zakim, Bryan_Garaventa is bgaraventa1979 20:03:34 sorry, clown, I do not recognize a party named 'Bryan_Garaventa' 20:03:54 Zakim, I am Joanmarie_Diggs 20:03:54 sorry, joanie, I do not see a party named 'Joanmarie_Diggs' 20:04:26 richardschwerdtfeger has joined #aapi 20:04:35 zakim, who's on the phone? 20:04:35 On the phone I see Joseph_Scheuhammer, joanie, +1.650.773.aaaa 20:04:36 +1.650.773.aaaa has Bryan_Garaventa 20:04:46 what is the call in passcode? 20:04:49 zakim, i m bryan_garaventa 20:04:49 I don't understand 'i m bryan_garaventa', bgaraventa1979 20:04:52 zakim, joanie is Joanmarie_Diggs 20:04:52 +Joanmarie_Diggs; got it 20:05:04 richardschwerdtfeger: 2274# 20:05:27 +Rich_Schwerdtfeger 20:06:44 +[Microsoft] 20:06:50 http://www.w3.org/WAI/PF/aria-1.1/ 20:06:57 zakim, i am Bryan_Garaventa 20:06:57 sorry, bgaraventa1979, I do not see a party named 'Bryan_Garaventa' 20:07:11 cyns has joined #aapi 20:07:30 zakim, who's here? 20:07:30 On the phone I see Joseph_Scheuhammer, Joanmarie_Diggs, +1.650.773.aaaa, Rich_Schwerdtfeger, [Microsoft] 20:07:32 +1.650.773.aaaa has Bryan_Garaventa 20:07:32 On IRC I see cyns, richardschwerdtfeger, bgaraventa1979, Zakim, RRSAgent, davidb, clown, MichaelC, joanie, trackbot 20:08:37 scribenick: joanie 20:09:00 Zakim, take up agenda 20:09:00 I don't understand 'take up agenda', joanie 20:09:04 Zakim, take up item 1 20:09:04 agendum 1. "Having a core UAIG, one specific to HTML, and one to SVG. Also, when to start edits to the UAIG 1.1 core document." taken up [from clown] 20:09:30 RS: We have an outline we were going to do.... 20:09:52 http://www.w3.org/WAI/PF/wiki/Outline_Core_User_Agent_Implementation_Guide#Core_User_Agent_Implementation_Guide 20:10:11 RS: The bulk of the 1.1 Implementation Guide would go into the core 20:10:29 RS: What we can do is create implementation guides for HTML 5.1 and SVG 2 based on the core 20:10:43 RS: Instead of having to go back and duplicate role mappings, we can refer back 20:10:54 RS: There are features in the host language we'll have to define there 20:11:03 RS: Examples are name and description computations 20:11:43 https://svgwg.org/svg2-draft/struct.html#implicit-aria-semantics 20:11:46 RS: In the document structure section of the specification, we define how ARIA integrates into the specification 20:11:54 RS: We also have a new host language semantics section 20:12:10 RS: In each of these we have a defined role and how it gets mapped into the accessibility API 20:12:32 RS: The other thing we are doing, for those elements which can be mapped, we try to say they have a presentation role unless something else gets added to them to cause them to be mapped 20:12:51 RS: Because everything in SVG is persistent, we don't want to map everything to the tree unless we have to 20:13:06 RS: When do we create a role in the accessibility tree is going to be very important 20:13:47 presentation role provided no associated ‘title’ element, ‘desc’ element, ‘aria-label’ attribute, ‘aria-labelledby’ attribute, or ‘aria-describedby’ attribute; otherwise, group role 20:14:28 RS: Beyond that, there are no restrictions 20:15:04 RS: If you put some sort of text inside a circle (e.g. title, label) it would get mapped to group. 20:15:13 RS: We are going to be defining host language semantics 20:15:23 RS: We can then point to the core specification 20:15:33 RS: The HTML and SVG DOM stuff are all getting merged 20:15:37 RS: EVen the event handlers 20:15:49 RS: Other interesting things about SVG are 20:16:00 RS: You can embed an iframe in SVG, also a canvas element 20:16:06 RS: I have to think about what that means 20:16:13 RS: Is the fallback HTML or SVG? 20:16:25 JS: So the canvas element is the same? 20:16:26 https://svgwg.org/svg2-draft/embedded.html#CanvasElement 20:16:47 RS: That's correct. 20:17:00 RS: The good thing is we have one DOM and a common set of attributes. 20:17:08 RS: The question I have is, does that make sense? 20:17:23 RS: Are we going to take ARIA 1.1 and add it to the core? 20:17:25 JS: Yes 20:17:51 JS: We already have a promise to the GNOME Accessibility Team 20:17:55 JS: I want to get that going 20:18:04 JS: That draft (ARIA 1.1) could start out as the core 20:18:15 JS: Then you could start taking things out or whatever you need to do 20:18:27 RS: I like the way the HTML and SVG specs expand and collapse elements 20:18:34 RS: Are you going to do that? 20:18:40 JS: I wanted to get that done for 1.0 20:19:08 JS: But the script doesn't work with the table in the UAIG 20:19:18 JS: The table markup is slightly different 20:19:51 http://www.w3.org/TR/2012/WD-html-aapi-20120329/ 20:20:24 CS: (Confirms what Jospeh stated) 20:20:37 JS: The document you put in Rich looks like what I was refering to 20:20:45 RS: I can expand them but not collapse them 20:20:52 JS: I should ask Jason about this 20:21:06 RS: I don't think you can expand or collapse them with the keyboard 20:21:49 (Discussion on how there is an option at the top to toggle all) 20:21:59 JS: I think they are using re-spec(?sp) 20:22:15 JS: You write the spec with staright HTML in one file 20:22:28 JS: And you include this re-spec javascript and it does all the formatting, etc. 20:22:35 JS: What we do for the ARIA documents... 20:23:00 JS: We have a core document and an XSLT processor 20:23:21 JS: And it puts everythign together, adds table of contents, creates a full HTML document 20:23:28 RS: Does anyone have the source for it? 20:23:33 CS: You'll have to ask Jason 20:23:50 JS: I have the javascript. It's in the document itself. 20:23:56 RS: We need to get the original 20:24:04 JS: It's probably in W3C's mercurial repo 20:24:14 CS: Jason will know and Steve Faulkner will know 20:24:34 (Discussion about this might not being the right/same document) 20:24:41 http://www.w3.org/TR/html-aapi/ 20:24:42 http://rawgithub.com/w3c/html-api-map/master/index.html 20:25:12 RS: I didn't know you could put W3C docs on github 20:25:19 CS: Anyway, email Jason and Steve 20:25:26 JS: This one works with the keyboard 20:25:32 RS: We definitely want this one 20:25:49 RS: So who is going to be the editor of the HTML 5.1 one? 20:25:59 CS: I just asked for that to be put on the Task Force agenda 20:26:08 CS: Steve doesn't have time, Jason doesn't have time 20:26:19 CS: We need people 20:26:45 RS: I'll talk to Steve about this 20:26:53 RS: We need to figure out who is going to edit this 20:27:03 RS: I don't have bandwidth for this. I might to SVG 20:27:15 CS: I have bandwidth to provide details about how IE does things 20:27:23 JS: I have bandwidth to work on the core right now 20:28:05 RS: Will we have the UIA for 1.1? 20:28:15 CS: I cannot answer that yet 20:28:42 RS: They have a single table too 20:28:59 JS: When I looked at it you gave it the ID of the table element and it would do that table 20:29:05 JS: So you could do it for multiple tables 20:29:13 RS: Given that most of this will be in the core spec.... 20:29:19 RS: This should go in the core, right? 20:29:23 JS: The HTML one? 20:29:30 RS: The table mapping for the APIs 20:29:40 RS: What they have here is like anchor 20:29:45 RS: It goes to a link role 20:29:57 JS: To you want this anchor list to be in the core? 20:29:59 RS: No 20:30:07 RS: You are going to have an equivalent in the core spec 20:30:31 RS: All the API mappings will be 20:30:34 JS: What they are now 20:30:41 RS: But it wouldn't be in the HTML spec 20:30:53 CS: It would be in the HTML mapping guide because HTML and ARIA aren't the same thing 20:31:06 JS: I think Rich is saying you'd put a link to the core 20:31:31 (Discussion on specific examples to clarify the point) 20:31:47 CS: I disagree that mapping from HTML to accessibility APIs should have to go through ARIA 20:31:53 RS: But that is what we are doing 20:31:59 RS: This is needed for SVG 20:32:09 RS: I don't know if we'd call it "ARIA" 20:32:28 RS: But it doesn't make sense to duplicate it 20:32:34 RS: It makes sense to have it in one place 20:32:45 CS: But if I'm implementing HTML, why do I have to look in two specs? 20:32:52 RS: Trying to keep them in sync is a nightmare 20:33:07 RS: That is why we want to have one core spec that define things in terms of ARIA symantics 20:33:29 RS: What we want to do is have a core implementation guide that defines the mapping for those symantics in it 20:33:38 RS: We'd refer back to the core spec where we can 20:33:52 RS: But not with things like name computation 20:34:17 CS: What about places where HTML and something else has a mapping, but ARIA does not? 20:34:23 RS: Then we'd have to take the HTML version 20:34:53 JS: You could populate the HTML version by pulling the mapping out of the core, e.g. via AJAX 20:35:06 JS: Use the UAIG core as the database 20:35:11 RS: Yeah, you could do that 20:35:23 JS: As you load the mapping table, it fetches content (done in the browser) 20:35:42 CS: One of the things I'd like to do is see what features are missing from my API 20:35:53 CS: Having a place where they are all together would be helpful 20:36:02 RS: Did you file the bugs after we went through CR? 20:36:06 CS: Yes 20:36:37 CS: I want to be able to explain both to IE and authors is the relation between HTML and UIA 20:36:47 CS: The levels of indirection makes that harder 20:36:57 RS: I don't think there are that many levels of indirection 20:37:08 CS: Having a view that puts this together would be very helpful 20:37:18 CS: I think the script Jason has would be able to do that 20:39:02 (more discussion about the above) 20:39:24 CS: Are you ok with us owning this html piece as well 20:39:33 JS: Who is "we"? 20:39:42 JS: I'm not able to be the editor 20:39:54 CS: I'm trying to get the same level of productivity? 20:40:02 JS: Would it be part of this call? 20:40:08 CS: (confirms) 20:40:19 CS: We'd have to find another editor 20:40:26 JS: We can ask 20:40:35 RS: I'm not sure if David will have time 20:40:46 RS: It sounds like we need a call with Jason 20:41:07 CS: I got some feedback from Jason about where things stand now and his availability 20:41:33 CS: There was a timezone issue in the past (e.g. Toronto, Siberia, New Zealand) 20:42:03 RS: So we just need editors for HTML 5 and the other one 20:42:12 JS: I'm willing to try to bring the HTML 5 issues to this call here 20:42:21 JS: But I am afraid we will run out of time 20:42:24 JS: We can try 20:42:34 RS: We will have to coordinate things like name computation 20:42:43 JS: I think 90% of name computation is core 20:42:52 RS: It's going to be different for HTML 5 and SVG 20:43:03 RS: (gives example) 20:44:10 http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_nd 20:44:34 RS: It's called placeholder 20:44:46 http://rawgithub.com/w3c/html-api-map/master/index.html#input-type-text-input-type-password-input-type-search-input-type-tel-input-type-url-and-textarea-element 20:45:13 CS: How does that figure into name calculation 20:45:24 CS: It's an aria-hint as far as I'm concerned 20:45:41 RS: (points out mobile use case) 20:46:01 CS: If there's not another label, the placeholder would go into the name 20:46:13 20:46:20 CS: If an image has both an alt and a title, then the alt is the name and the title is the description 20:46:26 CS: It would be similar with placeholder 20:46:35 RS: But this doesn't tell with the text before and after 20:46:56 20:47:16 davidb has joined #aapi 20:47:31 JS: Is the above how placeholder works? 20:47:38 CS: Yes 20:47:46 RS: It's meant to be for the label 20:48:00 RS: (looks for form example) 20:48:55 CS: In the example from the HTML spec it's got "sample text" 20:49:06 RS: Where they really started using this first is Apple 20:49:26 RS: You'd put "city" and when you started typing that text would go away 20:49:38 The html spec example says 20:49:40
20:50:44 BG: Is the placeholder text supposed to disappear when it gets focus? 20:50:50 BG: Or when you start typing? 20:50:52

20:51:08 RS: Basically what happens is that they put the text label in the input field as grey text 20:51:12 RS: This is to save space 20:51:19 RS: Then you don't need to put an actual label 20:51:28 RS: When you start typing, the grey text goes away 20:51:48 CS: And sometimes that's a bad experience for sighted users too 20:52:03 RS: I'm not trying to defend it; I'm just describing what it's been used for 20:52:22 CS: (Refers to text example from the spec she pasted in above) 20:52:42 http://www.w3schools.com/tags/att_input_placeholder.asp 20:52:50 RS: They put first name and last name 20:53:03 RS: (said in reference to the example he pasted in) 20:53:09 JS: They're trying to save space 20:53:23 RS: That is what I was saying 20:53:30 JS: You cannot select the text 20:53:39 RS: It's considered a vanishing, static label 20:53:58 (More discussion about this user experience and use cases) 20:54:15 RS: The fact that it's in the name computation must give it credence 20:54:23 CS: It's similar to the title attribute 20:54:36 JS: Firefox is setting the accessible name to the placeholder text in that case 20:54:54 CS: That's what we'd do too, I think. But it's the name of last resort 20:55:41 CS: Before there was placeholder, this was done via value and CSS 20:56:44 RS: The question is, do you put this in a hint and also in a name if nothing else is there? 20:57:04 JS: James Craig is writing the precedence as one of his 1.1 tasks 20:58:59 RS: I guess I can be the SVG editor, but I'd like to get some eyes on this 20:59:13 CS: Are the HTML working group going to be ok pulling this into core? 20:59:31 RS: I don't know if we've formalized it, but all the editors working on that spec agreed this is the way to go 20:59:40 RS: We haven't agreed on who is going to work on what yet. 21:00:09 JS: To wrap up.... 21:00:21 JS: In order to do anything we (or I) need help from Michael 21:00:27 JS: To find out how to fork the documents 21:00:39 JS: And how to do this work without interfering with what he is doing 21:00:44 JS: Otherwise we are stalled 21:00:50 RS: Was he supposed to be on the call? 21:01:08 CS: as long as there is a way to see all, I am ok with breaking this into core/html/svg. We have had trouble with staffing and progress on the HTML doc. pulling things into core would make html - api mapping smaller, which might help with staffing. 21:01:08 JS: I was hoping he would be. Before Christmas he was. Since then he's been busy. 21:01:24 JS: I will ask him how we can go ahead. 21:01:34 RS: I am going to send him a note now. 21:01:45 -Rich_Schwerdtfeger 21:01:54 JS: Let's call it the end of meeting. 21:01:55 -[Microsoft] 21:01:59 - +1.650.773.aaaa 21:02:41 Zakim, part 21:02:41 leaving. As of this point the attendees were Joseph_Scheuhammer, Bryan_Garaventa, Joanmarie_Diggs, Rich_Schwerdtfeger, [Microsoft] 21:02:41 Zakim has left #aapi 21:02:54 regrets: David_Bolter 21:03:21 RRSAgent, stop