... 14:19:08 clown: We made it a note to avoid numerous test cases, primarily from HTML. 14:19:25 clown: On the other hand, we thought this useful info 14:21:02 jc: Don't mind making this a note in the 1.1 spec 14:21:19 mc: But, we can't intro changes in 1.0 14:22:14 +[SAP] 14:22:51 Stefan has joined #pf 14:23:00 action-1136? 14:23:00 action-1136 -- Joseph Scheuhammer to Ask the PFWG on the Mon call, what issue-486 is all about. -- due 2012-12-20 -- CLOSED 14:23:00 https://www.w3.org/WAI/PF/Group/track/actions/1136 14:23:15 "a reference to HTML5's section on @alt in the name calculation spec, with an editorial note to remove this reference (?)" 14:24:09 action-1142? 14:24:09 action-1142 -- Joseph Scheuhammer to Remove reference to HTML5 @alt section in the UAIG name calculation section. -- due 2013-02-01 -- CLOSED 14:24:09 https://www.w3.org/WAI/PF/Group/track/actions/1142 14:24:51 mc: Will work on sorting this out 14:26:54 clown: So agreement that there would be an informative note both in UAIG and the spec. So far, it's only showing up in the UAIG. 14:27:51 jc: Suggest pulling into a separate file if changing the src 14:28:49 mc: Notes this a formatting issue, it's not an RFC note 14:29:20 mc: UAIG has added content, though 14:29:47 clown: Hmmm. 14:30:29 mc: OK, let's go on for now ... 14:30:56 clown: We will process in UAIG call, but are doing open actions first 14:31:18 mc: Let's look at issues, but be selective for things relevant to 2nd LC 14:31:38 issue-564? 14:31:38 issue-564 -- ROLE_SYSTEM_TEXT is not used role="heading" -- open 14:31:38 https://www.w3.org/WAI/PF/Group/track/issues/564 14:32:38 clown: Waiting on report from DB re what's ok with AT vendors 14:33:50 mc: moving on ... looking at things we can profitably discuss here 14:33:57 close issue-566 14:33:57 Closed issue-566. 14:34:23 issue-570? 14:34:23 issue-570 -- Investigate if this UAIG requirement is incompatible with AX API. #keyboard-focus_aria-activedescendant "Do not expose the focused state in the accessibility API for any element when it has DOM focus and also has aria-activedescendant which points to a va -- open 14:34:24 https://www.w3.org/WAI/PF/Group/track/issues/570 14:36:04 http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_nd_te 14:36:18 http://www.w3.org/WAI/PF/aria-implementation/#keyboard-focus_aria-activedescendant 14:38:04 jc: Word "focus" only means "keyboard focus" for us. 14:38:13 Stefan has joined #pf 14:39:10 mc: Should we add a conditional statement? RE platforms that ... 14:40:35 ACTION: Joseph to prefix bullet 2 of #keyboard-focus_aria-activedescendant with "For platforms that expose an accessibility focus separately from the keyboard focus," 14:40:36 Created ACTION-1269 - Prefix bullet 2 of #keyboard-focus_aria-activedescendant with "for platforms that expose an accessibility focus separately from the keyboard focus," [on Joseph Scheuhammer - due 2013-10-07]. 14:40:39 [group checking that conditional doesn't affect IE] 14:42:37 clown: Let's come back to 582 when Rich is here 14:43:48 jc: Important issue re AxAPI ... whenever I run test, expected results are relevant to MSAA, not AxAPI 14:44:14 jc: Tool isn't bringing up the correct expectation 14:44:19 mc: But the test is OK? 14:44:21 jc: yes 14:46:48 clown: Noting we need ID and role 14:46:55 clown: Alex confirms this is sufficient 14:47:04 mc: So should be closed if Rich is OK with this answer 14:47:58 issue-583? 14:47:58 issue-583 -- Elements that are descendants of an element having aria-activedescendant should not all be focusable -- open 14:47:58 https://www.w3.org/WAI/PF/Group/track/issues/583 14:48:10 clown: AT-SPI test on this passed -- don't recall exactly which 14:48:57 issue-584? 14:48:57 issue-584 -- Firefox has introduce a role mapping of grouping for rowgroup (should this be consistent across platforms) -- open 14:48:57 https://www.w3.org/WAI/PF/Group/track/issues/584 14:49:38 issue-585? 14:49:38 issue-585 -- What to do with role=rowgroup? -- open 14:49:38 https://www.w3.org/WAI/PF/Group/track/issues/585 14:49:50 mc: And #585? 14:49:55 clown: Seems similar 14:50:00 mc: yes 14:51:02 mc: Is this something that can be put off to 1.1? 14:51:10 clown: That's the question. 14:51:20 clown: believe FF wants left as is 14:51:25 mc: Can we pass test cases? 14:51:30 clown: Don't know 14:51:42 mc: Need a reason to not put this off ... 14:52:06 clown: FF wanted this changed 14:52:22 clown: Q is what IE does 14:52:38 mc: Next 586 ... 14:52:41 issue-586? 14:52:41 issue-586 -- role option cannot be a child of menu in Mac Role mapping -- open 14:52:41 https://www.w3.org/WAI/PF/Group/track/issues/586 14:53:39 http://www.w3.org/WAI/PF/aria-implementation/#mapping_role_table 14:54:23 clown: Is AxAPI text correct? 14:56:56 clown: Sounds like jc ok with removing ... 14:57:02 jc: Also text about listbox 14:57:56 ACTION: Joseph to switch AX API "option" expectation back to AXStaticText… … 'text'… 14:57:57 Created ACTION-1270 - Switch ax api "option" expectation back to axstatictext… … 'text'… [on Joseph Scheuhammer - due 2013-10-07]. 15:00:06 close issue-586 15:00:06 Closed issue-586. 15:00:47 clown: Should be done by Tuesday, also 598, on Cyns 15:00:51 mc: 600? 15:01:04 clown: Want Rich to explain 15:01:08 mc 612 15:01:29 clown: under discussion with db 15:01:32 mc 616 15:01:43 issue-616? 15:01:43 issue-616 -- ISSUE: Review potentially at-risk statement "When the user triggers an element with a defined activation behavior in a manner other than clicking it, such as by pressing Enter, simulate a click on the element." -- open 15:01:44 https://www.w3.org/WAI/PF/Group/track/issues/616 15:01:45 jc: major blocker for Apple, maybe other ua's as well 15:01:58 clown: Interesting, 15:02:08 clown: Cyns says it doesn't work on IE, but should 15:02:19 jc: Believe that's a hard sell 15:04:39 "When the user triggers an element with a defined activation behavior in a manner other than clicking it, such as by pressing Enter, simulate a click on the element." 15:07:01

