17:00:56 RRSAgent has joined #aria 17:00:56 logging to http://www.w3.org/2014/06/30-aria-irc 17:00:58 RRSAgent, make logs member 17:00:58 Zakim has joined #aria 17:01:00 Zakim, this will be WAI_PF 17:01:00 ok, trackbot, I see WAI_PFWG(ARIA)1:00PM already started 17:01:01 Meeting: Protocols and Formats Working Group Teleconference 17:01:01 Date: 30 June 2014 17:01:04 jongund has joined #aria 17:01:05 RRSAgent, make log public 17:01:09 chair: Rich 17:01:19 +??P3 17:01:20 meeting: W3C WAI-PF ARIA Caucus 17:01:25 zakim, ??P3 is me 17:01:25 +janina; got it 17:01:40 +Rich_Schwerdtfeger 17:01:49 agenda: http://lists.w3.org/Archives/Public/public-pfwg/2014Jun/0139.html 17:02:08 +Jon_Gunderson 17:03:19 + +1.603.882.aabb 17:03:28 +??P10 17:03:41 Zakim, aabb is me 17:03:41 +joanie; got it 17:03:50 Birkir has joined #aria 17:05:02 Birkir Gunnarsson the the secret 919 code 17:05:11 zakim, aaaa is Birkir_Gunnarsson 17:05:11 +Birkir_Gunnarsson; got it 17:05:13 Raleigh, North Carolina! 17:05:21 zakim, Microsoft is Chris_Gallello 17:05:21 +Chris_Gallello; got it 17:05:40 Zakim, joanie is Joanmarie_Diggs 17:05:40 +Joanmarie_Diggs; got it 17:06:08 like the Life Aquatic discussions, great movie too ;) 17:07:07 Next time, I prommise, not quite set up this time. 17:07:25 I promise not to scribe in Icelandic .. and next time will be next Monday, promise 17:08:15 scribe: jongund 17:08:29 RS: Intro to the specs 17:09:04 JS: We will publish heart beats in we want to be updating intro, we need the newer thinking 17:09:21 jamesn has joined #aria 17:09:34 JS: Please look at the intro, looking for volunteers to look at the intros 17:09:44 RS: I have to do it for SVG 17:10:03 RS: Things have chnaged form when we started ARIA 17:10:37 RS: I am willing to take a stab for ARIA spec and Core and I will be doing it for SVG 17:10:52 RS: I will not being doing it for HTML5 17:11:26 MC: We will have several fingers in that pot, but if rich can do a first pass that will be a big help 17:11:40 RS: Are there specific points you want in the intros 17:12:00 + +1.415.624.aacc 17:12:26 action: schwerdtferger to draft introductions for ARIA 1.1, Core-AAM 1.1, and SVG-AAM 1.1 17:12:27 Error finding 'schwerdtferger'. You can review and register nicknames at . 17:12:30 MC: I have a few things, write from the perspective of someone who is not familiar with the technology or the problem, help people understand the problem and solution 17:12:31 bgaraventa1979 has joined #aria 17:12:43 RS: We are looking at application wide changes 17:12:50 #aria is associated with #pf. 17:12:52 #aria is associated with #pf. 17:13:04 action: RS to draft introductions for ARIA 1.1, Core-AAM 1.1, and SVG-AAM 1.1 17:13:04 Created ACTION-1470 - Draft introductions for aria 1.1, core-aam 1.1, and svg-aam 1.1 [on Richard Schwerdtfeger - due 2014-07-07]. 17:13:09 zakim, aaaa is Bryan_Garaventa 17:13:09 sorry, bgaraventa1979, I do not recognize a party named 'aaaa' 17:13:17 RS: We are trying to harmonize the integration of accessibility around graphics and HTML5 17:13:31 RS: ARIA 2.0 is way off in the future 17:13:31 zakim, I am Bryan_Garaventa 17:13:31 sorry, bgaraventa1979, I do not see a party named 'Bryan_Garaventa' 17:13:41 zakim, aacc is Bryan_Garanventa 17:13:41 +Bryan_Garanventa; got it 17:13:47 RS: Addressing things that we were not able to address in 1.0 17:13:50 zakim, Bryan is Bryan_Garaventa 17:13:50 +Bryan_Garaventa; got it 17:13:58 RS: We are trying to fix all these particular issue 17:14:05 +James_Nurthen 17:15:01 +Cynthia_Shelly 17:15:05 JS: We need a requirements document, issues that we are working on, when we are done we point to a problem statement ... 17:15:15 JS: looking for some to help with that 17:15:21 -Cynthia_Shelly 17:15:39 JS: Did I miss anything 17:15:51 +Cynthia_Shelly 17:16:02 MC: Two important roles we want to consider, how does the spec meet its requirement 17:16:35 MC: JG: I would be willing to help with that 17:17:03 action: jon to start list of requirements for ARIA 1.1 17:17:03 Created ACTION-1471 - Start list of requirements for aria 1.1 [on Jon Gunderson - due 2014-07-07]. 17:17:46 MC: A single requirements document or separate documents for each spec, need to make a conscious decision 17:18:00 JS: JRG think about that and give a recommendation 17:18:25 JS: When do we want to publish a new heart beat, we need to get ahead of TPAC, early october 17:18:47 RS: About 3 months, about every quarter 17:18:53 RS: any objections? 17:19:19 MC: We need to keep that in our minds... 17:19:40 JS: We need to test early, when we want to do that 17:20:20 RS: To that point, I would like to get some feedback, for role="none" I have been filing bugs 17:20:52 CS: I would prefer something other than a wiki 17:21:09 JS: Concerned about about maintanence 17:21:17 CS: Bugzilla 17:21:28 RS: Bugzilla for all the other bugzilla 17:21:33 assign someone to file issues against browsers/assistive technologies (or to oversee such a process)? 17:21:50 CS: A bug for each browser and linked ... 17:21:57 RS: Do you want to do it? 17:22:11 CS: When do we want to start testing? 17:22:21 RS: We want to get the defects in the browser 17:22:37 CS: Let me talk to IE team on what would help them 17:23:05 RS: You can talk to mozilla on the list, JC is out for 3 weeks 17:23:22 CS: I can talk to IE team and ping david 17:23:37 + +1.541.678.aadd 17:24:23 RS: I can't do anymore right now 17:25:09 mattking has joined #aria 17:25:16 JG: I have some people who can help with testing 17:25:51 MC: It sounds like we have some people to create test cases 17:26:11 zakim, aadd is Matt_King 17:26:11 +Matt_King; got it 17:26:17 RS: FOr role=presentation, we can do role="none" 17:26:25 JS: That is an east 17:26:45 MC: test harness copy some stuff over... 17:28:37 JG: Question about nested tables and role=presentation 17:28:55 RS: Can JRG create test cases 17:29:05 If they are accessible, I would be happy to help out with test case writing. 17:29:08 JG: We can try it 17:29:14 I am new to this process. 17:29:28 action: cooper to work with Jon Gunderson and his team on creating test cases for for ARIA 1.1 17:29:29 Created ACTION-1472 - Work with jon gunderson and his team on creating test cases for for aria 1.1 [on Michael Cooper - due 2014-07-07]. 17:30:06 action: cynthia to prepare recommendation on automation of tracking of bugs filed with various implementers 17:30:06 Created ACTION-1473 - Prepare recommendation on automation of tracking of bugs filed with various implementers [on Cynthia Shelly - due 2014-07-07]. 17:30:37 RS: Anything else JS? 17:30:45 RS: Issue 658 17:30:51 RS: This is clean up 17:31:05 RS: Annotation role....., MS proposal for annotation 17:31:33 RS: We have already done this, can we close, any objections? 17:31:47 RS: Resolution to close 568 17:32:27 RS: Is Joespeh S on today? 17:32:33 ack me 17:32:46 RS: Lets hold off until the next weekend 17:32:55 RS: Issue 493 17:32:59 https://www.w3.org/WAI/PF/Group/track/issues/493 17:33:21 ack me 17:33:54 RS: Why is closed 17:34:23 MC: I am not sure this working, JC closes the issue when an action is created to resolve the issue 17:34:33 RS: Issue 522 17:34:45 RS: This is from JN 17:34:59 issue-522? 17:34:59 issue-522 -- Name Computation 2A - bullet 3 confusion -- open 17:34:59 https://www.w3.org/WAI/PF/Group/track/issues/522 17:35:17 RS: Is aria-labelledby and aria-label .... not marked as presentational.... 17:36:54 JN; This is how other people are reading it, people are not getting the child elements for role="presentation" 17:36:58 zakim, mute birkir 17:36:58 Birkir_Gunnarsson should now be muted 17:38:08 JN: If something is marked presentational it should be used in accessible name calc 17:38:37 CS: Firefox gets the name from going through the accessible tree, not the DOM 17:39:14 JN: The name calculation says what should be done, and the presentation should not block the name calculation 17:39:26 CS: it seems the description is unclear 17:40:11 MK: They decided to put all the content of a table into one element, so a screen reader is treating the table as a paragraph 17:40:31 MK: this is a miss understanding on how to implement role presentation 17:41:02 CS: Should this be part of the implementation guide, maybe a flow chart or several examples 17:41:06 http://www.w3.org/TR/wai-aria/roles#textalternativecomputation 17:42:00 JN: There is not the same understanding even with people whoa re members of this group 17:42:30 RS: Let's say we have a label on something, and the button is marked presentational, the name has to be applied to what.. 17:42:54 +q 17:43:15 JN: creating a an example ..... 17:43:17 q? 17:43:19
some text
17:44:36 MK: that is one thing that is not clear, we need to give something a role ... 17:44:45 CS: DIV has a role of group 17:44:53 MK: It does not 17:45:05 CS: It does on every browser 17:45:15 CS: Every windows browser 17:45:21 RS: I am sure that is not the case 17:45:33 MK: I thin your right rich 17:46:27 MK: If is suppose to be something other than what it was, .... the content still has to be there, and the that content should have a role, even though it is different 17:46:39 RS: The text content is there, but there is no role 17:47:00 RS: In SVG there is a lot of things that will have role="none" 17:47:26 in FF it seems to be role of section 17:47:41 RS: There are different roles for DIV in various browsers and OSs 17:47:54 RS: the text has a node 17:48:11 RS: Text in the browser has role of readonly text 17:48:23 MK: We do not say that specfically 17:48:37 RS: We don't have a role a mapping for text 17:48:49 MK: We don't have a role mapping for role=presentation 17:49:07 RS: Paragraph has roles of .... 17:49:15 CS: What are the roles for span 17:49:24 MK: It is interesting though .... 17:49:35 span is closest as spans can have child elements..... 17:49:45 RS: span has a number of different roles depending on OS and browser 17:50:09 ugh... 17:50:34 MK: we have a defect in FF they put all the text of a layout table as a single line 17:51:30 MK: For a able to be readable needs to have some type of separator for text in the different cells 17:51:45 MK: giving an example ..... 17:52:00 CS: that is a data table it should not be a layout table 17:52:15 CS: You could make that a data table, another example..... 17:53:04 MK: In practice it does't work very well, we need a more paragraph model 17:53:30 CS: You have images, text ...., really should be absolutelely positioned... 17:53:48 If they are accessible, I would be happy to help out with test case writing.Divs would do the trick with a presentational table, they are blocklevel elements, spans make tables with role="presentation" near unreadable, that is true 17:53:52 MK: If they are spaced differently, the screen reader needs to know about the spacing too 17:54:30 q? 17:54:44 MK: That's why the role of whats left matters 17:54:47 ack bgaraventa 17:55:16 RS: Button doesn't have any semantic children 17:55:32 RS: The button objects goes away and you just have text 17:56:03 RS: On the table all the children go away.... 17:56:15 RS: That makes sense too 17:56:32 MK: We did have a separate issue of buttons have popup menus 17:56:56 RS: Look at this as semantic sugar, when you take it away you just have content 17:57:40 JN: I reported it, brian was interpreting different from me 17:58:06 JN: Reading a e-mail response.... 17:58:30 Brian: I know which one your talking about now.. 17:59:07 JN: I requesting a clarification so people reading it for the first time have a better understanding it 17:59:27 JN: There is confusion even among current working group memebers 17:59:43 RS: Which aspect of the text could help with clarification 17:59:43 If aria-labelledby and aria-label are both empty or undefined, and if the element is not marked as presentational (role="presentation"), check for the presence of an equivalent host language attribute or element for associating a label, and use those mechanisms to determine a text alternative. For example, in HTML, the img element's alt attribute defines a label string and the label element references the form element it labels. See How to Specify 17:59:44 Alternate Text ([HTML], section 13.8) and HTML 5 Requirements for providing text to act as an alternative for images ([HTML5], section 4.8.1.1). 18:00:00 JN: We understand it now, so it is hard for us to identify the problem 18:00:30 JN: Maybe we say that the child text content does not go away and is still part of the accessibility API 18:01:25 MK: Can we simplify role=presentation now has a role=text or something else (e.g. equivalent), would that help 18:01:55 RS: We spent a lot of time writing this, reading through spec text.... 18:03:36 RS: Do people understand the text? 18:03:56 Brian: Developers don't understand the difference between the accessibility tree and the DOM 18:04:20 RS: The mis match between the DOM and accessibility tree 18:04:56 MK: There is more than that, must "expose" content, we don't say how that should be done 18:06:02 CS: The bulleted list is not the best to way to explain algorithm, pauedo code or input/output 18:06:13 CS: maybe some examples from good test cases 18:07:02 CS: There is too much open to interpretation 18:07:33 RS: So we can't put an exhaustive list in the spec, do we need to show an example 18:08:02 RS: One where you have a single table and show the new tree 18:08:19 RS: Nested data table in a layout table 18:08:29 RS: button with role presentation 18:08:57 RS: Do these sound like the three scenarios we need 18:09:13 JN: I am not going to comment until i see the new description 18:09:30 JN: We need get some new people to look at it 18:09:57 RS: is putting it in the role presentation for .. 18:10:08 JN: We need them in both places 18:10:13 ack me 18:10:18 CS: Even implementators 18:10:30 RS: I am worried about the spec getting to big 18:10:40 MC: We use supporting documents 18:11:42 RS: I am looking at bullet 3 again, this was difficult approach 18:11:50 aria accessible name calculation is also tricky in that the spec does not exclusively state if user agents should stop when they find an accessible name, or continue down the list. 18:11:52 CS: Give me an action 18:11:57 think a button with an aria-label and a title. 18:12:17 RS: Can you work on this with Joesph, because he wrote this section 18:12:31 CS: We can do it during the implementation call 18:12:39 CS: It is really important 18:13:39 Action: Cynthia Work with Joseph S. and David B. to rewrite text alternative computation for both the ARIA spec. and the Core Accessibility API mappings specification. 18:13:40 Created ACTION-1474 - Work with joseph s. and david b. to rewrite text alternative computation for both the aria spec. and the core accessibility api mappings specification. [on Cynthia Shelly - due 2014-07-07]. 18:14:18 MK: I now understand why we have problems in the browser, IE column, exposes role system ..., see general rules 18:14:25 RS: Who did that? 18:14:44 MK: That's what is says to do ... 18:15:05 CS: Part of the over all parent, a string within the windows 18:15:28 MK: Expose the content, means to put it in the tree 18:15:46 RS: We want to say the semantics goes away... 18:16:12 MK: If is is going to be in the tree, even plain text has some kind of role 18:16:31 MK: We want to make sure there is a sensible mapping, which we do not have 18:16:52 RS: Do you want put the examples in the spec, but the spec gets bigger 18:17:08 JN: the authoring practices can have more extensive examples 18:17:19 JN: Authors need to know what is going to happen 18:17:27 MK: I agree with you JN 18:17:41 CS: An input and output table is crucial... 18:17:54 MK: We need to train authors on how to use it properly 18:18:22 http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html 18:19:38 RS: Do you want to create that? 18:19:50 CS: I would like to have a collaborator 18:19:56 ack me 18:20:26 CS: What kind of drawing,I need to translate the thought into a picture 18:20:33 MC: I would like to help 18:20:47 CS: This would be good at the FTF meeting 18:22:02 RS: Creating action item... 18:22:10 Action: Cynthia work with Michael C. and Joseph S. to create up to 4 Accessibility diagrams showing the application (before and after) of applying role=“presentation”/none 18:22:10 Created ACTION-1475 - Work with michael c. and joseph s. to create up to 4 accessibility diagrams showing the application (before and after) of applying role=“presentation”/none [on Cynthia Shelly - due 2014-07-07]. 18:23:02 trackbot, associate action-1475 with issue-522 18:23:02 action-1475 (Work with michael c. and joseph s. to create up to 4 accessibility diagrams showing the application (before and after) of applying role=“presentation”/none) associated with issue-522. 18:23:18 trackbot, associate action-1474 with issue-522 18:23:18 action-1474 (Work with joseph s. and david b. to rewrite text alternative computation for both the aria spec. and the core accessibility api mappings specification.) associated with issue-522. 18:23:51 RS: We have 7 minutes left 18:24:41 http://www.w3.org/TR/wai-aria/roles#directory 18:25:25 RS: Any objects, content from the name from? 18:26:40 MK: Don't name from content 18:26:52 JN: What name from content, all the content 18:27:23 JN: For a table, it will be its contents, unless there is another label 18:27:35 MK: Table needs a caption .... 18:27:40 JN: Your right 18:27:55 RS: Any object, the contents value for directory? 18:28:14 MK: Do you delete that role in the table... 18:28:29 RS: I would be just the author, not from contents 18:28:37 RS: Action to editor 18:28:55 Action: jcraig remove contents from the list of Name From values for role “directory” 18:28:55 Created ACTION-1476 - Remove contents from the list of name from values for role “directory” [on James Craig - due 2014-07-07]. 18:29:31 JN: Role=row takes name form contents 18:29:43 RS: Like an e-mail program 18:29:56 trackbot, associate action-1476 with issue-643 18:29:56 action-1476 (Remove contents from the list of name from values for role “directory”) associated with issue-643. 18:29:58 JN: Contents might be the right thing... 18:30:25 MK: If it shouldn't have a name it should only have a value 18:30:33 RS: Might break a product 18:30:43 RS: We can take it off line 18:30:58 rrsagent draft, minutes 18:31:13 rrsagent, draft minutes 18:31:13 I have made the request to generate http://www.w3.org/2014/06/30-aria-minutes.html jongund 18:31:31 NK: document is name form author only... 18:31:36 -Michael_Cooper 18:31:44 RESOLUTION: ISSUE 643 closed with action 1476 18:31:48 MK: Grid is from author only 18:32:03 RS: We are over time 18:32:45 -Birkir_Gunnarsson 18:32:55 -Jon_Gunderson 18:32:59 -Joanmarie_Diggs 18:33:00 -James_Nurthen 18:33:00 -Chris_Gallello 18:33:02 -Matt_King 18:33:02 -Bryan_Garaventa 18:33:03 -Cynthia_Shelly 18:45:27 -Rich_Schwerdtfeger 18:45:28 -janina 18:45:28 WAI_PFWG(ARIA)1:00PM has ended 18:45:28 Attendees were +1.919.607.aaaa, janina, Rich_Schwerdtfeger, Jon_Gunderson, +1.603.882.aabb, Michael_Cooper, Birkir_Gunnarsson, Chris_Gallello, Joanmarie_Diggs, +1.415.624.aacc, 18:45:28 ... Bryan_Garanventa, Bryan_Garaventa, James_Nurthen, Cynthia_Shelly, +1.541.678.aadd, Matt_King 19:00:50 janina has changed the topic to: ARIA Weekly Teleconference; Monday 7 July at 17:00Z for 90 minutes; Zakim 92473# 20:37:22 Zakim has left #aria 22:20:23 Birkir has joined #aria