that will look like a td when aria-interactive is false? 16:54:27 MK: Yes. 16:54:37 MK: At the moment, we're only put this on grid and list. 16:55:09 MK: I changed the ontology. 16:55:28 MK: Previously, list had as subclasses menu and directory. 16:55:40 MK: And directory had tablist as one of its subclasses. 16:56:04 MK: I removed menu from list and tablist from directory. Now both tablist and menu are composites and do not inherit from list. 16:56:21 MK: Now aria-interactive will operate on grid, treegrid, list, and directory. 16:56:51 RS: Were there any inherited states and properties lost as a result? 16:56:56 MK: I don't think so. 16:57:03 JD: I had checked. The answer is no. 16:57:08 RS: Just double-check it. 16:57:19 MK: There's one more change if the group still wants to go in this direction. 16:57:38 MK: I can see both plusses and minuses to this approach. 16:57:47 MK: I'm not sure this will be better than adding new roles. 16:57:56 RS: I think people are already doing this anyways. 16:57:59 Editorial comment: aria-interactive in "list" has an and whitespace before it in the table entry 16:58:27 RS: For instance using grid as a non-interactive table. I've heard this is already happening in the wild. 16:59:17 MK: I think when you're nesting tables in tables, you really need to be explicit.... I cannot think of any situation when you'd want to have an interactive child inside a non-interactive parent or vice versa. 16:59:45 MK: For example, in a static table you don't need to make the sortable column headers interactive. Just make them standarrd links, right? 16:59:59 RS: It's less likely if you're using divs and spans. 17:00:32 q+ 17:00:34 RS: If someone wants to embedded a grid in a cell of a non-interactive grid, you are not prohibiting that. 17:00:42 MK: Correct. 17:00:49 RS: Did you look at treegrid? 17:00:57 MK: Not yet. 17:01:19 JG: Is aria-interactive considered a repair technique? 17:01:23 RS: No, I don't think so. 17:01:49 JG: But you're using grids, and if you put this on it, you're making it non-interactive. 17:02:01 JG: What's the difference between a non-interactive grid and a table? 17:02:05 MK: Nothing. 17:02:39 MK: This gives us a way to support tables in host languages which lack them. 17:03:04 MK: On the flip side, on a static element like list, this will result in a new interactive widget: a listview. 17:03:11 MK: That's a capability we didn't have before. 17:03:28 JG: So a gridcell can be interactive or not based on this property? 17:03:34 MK: A grid can be. 17:03:43 JG: This will be interesting to explain to authors. 17:04:04 MK: I was thinking about this. And this is one reason I'm not convinced this is better than new roles with respect to authoring. 17:04:19 RS: I think we're ok for now. Let's see what happens in the wild if people complain. 17:04:32 JG: Besides list and grid, how many other candidates are there? 17:04:39 MK: In my estimation, not many. 17:04:55 MK: Related, why isn't toolbar a composite? 17:05:09 JS: I agree with you, but this discussion was raised at least twice before. 17:05:20 JS: The conclusion was that a toolbar should be a structure. 17:05:40 RS: If you want to raise an issue, raise an issue. 17:05:45 zakim, ack me 17:05:45 clown, you wanted to note that practically any element can be made interactive via script. 17:05:48 I see jongund on the speaker queue 17:05:58 https://lists.w3.org/Archives/Public/public-pfwg/2015May/0078.html 17:06:05 Topic: ARIA Extension Review 17:06:12 https://www.w3.org/WAI/PF/wiki/ARIAExtensions 17:06:14 RS: Shane and I worked on this a bit. 17:06:22 RS: Are people happy with this? 17:06:24 mattking has joined #aria 17:06:46 Janina: In the global thing, I think we maybe want to decide between "extension" or "module". 17:06:59 Janina: The why is because what happens once it is accepted. 17:07:18 q+ to answer janina 17:07:20 Janina: On the user agent side, you have to implement it because it's part of the ARIA specification. Right? 17:07:25 CS: I'm not sure. 17:07:54 CS: Thinking out loud, there are pieces. For instance, patterns I think can be pretty separable. 17:08:14 CS: You could support one without the other and it would still work. You'd have holes, but it should work. 17:08:43 q? 17:08:45 Janina: We need disambiguation somewhere (e.g. the "part" role). 17:08:53 ack jongund 17:09:29 Shane: I think anything that becomes a W3C REC (see item 4), then it's required. 17:09:38 Shane: (Reads from his text) 17:10:03 Shane: It should say "every conforming ARIA implementation". 17:10:14 Shane: But that's my opinion, and not what Cynthia is saying. 17:10:21 q? 17:10:27 ack ShaneM 17:10:27 ShaneM, you wanted to answer janina 17:10:27 ack ShaneM 17:10:36 CS: I'm thinking about how this will be implemented in software. 17:10:49 CS: It's a collection of features that fits into a milestone. 17:11:05 CS: If it maps to something, that makes it easier to implement. 17:11:17 CS: If it's a big monolithic spec, that's harder to accomplish. 17:11:29 RS: I want to separate spec from extension. 17:11:35 q+ 17:11:47 RS: If something can be implemented broadly, we can put that in a spec. 17:12:08 RS: If it's specific to a particular area/industry, like digital publishing, we'd put it into a module. 17:12:38 RS: It's also possible that the digital publishing would not go into a regular browser implementation; just a digital publishing version of that browser. 17:12:40 q+ 17:12:57 ack tzviya 17:13:17 Tzviya: I think it would be helpful in writing the module, if we could leave the concept of roles being brought into the master specification aside. 17:13:41 Tzviya: I don't want to have to keep track of which role is implemented where. 17:14:03 Tzviya: I think it's great that roles might be incorporated into the master spec, but I think we should set that aside for now. 17:14:47 RS: You have a timeline. If there were certain things we wanted in the ARIA spec, if we get it in in time, would that meet your needs? 17:15:13 q+ to talk about duplication and semantics 17:15:27 Tzviya: We'd like to avoid duplication (e.g. a chapter role in both the core spec and the DPUB spec). 17:15:31 RS: So would I. 17:15:48 RS: If we do it quickly, we could put it in a heartbeat draft. Then you wouldn't have to do it. 17:16:05 Tzviya: We'd want to know from the outset what direction we're headed in. 17:16:06 ack janina 17:16:19 Janina: Trying to get all of this resolved in the W3C. 17:16:38 Janina: PF is expected to take issues having to do with HTML to the task force. 17:17:02 Janina: We are going to try to invite everyone soon, perhaps at next week's telecon, to discuss this. 17:17:13 Janina: 11:00 Eastern. 17:17:31 Janina: So we can discuss and move to a solution that works for everyone. 17:18:04 Janina: We also need to discuss how a user agent developer knows how they have version x.y of a spec implemented. 17:18:11 RS: That's true for HTML now. 17:18:18 q? 17:18:23 Janina: No, HTML extensions are part of the spec. 17:19:10 Tzviya: Reads from @@. 17:19:38 s/Tzviya: Reads from @@.// 17:20:01 RRSAgent, make minutes 17:20:01 I have made the request to generate http://www.w3.org/2015/05/14-aria-minutes.html joanie 17:20:23 RS: I shared this ARIA extensions with Steve, and he doesn't seem to have any issues with it. 17:20:37 q+ 17:20:42 chair: Rich_Schwerdtfeger 17:20:52 I have made the request to generate http://www.w3.org/2015/05/14-aria-minutes.html clown 17:20:58 q+ cynthia 17:21:02 ack ShaneM 17:21:02 ShaneM, you wanted to talk about duplication and semantics 17:21:43 Shane: If something gets approved it's part of the core. 17:22:40 Shane: If there are things that use the same term, obviously they need to be distinguished. Perhaps through a prefix. 17:22:48 Shane: However, that's what PF is for. 17:23:14 Shane: We need to ensure that roles work well across the board whenever possible. 17:23:23 q+ to say it´s hard to predict future collisions, to decide what might need prefixing and what doesn´t 17:23:25 q+ 17:24:00 RS: When a group creates a module, as long as we don't have a collision, we should have bottlenecks and trying to redefine industry language. 17:24:12 RS: These people working on this spec are experts in this area. 17:24:21 q+ to ask about extensiblity of extensions 17:24:27 ack richardschwerdtfeger 17:24:30 RS: We should try to be respectful and just worry about the conflict issues, and ensure we have good mappings. 17:24:30 ack r 17:24:30 ack c 17:24:53 q+ 17:24:54 CS: One issue is roles for an area. Another is OS features. 17:25:02 CS: These may need to be treated separately. 17:25:18 CS: From a user agent perspective, it's nice to be able to say "I've implemented this piece." 17:25:21 q+ 17:25:28 CS: For really big specs, that's more difficult. 17:25:34 ack MichaelC 17:25:34 MichaelC, you wanted to say it´s hard to predict future collisions, to decide what might need prefixing and what doesn´t 17:25:45 MC: About collisions, I think Shane is right. We're here to ensure there are not collisions. 17:25:56 MC: However that's hard to predict. 17:26:12 MC: Example if we were going to do music, "ARIA" might not have been chosen. 17:26:24 ack fesch 17:26:35 FE: Two things. One is you worry about what you can pass to ATs. 17:26:53 FE: With graphics, you want to expose that role to ATs, like "axis". 17:27:06 FE: You don't want to be limited to a small set of limited terms. 17:27:15 q? 17:27:32 FE: The other thing is navigation. You need to provide keys and information so that you can adjust and provide better understanding. 17:27:34 ack tzviya 17:27:34 tzviya, you wanted to ask about extensiblity of extensions 17:27:41 q+ 17:27:55 Tzviya: In Digital Publishing, we hope to be able to extend our extension in the future. 17:27:56 q+ to point out that role synonyms are very low cost to support 17:28:03 q- 17:28:11 Tzviya: For instance, terms related to education and assessment. 17:28:35 RS: That's why the nice thing about the prefix thing is that it will allow you to do what you want to do without name collisions. 17:29:00 RS: Cynthia, we haven't even looked at the API extensions, but that doesn't mean we can't change this down the road. 17:29:07 q+ to mention that collisions are not just about the LEXICAL name. They are about the behavior and semantics. 17:29:10 RS: I think HTML changed it a couple of times in the past. 17:29:20 RS: So if we need to do something, we can do it later on. 17:29:34 RS: Does anyone have any fundamental issues with what we have at the moment? 17:29:39 Janina: I don't. 17:29:55 CS: Please read it. 17:30:04 RS: (Reads it) 17:30:13 https://www.w3.org/WAI/PF/wiki/ARIAExtensions 17:30:25 The above text is what RS is reading from. 17:33:44 CS: That all sounds great for adding roles. 17:33:58 CS: But that doesn't address extensions I'd like to add. 17:34:39 MK: In response to what Fred said, it's my understanding that ATs don't have to use the rolenames explicitly. They can translate it however they want/need to. 17:35:01 MK: I don't think you should assume that the rolenames exposed will not be the rolenames presented by ATs. 17:35:05 q? 17:35:12 ack richardschwerdtfeger 17:35:16 ack mattking 17:35:36 MK: ATs are not obligated to use the rolename as stated in the spec. 17:35:56 RS: Right. We cannot dictate the AT presentation. 17:36:02 q? 17:36:19 MK: Example "combo box" might be presented as "pick list" (hypothetically) 17:36:28 q/ 17:36:31 q? 17:36:39 JS: The accessibility APIs frequently have ways to do localization. 17:36:50 ack ShaneM 17:36:50 ShaneM, you wanted to point out that role synonyms are very low cost to support and to mention that collisions are not just about the LEXICAL name. They are about the behavior and 17:36:53 ... semantics. 17:36:57 q? 17:37:08 q+ to propose generic vs specific delineation 17:37:36 Shane: James Craig has stated that role synonyms are very low cost to support. Example, role presentation and role none. 17:38:14 Shane: But, it's always been my assuption that the role which gets matched by the browser is exposed to the ATs. 17:38:31 Shane: But I'd hope the other roles can still be obtained. 17:38:45 Shane: As an AT. I can find out the real role value. 17:39:00 MK: I'm not sure that's the case on all platforms. 17:39:06 CS: In Windows, you can. 17:39:29 q+ to mention item 5 at http://w3c.github.io/aria/core-aam/core-aam.html#roleMappingGeneralRules 17:39:33 tzviya has joined #aria 17:39:33 CS: We use the constant for the similar role, along with a localizable string that's closer to the ARIA role. 17:39:49 CS: I think Apple has a similar mechanism. 17:40:04 q? 17:41:11 http://w3c.github.io/aria/core-aam/core-aam.html#roleMappingGeneralRules 17:42:04 JS: The URL above, says "User agents must expose the WAI-ARIA role string if the API supports a mechanism to do so. This allows assistive technologies to do their own additional processing of roles." 17:42:47 CS: The goal is to have the platform APIs be as rich as ARIA. 17:43:04 zakim, ack me 17:43:04 clown, you wanted to mention item 5 at http://w3c.github.io/aria/core-aam/core-aam.html#roleMappingGeneralRules 17:43:06 I see janina on the speaker queue 17:43:09 Shane: The other point I wanted to make is that it's not about the string, it's what the string means. 17:43:35 q+ Cynthia 17:43:50 Janina: I was going to suggest we have some global statements and some module statements. 17:44:00 Janina: I think this is what Cynthia was talking about earlier. 17:44:13 Janina: Example, someone might want to extend states. 17:44:43 Janina: We should probably add a statement that the extensions currently under consideration pertain to roles. But that there are potentially others. 17:45:18 Shane: What Cynthia is talking about is dynamically extending the taxonomy. 17:45:28 CS: (Confirms that) 17:45:49 CS: I heard several constraints about adding roles and properties, and not other features. 17:45:59 CS: We're going to need to deal with this. 17:46:11 RS: I think we'll have to deal with it for ARIA 2. 17:46:30 RS: For example, the WAPA work. 17:46:36 CS: It doesn't say that. 17:46:40 RS: Because I didn't think of it. 17:46:51 RS: Do you want us to say this for ARIA 1.x? 17:47:11 q? 17:47:13 CS: I'll look at it later today. I don't want there to be an ARIA 1.2; I want to get started on ARIA 2.0. 17:47:18 ack ja 17:47:18 janina, you wanted to propose generic vs specific delineation 17:47:21 ack janina 17:47:28 RS: Whatever we do for 2.0 cannot break the 1.1 extensions. 17:47:29 ack Cynthia 17:47:44 Shane: Cynthia, please feel free to edit the wiki. 17:47:59 RS: Janina, can we add this to next Wednesday's call? 17:48:02 q? 17:48:02 Janina: Yes. 17:48:26 RS: Aside from any additions by Cynthia, are we all set? 17:48:41 RS: Should we put a version on this? 17:48:52 CS: You may want to do so as I may have some significant edits. 17:48:55 Shane: I agree. 17:49:29 q? 17:49:59 Topic: Review Open Action Items and Issues 17:50:54 action-1361 17:50:54 action-1361 -- James Nurthen to Suggest new text for the application role -- due 2015-04-02 -- OPEN 17:50:54 https://www.w3.org/WAI/PF/Group/track/actions/1361 17:51:03 JN: I haven't done it. 17:51:08 RS: I know. :) 17:51:28 JN: I'm not sure when I can get to this. 17:51:40 MK: I'm lined up to do aria-selected. 17:52:04 MK: If this action is important, I am willing to look at his action after I do aria-selected. 17:52:21 RS: How about I assign it to you Matt? 17:52:38 MK: Two weeks from today for action-1361. 17:53:37 action-603? 17:53:38 action-603 -- James Craig to Add thead markup to UAIG so headers are readable on multi-page printouts -- due 2010-06-30 -- CLOSED 17:53:38 https://www.w3.org/WAI/PF/Group/track/actions/603 17:54:06 issue-603 17:54:06 issue-603 -- Need an attr to indicate element activation triggers audio, video, etc. -- open 17:54:06 https://www.w3.org/WAI/PF/Group/track/issues/603 17:54:16 action-1363? 17:54:16 action-1363 -- James Craig to Patch issue-603: aria-startsmedia -- due 2015-03-12 -- OPEN 17:54:16 https://www.w3.org/WAI/PF/Group/track/actions/1363 17:57:46 action-1380 17:57:46 action-1380 -- James Craig to #presentation should mention aria-hidden vs presentation role on raster and vector images in relation to ACTION-1379 -- due 2015-02-13 -- OPEN 17:57:46 https://www.w3.org/WAI/PF/Group/track/actions/1380 17:58:03 RS: Can you look into this Joanie? 17:58:36 JD: I can look into it, but it won't be next week. 17:59:35 JD: June would be lovely. 17:59:57 q+ 18:00:08 q? 18:00:17 JG: Testing plans for ARIA 1.1? 18:00:25 RS: We should probably do that. 18:00:36 RS: But should figure out what's going to happen with the charter. 18:00:50 MC: Testing is on my radar, but on the backburner currently. 18:01:08 MC: Do we want to use the existing harness or Test The Web Forward. 18:01:30 MC: The latter doesn't support direct access to accessibility APIs. 18:01:45 RS: The group would love that. 18:01:55 Janina: If we want to be in CR, we need to be testing. 18:02:03 CS: Six months might be doable. 18:02:36 RS: Should annotations be moved out to ARIA 2.0? 18:02:45 CS: Could we make it an extension? 18:03:06 RS: Why not move it out to ARIA 2.0. And if need be, put it into an extension. Will that work? 18:03:10 CS: Yes. 18:03:31 RS: I'm trying to get ARIA 1.1 done. 18:05:14 RRSAgent, make log public 18:05:29 Meeting: W3C WAI-PF ARIA Caucus 18:05:37 chair: Rich 18:06:02 http://www.w3.org/2015/04/draft-aria-charter 18:06:15 Topic: Charter 18:06:24 MC: http://www.w3.org/2015/04/draft-aria-charter 18:06:32 MC: The group should look at that. 18:06:57 RRSAgent, draft minutes 18:06:57 I have made the request to generate http://www.w3.org/2015/05/14-aria-minutes.html richardschwerdtfeger 18:07:13 present+ Matt_King 18:07:30 RRSAgent, make minutes 18:07:30 I have made the request to generate http://www.w3.org/2015/05/14-aria-minutes.html joanie 18:08:05 Zakim, part 18:08:05 Zakim has left #aria 18:09:09 RRSAgent, stop 18:11:52 s/window keeps crashing// 18:12:04 RRSAgent, make minutes 18:12:04 I have made the request to generate http://www.w3.org/2015/05/14-aria-minutes.html joanie 18:12:22 RRSAgent, stop