… 15:07:06 jc: expects ua's to change default behavior, and at risk as not supported (except Opera) 15:07:40 s/expects ua's/ISSUE-616 expects UA's/ 15:07:42 clown: Guess need clarification from Cyns on what is meant 15:07:59 clown: Sometimes actions can be associated 15:08:21 mc: Seems strays into dom activate that remains unfinished 15:09:28 mc: 3 more issues -- 15:09:35 mc 591 15:10:13 jc: Noting that click now means activate in dom spec 15:10:50 jc: Should trigger click on relevant keypress, i.e. return or spacebar 15:11:00 jc: need edit to dom4 15:11:58 https://www.w3.org/WAI/PF/Group/track/issues/616 15:12:17 s/return or spacebar/return or spacebar, if element is focused and has 'click' handler registered/ 15:13:07 mc: remaining issue s need to go to UAIG call ... 15:13:10 topic: Test Plannina 15:13:21 http://www.w3.org/WAI/PF/wiki/ARIA/UAIG_Tests 15:13:26 s/Test Plannina/Test Planning/ 15:14:06 jg: Doesn't seem correct, so am checking 15:14:15 mc: I'll go through and look 15:14:22 http://www.w3.org/WAI/PF/wiki/ARIA/Tests/Testable_Statements#User_Agent_Implementation_Guide_Testable_Statements 15:15:18 action-1258: see http://www.w3.org/WAI/PF/wiki/ARIA/Tests/Testable_Statements#User_Agent_Implementation_Guide_Testable_Statements 15:15:18 Notes added to action-1258 Write some uaig test cases and expected results starting with test case 102 and working backward. 15:16:00 mc: We need testable statements written wherever @@ is present 15:16:37 mc: Look where ref is to UAIG 15:17:36 mc: Noting testing in process, majority of these we have defined we have passes 15:18:12 mc: Anything to discuss re "uncertain" status denotation? 15:18:42 jc: 85-87 need test file updates -- not changing changes via script 15:18:52 jc: Assertion is valid, but file needs update 15:19:09 mc: You could do those ... 15:19:33 jc: Some I'm waiting on Issue 616 15:20:01 jc: #37 doesn't apply to AxAPI focus pointer 15:20:42 janina: If not applicable, not a pass because we're testing implementability 15:22:48 mc: Seems test files are pretty much complete 15:23:00 mc: So JG's part here particularly important 15:23:02 jg: OK 15:23:21 mc: So how much testing do we need to complete before we go LC? 15:23:52 mc: Anything likely from testing that might change UAIG? 15:24:00 clown: Some parts re IE 15:24:44 mc: So invalidate test? Or just expected results? 15:25:01 s/AxAPI/AX API/ 15:25:20 clown: I've made numerous UAIG changes. Have these been reflected in tests? 15:25:23 mc: Probably not 15:25:33 clown: So important 15:25:33 s/#37 doesn't apply/#37 and #38 don't apply/ 15:25:44 mc: There's metadata to corss ref 15:25:56 s/corss/cross/ 15:26:28 #69 and #71 waiting on ISSUE-612 15:26:55 s/Some I'm waiting on Issue 616/#31 and #32 I'm waiting on ISSUE-616/ 15:27:22 action: cooper to look at diff of UAIG in past 1.5 years and figure out which changes might impact the test suite, then to work with Joseph on updating tests 15:27:22 Created ACTION-1271 - Look at diff of uaig in past 1.5 years and figure out which changes might impact the test suite, then to work with joseph on updating tests [on Michael Cooper - due 2013-10-07]. 15:27:51 action-1271: there are commit logs that might have good pointers 15:27:51 Notes added to action-1271 Look at diff of uaig in past 1.5 years and figure out which changes might impact the test suite, then to work with joseph on updating tests. 15:28:34 -James_Craig 15:28:38 jcraig has left #pf 15:34:46 https://www.w3.org/WAI/PF/testharness/test?testsuite_id=2&testcase_id=22&platform_id=4 15:38:54 -Jon_Gunderson 15:43:20 -Michael_Cooper 15:44:10 -[SAP] 15:44:46 -janina 15:44:48 -Joseph_Scheuhammer 15:44:48 WAI_PFWG(ARIA)10:00AM has ended 15:44:48 Attendees were Jon_Gunderson, Joseph_Scheuhammer, janina, Michael_Cooper, James_Craig, [SAP] 15:44:52 zakim, bye 15:44:52 Zakim has left #pf 15:44:55 rrsagent, make minutes 15:44:55 I have made the request to generate http://www.w3.org/2013/09/30-pf-minutes.html janina 15:48:38 make log public 15:57:30 rrsagent, make log public 15:57:37 rrsagent, make minutes 15:57:37 I have made the request to generate http://www.w3.org/2013/09/30-pf-minutes.html MichaelC 16:02:42 clown has joined #pf