18:58:33 RRSAgent has joined #aria 18:58:33 logging to http://www.w3.org/2010/06/15-aria-irc 18:58:39 rrsagent, make log world 18:58:52 meeting: ARIA mapping - HTML A11Y TF 18:58:56 chair: Steve_Faulkner 18:59:22 agenda: http://lists.w3.org/Archives/Public/public-html-a11y/2010Jun/0151.html 19:00:26 WAI_PFWG(Aria)3:00PM has now started 19:00:33 +Michael_Cooper 19:02:11 +[IPcaller] 19:02:38 zakim, IPcaller is Stevef 19:02:38 +Stevef; got it 19:03:47 +Rich 19:04:35 janina has joined #aria 19:04:44 zakim, call janina 19:04:44 ok, janina; the call is being made 19:04:45 +Janina 19:08:13 +[Microsoft] 19:08:46 zakim, Microsoft is Cynthia_Shelly 19:08:46 +Cynthia_Shelly; got it 19:10:27 cyns has joined #aria 19:12:02 http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html 19:13:37 richardschwerdtfe has joined #aria 19:13:51 http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html 19:14:38 how do I make myself scribe? 19:15:16 SF: schould we use ARIA or WAI-ARIA in the doc? 19:15:30 scribe: cyns 19:16:02 JS: I think it's WAI-ARIA 19:16:43 SF: we have 2 tables. the first one used to be called strong native semantics. I changed it to elements with base sematnics that cannot be overridden 19:17:07 this first table is pretty much what's in the spec. The second table is elements with semantics than can be overriden 19:17:35 this table is the things we've talked about before 19:18:05 cyns has joined #aria 19:18:26 RS: did we call the button role? 19:18:40 i am here 19:18:47 i can hear 19:19:01 i will call back in 19:19:10 zakim, who is on the phone? 19:19:10 On the phone I see Michael_Cooper, Stevef, Rich, Janina, Cynthia_Shelly 19:19:10 ok. thanks. 19:19:13 -Stevef 19:19:48 +[IPcaller] 19:20:12 RS: si this waht we agreed to for details? 19:20:15 zakim, IPcaller is Stevef 19:20:15 +Stevef; got it 19:20:24 CS: I thought the summary child was the button 19:20:37 RS: implied semantics for details is that its labeled by summary 19:20:59 RS: we also found some bugs with the spec, that we need to address such as bug 92 19:21:15 SF: There are places where we still need to make decisions. 19:21:28 SF: we also need to address places where we don't agree with the restrictions. 19:21:38 CS: should we just start at the top? 19:21:56 RS: where we allow people to override, does this mean or, that is you cna have either one 19:22:17 RS: look at details. it's a reveal button. it reveals an area. 19:22:38 RS: it's only a combobox if someone decides to override it and make selectable entries inside it. 19:22:51 RS: we're saying what it can be overridden by. 19:23:04 SF: restrictions are what it can be overriden with. 19:23:06 RS: ok 19:23:21 RS: do we want to say that it controls the section that it's expanding. 19:23:30 SF: it could, but that's not what this table is about 19:23:36 RS: i meant the implied semantics 19:23:43 SF: we can put that in as well. 19:23:51 CS: do we want to? 19:23:59 SF: if they're helpfu we can add them in 19:24:25 SF: the main thing about the second table is that it has a lot fo things that used to be in the first table because there were more restrictions. 19:24:46 SF: what i need you to do is to go through and say if you agree of disagree, and bring it up and why. 19:26:54 scribe: janina 19:27:34 rich: input type should say what indeterminate is 19:27:46 steve: yes, but separate from what we're doing here 19:27:54 cyns has joined #aria 19:28:06 i'm back 19:28:47 steve: an aria check on a standard html checkbox should be quite rare 19:28:53 it's probably going to be pretty rare where a standard html text box is going to have an aria-checked on it? 19:28:58 cyns: seems like an easy beginner's mistake, though 19:29:07 CS: inexperienced authors may make that mistake. 19:30:07 cyns: perhaps having both should be a warning 19:30:10 steve: yes 19:31:01 steve: please read guidance for conformance checkers ... 19:31:14 sf: first, metadata content ... 19:31:50 cs: makes sense 19:32:08 rs: yes 19:32:58 sf: second table, anything form associated or interactive 19:33:50 sf: so, error if overwritten 19:34:14 cs: agree, but might want to say 'specified in the table above' or similar 19:35:27 sf: a warning if something other than what's allowed goes for the first table, which is more restrictive 19:37:08 cs: might be helpful to make our purpose more explicit 19:39:45 rich: are we saying validators must support a b and c -- is this what html-wg wants? 19:40:31 -Stevef 19:41:05 +[IPcaller] 19:42:17 -[IPcaller] 19:42:41 +[IPcaller] 19:43:04 i can hear you 19:43:17 i will ring in on another phone 19:43:27 -[IPcaller] 19:44:10 +[IPcaller] 19:47:16 sf: spec has referred to error/warning conditions, so i've based on our dicusssions 19:51:11 sf: tried to provide useful author guidance as well 19:52:54 cs: pretty subtle, but i like it 19:53:57 cs: think you're on the right track 19:54:04 rs: due when? 19:54:11 js: next week--the 24th 19:54:41 sf: obviously i agree with all this, i put it there 19:54:55 sf: can you all send a list of what you disagree? and we can focus on that? 19:54:59 cs: yes 19:55:30 rs: not today--will do my best 19:56:59 sf: think we're closer than last week? 19:57:00 rs: yes 19:57:25 rs: we need a list of issues related to this to submit--e.g. bug 9817 19:57:31 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9817 20:00:27 -Rich 20:00:28 -Cynthia_Shelly 20:00:36 -Michael_Cooper 20:00:38 -Janina 20:00:39 zakim, bye 20:00:39 leaving. As of this point the attendees were Michael_Cooper, Stevef, Rich, Janina, Cynthia_Shelly, [IPcaller] 20:00:39 Zakim has left #aria 20:00:48 rrsagent, make minutes 20:00:48 I have made the request to generate http://www.w3.org/2010/06/15-aria-minutes.html janina 20:01:03 rrsagent, make log public 20:01:09 rrsagent, make minutes 20:01:09 I have made the request to generate http://www.w3.org/2010/06/15-aria-minutes.html janina