16:59:16 RRSAgent has joined #aria 16:59:16 logging to http://www.w3.org/2014/03/31-aria-irc 16:59:18 RRSAgent, make logs member 16:59:18 Zakim has joined #aria 16:59:20 Zakim, this will be WAI_PF 16:59:20 ok, trackbot, I see WAI_PFWG(ARIA)1:00PM already started 16:59:21 Meeting: Protocols and Formats Working Group Teleconference 16:59:21 Date: 31 March 2014 16:59:27 RRSAgent, make log public 16:59:31 chair: Rich 16:59:41 meeting: W3C WAI-PF ARIA Caucus 16:59:42 + +1.415.624.aaaa 16:59:43 janina has joined #aria 16:59:45 + +1.512.445.aabb 17:00:19 bgaraventa1979 has joined #aria 17:00:30 +??P3 17:00:45 zakim, aaaa is Bryan_Garaventa 17:00:45 +Bryan_Garaventa; got it 17:01:10 zakim, I am Bryan_Garaventa 17:01:10 ok, bgaraventa1979, I now associate you with Bryan_Garaventa 17:01:20 jcraig has joined #aria 17:01:21 zakim, who's on the phone? 17:01:21 On the phone I see Rich_Schwerdtfeger, Bryan_Garaventa, +1.512.445.aabb, ??P3 17:01:33 zakim, ??P3 is me 17:01:33 +janina; got it 17:03:00 +??P26 17:03:03 zakim, +aabb is Susann 17:03:03 sorry, janina, I do not recognize a party named '+aabb' 17:03:30 zakim, aabb is Suzanne_Keohane 17:03:30 +Suzanne_Keohane; got it 17:03:52 zakim, Sus is Suzann_Keohane 17:03:52 sorry, MichaelC, I do not recognize a party named 'Sus' 17:03:57 zakim, Sua is Suzann_Keohane 17:03:57 sorry, MichaelC, I do not recognize a party named 'Sua' 17:03:58 mattking has joined #aria 17:04:01 zakim, Suz is Suzann_Keohane 17:04:01 +Suzann_Keohane; got it 17:04:28 zakim, Suz is Susann_Keohane 17:04:28 +Susann_Keohane; got it 17:04:33 clown has joined #aria 17:04:34 + +1.603.882.aacc 17:04:45 +Jon_Gunderson 17:04:59 + +1.541.678.aadd 17:05:02 +[Apple] 17:05:07 zakim, aacc is Mary_Jo_Mueller 17:05:08 +Mary_Jo_Mueller; got it 17:05:12 zakim, aadd is Matt_King 17:05:12 +Matt_King; got it 17:05:18 Zakim, Apple has jcraig 17:05:19 +jcraig; got it 17:05:28 zakim, aacc is me 17:05:29 sorry, joanie, I do not recognize a party named 'aacc' 17:05:37 +[GVoice] 17:05:46 zakim, GVoice is Joseph_Scheuhammer 17:05:46 +Joseph_Scheuhammer; got it 17:05:58 zakim, I am Joseph_Scheuhammer 17:05:58 ok, clown, I now associate you with Joseph_Scheuhammer 17:06:02 + +1.626.841.aaee 17:06:38 This is Dominic Mazzoni - I just joined 17:06:51 + +49.322.110.8.aaff 17:07:43 Stefan has joined #aria 17:07:57 +James_Nurthen 17:08:02 zakim, aaff is Stefan_Schnabel 17:08:02 +Stefan_Schnabel; got it 17:08:08 jamesn has joined #aria 17:08:54 Susann_Keohane has joined #aria 17:09:35 scribe: Susann_Keohane 17:11:18 Topic: UAIG status 17:11:56 richard: documents using ReSpec and put out on github 17:13:19 michael cooper: documents are produce of both. SVG folks will have to join pf working group 17:13:50 george: looking for formal working statement from both groups. Sign off from both groups 17:14:25 george: time to publish. we will need formal approval from both groups like last call will need svg and pf sign off 17:14:30 s/documents are produce of both/A SVG mapping document is products of both SVG and PFWG/ 17:14:50 richard: we are going to have to create semantics for graphics that will show up in svg spec at some point 17:15:20 s/george: /janina: /g 17:15:41 matt: how many modules - svg, uaig, core user AIG, HTML5 17:16:02 richard: not decided how to deal with modules 17:16:31 modules meaning 2 sub efforts - (1) epub structural semantics (2) graphics 17:17:31 matt: modules are not uaig, but modules that are part of actually ARIA specs 17:18:25 matt: 6 modules - core spec, core uaig, module epub structiral semantics, graphics, spec implementations for svg and html5.1 17:19:09 rich: shane is working on the first reSpec 17:20:42 defining what ReSpec and Github is 17:21:35 s//JamesC:/ 17:22:16 http://www.w3.org/respec/ 17:22:26 Mattking^ 17:23:11 george: html accessibility task force charter and it shows two doc as joint doc - HTML mapping guide and using aria in html 17:23:18 JC: Git is a type of distributed version control. GitHub is a series of tools (review, merge, compare) that work on top of Git. 17:23:24 s/george:/janina:/g 17:24:08 janina: might want to rename the doc 17:24:23 JC: ReSpec is a JavaScript-based set of transformation tools that just make it easier to do the monotonous parts of W3C spec editing. 17:24:57 rich: michael to chair the next two ARIA calls 17:25:32 Topic: ARIA 1.1 Meaty issues 17:27:04 DM: web components - elements inside shadow is not accesibility inside from outside 17:27:21 DM: idea is to encapsulate them but there are new tools to jump inside components 17:27:34 s/accesibility inside from outside/accessible from the containing document/ 17:28:11 DM: challenge is what is if you need to refernce something inside from outside like aria labelled by 17:28:17 q+ to discuss the activedescendant example 17:28:27 +q 17:28:54 q? 17:29:14 DM: two options 17:29:20 ack me 17:29:20 jcraig, you wanted to discuss the activedescendant example 17:29:50 james: active descendant - one case where this would be applicable is combobox 17:30:08 james: list box that pops up will be a shadow dom control 17:30:40 james: ask DM for other examples 17:31:11 DM: one case provided may not be necessary for this proposal 17:31:42 s/DM for james 17:32:27 DM: activedescendant there might be an alt case for a combo box. listbox where every option in the list box is it's own 17:32:36 matt: would a grid be a use case 17:32:44 DM: yes it's certainly possible 17:32:47 q? 17:32:53 q+ 17:32:59 q+ 17:32:59 q+ Matt_King 17:33:13 q? 17:33:35 stefan: how does AT access the part. Is there already some ref exist? what can we expect 17:33:46 q- Matt_ 17:34:27 ack Stefan 17:34:28 DM: web componenet spec doesn't specifically ref a11y, but it makes it clear how web component behave. Take all the contents to the html add it to the dom where the custom element is found. that is what is presented to ATs 17:34:51 q+ to describe more details/problems with the shadow DOM model 17:35:05 DM: basic things work as if you added the html right there 17:35:25 stefan: you can hide the code implementation but the screen readers can access it 17:36:04 q? 17:36:16 q- 17:36:17 DM: issues with focusability 17:37:16 DM: this idea of defining alt way to define id ref and could be a good feature outside of web components 17:37:17 Agreed that this feature is not limited to shadow DOM usage 17:38:02 Rich: question - the aria labelled by is inside component but wants to be labelled outside 17:38:42 rich: question expands into the dom 17:38:43 q- 17:38:54 rich: what if you have an a11y that is traversing the dom itself 17:39:16 DM: there are javascript api that let you traverse inside a component 17:39:36 q+ to suggest we talk about this outside the context of shadow DOM. We 17:39:48 ack r 17:39:52 DM: a11y dev tools ext for chrome supports web components and find a11y issues inside components 17:40:15 rich: which browsers besides chrome 17:40:43 q? 17:40:48 DM: mozilla has provided support to the group, they are all at different stages at different browsers 17:41:20 ack mattking 17:41:26 ack mattk 17:41:47 matt: what is the status - what is the context? 17:42:46 http://w3c.github.io/webcomponents/explainer/ ? 17:42:51 DM: web components could be considered a mini iframe 17:43:11 ack me 17:43:11 jcraig, you wanted to suggest we talk about this outside the context of shadow DOM. We 17:43:19 DM: shoudl take the discussion outside of web components to progress conversation 17:43:41 q+ you wanted to suggest we talk about this outside the context of shadow DOM. 17:43:43 matt: shadow dom, it is very diff than iframe that is not a seperate doc 17:43:45 shadow dom: http://w3c.github.io/webcomponents/spec/shadow/index.html 17:43:57 DM: it has its own render tree that is how it is seperate 17:44:35 DM: it does have its own scripts and style sheets 17:44:45 q+ to suggest we talk about this outside the context of shadow DOM. 17:44:58 q+ 17:45:00 matt: a11y req around landmark and regions. If there is a main landmark inside a web component will there be a problem 17:45:23 everything should work as everything was composed into one page 17:45:37 susann: not sure who is speaking right now 17:46:01 ack me 17:46:01 jcraig, you wanted to suggest we talk about this outside the context of shadow DOM. 17:46:40 james: if you were to create a dialog and wanted to label it, you would have to give it a heading and ref it 17:46:50 james: I am labelled by the first heading inside of me 17:47:05 james; i control the first element inside me matching this classname 17:47:18 james: locked into id ref so it's not possible today 17:47:48 james: it would be easier to ref a particular element inside a control 17:47:51 q? 17:47:58 q+ 17:48:08 james: shadow dom is an ex that can't be done currently 17:48:19 james: but it is useful outside the shadow dom 17:48:45 brian: asked a question about ref in mark up 17:49:16 james: open up token parsing and attribute parsing rules to simple selectors 17:49:36 james: javascript based use a ccs selector and pass in ref to a dom element at page render time 17:49:50 ack rich 17:49:54 james: any and all selectors or whats avail in javascript 17:49:54 Q- 17:50:12 ich: query selector, it could be problematic 17:50:42 rich: you could have a mix that has to be parsed 17:50:59 rich:the mix of id and javascript 17:51:12 james: he put in a decent soln to that problem 17:51:34 rich: the idea of a selector is really nice and save code 17:51:52 Dominic proposed on list: aria-foo="myIdRef selector(mySelector) mySecondIdRef" 17:52:06 james: this is what dominic posted on list 17:52:37 james: unique syntax as open parm 17:53:02 james: worried about complex selectors 17:53:13 james: two elements or two class, do we allow 17:53:16 q? 17:53:27 matt: any other specs that use ids in this way or is aria the first 17:53:38 james: html and svg do use it in several places 17:53:58 DM: label for = and table cell can spec headers by id ref 17:54:09 DM: svg is another classic example 17:54:20 matt: is there any other spec that allows id to be selectors 17:54:27 matt: we're breaking new ground 17:54:43 rich: i like the selector indicator and run eval on it 17:55:11 DM: query selector and pass it that string to pass it that element 17:55:50 james: label all would be necessary 17:56:01 james: query selector all picks all 17:56:13 matt: every that has a certain class would make sense 17:56:27 DM: if aria attribute allows for multiple, select all 17:56:48 DM: rare if multiple elelments map and only won't the first one 17:57:16 aria-foo="selector([role=heading])" 17:57:28 DM: aria labelled by that takes multiple ids then call all 17:57:45 matt: the author would have to responsible to make sure you have a unique match 17:57:52 aria-foo="selector(>[role=heading])" (only the first heading?) 17:58:11 q+ 17:58:18 DM: I could go either way. we don't have to specify every permutation 17:58:41 matt: if there is anything implicited like it's all there is agreat possible of confusion 17:58:55 rich: 4 heading would give you list of headings 17:59:15 DM: dont need to solve the issue today on query select 17:59:15 q+ 17:59:21 ack r 17:59:38 rich: logicistic issue who is going to discuss web components group 17:59:47 james: no need to discuss with web components 17:59:55 james: need to discuss in web app and css 18:00:05 james: need a soln before we discuss to each group 18:00:17 rich: who is the person that will go discuss. James could go to web apps 18:00:33 james: is fine with that and is a member of css 18:00:52 james: want to work out all the kinks. Don't see a prob with javascript api 18:01:10 james: there is oddities with putting selectors inside attributes bc there is not precedents 18:01:22 DM: agreed there is alot of details to work out 18:02:21 s/precedents/precedence/ 18:02:49 DM: query selector can defer computation until AT request it 18:03:01 deferred computation is a good reason for the query approach 18:03:03 DM: potential performance win 18:03:27 DM: once when requested inside updated continuously 18:03:43 s/ inside with instead 18:04:03 james: how would you get a reference to self 18:04:23 attr="selector(>[role=heading])" 18:04:28 james: child selector 18:04:40 james: first child heading instead of first heading 18:04:55 DM: document query selector 18:05:21 james: can happen in nested web components 18:05:46 james: even if you added an id to get to self, you will have to ref shadow root with other selector and if multiple things match how would you tell 18:06:18 DM: may need to add syntax for self. Need to think about it some more 18:07:02 rich: what are the issues that we need to discuss? (1) attribute selector (2) nesting of web component (3) concerned about query selector resolve to multiple name 18:07:13 rich: other items? 18:07:34 DM: strong feelings about html only route vs javascript only route 18:07:38 q+ 18:07:44 q/ 18:07:46 q? 18:07:48 DM: does anyone have strong objections to one or other 18:07:54 MichaelC has joined #aria 18:08:14 james: no strong objections but working out kinks 18:08:34 james: this is a shift from typical declarative aria approach 18:08:45 james: there is not other language that use selectors 18:09:36 DM: may won't to choose one to go with first 18:09:48 MichaelC has joined #aria 18:10:05 james: reflective attributes for the rest of stuff 18:10:19 rich: the only thing I worry about is the test tool and how they get at information 18:10:26 rich: they are use to walking the dom 18:10:52 DM: we would have a javascript interface to inspect 18:11:02 rich: how hard to get features into browsers 18:11:12 MichaelC has joined #aria 18:11:21 rich: getting javascript features into browser is always a challenge 18:11:34 rich: understand it will be hard to coordinate 18:11:57 DM: that is why he is open to both ideas. reach out to mozilla as soon as possible 18:12:04 james: alex and david are both on the list 18:12:17 rich: we would have to get this in svg also 18:12:25 rich: if we are going to use the api route 18:12:46 james: element interface instead of html interface and should inherit to svg 18:13:27 rich: specific methods to say get role 18:13:55 james: we have specific aria to use in any language, generic mark up language 18:14:06 james: language has a possible to modify how aria efects it 18:14:23 rich: if you look at the dom form spec, don't have a get role 18:14:36 james: we will put in aria 1.1 our porposed ext to element 18:14:42 james: keep it into aria spec 18:14:55 rich: start earlier rather than later 18:15:10 rich: dont need it to be in dom spec? 18:15:21 james: as long as we extend it in a std way we can keep it in aria spec 18:15:38 james: search html doc for partial interface element and you will see it 18:15:55 s/partial interface element/"partial interface Element"/ 18:15:58 rich: what do we do about css attribute selector that are not in dom 18:16:26 james: one of proposal is the role selector, computed role selector 18:16:30 CSS computed role selector :role() selector 18:16:56 james: proposed this last year. render h1, h2 and any element that was equivalent to able 18:17:05 s/ able / "above" 18:17:14 h1, h2, *[role="heading"] would be equivalent to *:role(heading) 18:17:23 rich: checkbox? 18:17:35 james: you can use attrib selector for it 18:18:22 reflected attrs would be something like this: el.ariaChecked = "true"; results in 18:18:46 james: IE had reflected attib in its first implementation 18:18:55 james: beneficial qualities to it 18:19:05 rich: lets make sure we get this covered 18:19:15 s/IE had reflected /I think IE may have had reflected / 18:19:16 rich: is trying to reduce the amt of javascript 18:19:29 q+ to ask why you are trying to reduce JS usage 18:19:43 rich: trying to get fast and smaller 18:19:43 ack me 18:19:43 jcraig, you wanted to ask why you are trying to reduce JS usage 18:19:44 q? 18:20:00 ack r 18:20:27 rich: adding aria attributes after teh fact and adds performance issues. structures we use for aria we find in uI across the board 18:20:44 rich: we can style the UI using those attrib rather then make modifications to the dom 18:21:04 rich: trying to reduce footprint and make it faster 18:21:38 james: clarify - you had to change the aria properties and classname on element 18:21:54 rich: the viz would change that you set something in the dom 18:22:29 rich: alot of component lib don't make use of css capability because of running in old broswer 18:23:12 rich: css scrollable div didn't exist in IE 6 18:23:24 rich: we are seeing performance gains 18:23:50 rich: add a11y features in begin and use it to drive style reduces the amount of aria code 18:24:09 james: reSpec makes it easier to add new interfeaces 18:24:52 -Stefan_Schnabel 18:25:14 s/reSpec makes it easier to add new interfeaces/ReSpec makes it easier to add new IDL interfaces/ 18:25:26 Topic issue 590 18:25:30 issue-590? 18:25:30 issue-590 -- add caption role -- raised 18:25:30 https://www.w3.org/WAI/PF/Group/track/issues/590 18:25:32 rich: it can be closed 18:25:44 Issue 590 Caption Role: Per our last discussion this should be closed in 18:25:44 favor of aria-labelledby 18:25:45 - https://www.w3.org/WAI/PF/Group/track/issues/590 18:25:47 issue-590? 18:25:47 issue-590 -- add caption role -- raised 18:25:47 https://www.w3.org/WAI/PF/Group/track/issues/590 18:26:07 DM: used for tables and figures 18:26:20 DM: we dont have 1-1 mapping 18:26:38 DM: we got rid of label in aria 1.0 bc we had labelledby 18:27:07 DM: bc we now have this planned interface for computed role, move towards having a 1-1 mapping with any of the semantic html components 18:27:22 DM: may need a generic for the ones we don't have 1-1 mapping 18:27:51 DM: not to close issue but reinstating the label role? 18:28:07 rich: any objecting to introducing the label role? 18:28:40 matt: don't understand what the role=label buys you 18:28:55 DM: benefit is to inspect the dom the javascript interface 18:29:54 DM: computing role should return heading in examples provided 18:30:28 DM: caption has not element role mapping 18:32:39 matt: so what is the advantage? 18:32:47 rich: overtime 18:32:50 rich: take it to the list 18:32:52 -James_Nurthen 18:32:56 IA2_ROLE_PARAGRAPH 18:32:58 rich: response to action item 1398 18:33:03 action-1398? 18:33:03 action-1398 -- Richard Schwerdtfeger to Email list with discussion points for localized custom role names on known role types: role inheritance hierarchy, roadmap towards custom roles outlined, localization implications, potential for subroles etc. -- due 2014-03-24 -- OPEN 18:33:04 https://www.w3.org/WAI/PF/Group/track/actions/1398 18:33:15 rich: take a look at it and discuss over next week 18:33:20 -Jon_Gunderson 18:33:22 -Bryan_Garaventa 18:33:23 -[Apple] 18:33:28 -Matt_King 18:33:30 -Joanie_Diggs 18:33:31 -Joseph_Scheuhammer 18:33:32 Zakim, bye 18:33:32 leaving. As of this point the attendees were Rich_Schwerdtfeger, +1.415.624.aaaa, +1.512.445.aabb, Bryan_Garaventa, janina, Michael_Cooper, Suzanne_Keohane, Suzann_Keohane, 18:33:32 Zakim has left #aria 18:33:35 ... Susann_Keohane, +1.603.882.aacc, Jon_Gunderson, +1.541.678.aadd, Mary_Jo_Mueller, Matt_King, jcraig, Joseph_Scheuhammer, +1.626.841.aaee, Joanie_Diggs, +49.322.110.8.aaff, 18:33:35 ... James_Nurthen, Stefan_Schnabel 18:33:50 rrs agent, make minutes 18:34:00 rrsagent, make minutes 18:34:00 I have made the request to generate http://www.w3.org/2014/03/31-aria-minutes.html Susann_Keohane 18:34:02 rich, don't forget to reference your email to the list in action-1398 18:34:13 rrsagent, make log public 18:35:28 "W3C WAI Protocols & Formats" , 19:17:01 jgunder has joined #aria 19:40:59 clown has joined #aria 20:04:02 jcraig has joined #aria 20:33:50 jcraig has joined #aria 20:47:12 clown has left #aria