- From: Janina Sajka <janina@rednote.net>
- Date: Tue, 1 Oct 2013 15:09:12 -0400
- To: W3C WAI Protocols & Formats <public-pfwg@w3.org>
Trying again with apologies to all for the naked email earlier today ...
Minutes from the ARIA teleconference of 30 September are provided below as text, and are available as hypertext at:
https://www.w3.org/2013/09/30-pf-minutes.html
W3C
- DRAFT -
Protocols and Formats Working Group Teleconference
30 Sep 2013
Agenda
See also: IRC log
Attendees
Present
Jon_Gunderson, Joseph_Scheuhammer, janina, Michael_Cooper, James_Craig, [SAP]
Regrets
Rich_Schwerdtfeger
Chair
Michael_Cooper
Scribe
janina
Contents
* Topics
1. ARIA 1.0 UAIG Issues List
2. ARIA 1.0 Issues re UAIG
3. Test Planning
* Summary of Action Items
_________________________________________________________________________________________________________________________________________________________________
<trackbot> Date: 30 September 2013
trackbot, start meeting
<trackbot> Meeting: Protocols and Formats Working Group Teleconference
<trackbot> Date: 30 September 2013
<jongund> be back in a minute
ARIA 1.0 UAIG Issues List
<MichaelC> https://www.w3.org/WAI/PF/Group/track/products/10
<scribe> scribe: janina
ARIA 1.0 Issues re UAIG
<clown> issue-486?
<trackbot> issue-486 -- UAIG has some MUST requirements that could only be tested in HTML 5, but 1) the ARIA spec is being tested only against HTML 4 and we prefer to
do the same with UAIG, and 2) HTML 5 isn't complete; so we need to deal with this in the UAIG CR exit criteria n -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/486
<clown> http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_nd
clown: In UAIG it's a note, by intent
jc: Not using the same file for the compute?
mc: Thought so
<clown> "See How to Specify 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)."
clown: In the spec, this is Step 2a, but a note in UAIG
<MichaelC> http://www.w3.org/WAI/PF/aria-1.1/roles#namecalculation
jc: Perhaps should check UAIG src file
<clown> <p class="note">...
clown: We made it a note to avoid numerous test cases, primarily from HTML.
... On the other hand, we thought this useful info
jc: Don't mind making this a note in the 1.1 spec
mc: But, we can't intro changes in 1.0
<clown> action-1136?
<trackbot> action-1136 -- Joseph Scheuhammer to Ask the PFWG on the Mon call, what issue-486 is all about. -- due 2012-12-20 -- CLOSED
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1136
<clown> "a reference to HTML5's section on @alt in the name calculation spec, with an editorial note to remove this reference (?)"
<clown> action-1142?
<trackbot> action-1142 -- Joseph Scheuhammer to Remove reference to HTML5 @alt section in the UAIG name calculation section. -- due 2013-02-01 -- CLOSED
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1142
mc: Will work on sorting this out
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.
jc: Suggest pulling into a separate file if changing the src
mc: Notes this a formatting issue, it's not an RFC note
... UAIG has added content, though
clown: Hmmm.
mc: OK, let's go on for now ...
clown: We will process in UAIG call, but are doing open actions first
mc: Let's look at issues, but be selective for things relevant to 2nd LC
<MichaelC> issue-564?
<trackbot> issue-564 -- ROLE_SYSTEM_TEXT is not used role="heading" -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/564
clown: Waiting on report from DB re what's ok with AT vendors
mc: moving on ... looking at things we can profitably discuss here
<MichaelC> close issue-566
<trackbot> Closed issue-566.
<MichaelC> issue-570?
<trackbot> 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
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/570
<clown> http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_nd_te
<clown> http://www.w3.org/WAI/PF/aria-implementation/#keyboard-focus_aria-activedescendant
jc: Word "focus" only means "keyboard focus" for us.
mc: Should we add a conditional statement? RE platforms that ...
<jcraig> ACTION: Joseph to prefix bullet 2 of #keyboard-focus_aria-activedescendant with "For platforms that expose an accessibility focus separately from the
keyboard focus," [recorded in http://www.w3.org/2013/09/30-pf-minutes.html#action01]
<trackbot> 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].
[group checking that conditional doesn't affect IE]
clown: Let's come back to 582 when Rich is here
jc: Important issue re AxAPI ... whenever I run test, expected results are relevant to MSAA, not AxAPI
... Tool isn't bringing up the correct expectation
mc: But the test is OK?
jc: yes
clown: Noting we need ID and role
... Alex confirms this is sufficient
mc: So should be closed if Rich is OK with this answer
<MichaelC> issue-583?
<trackbot> issue-583 -- Elements that are descendants of an element having aria-activedescendant should not all be focusable -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/583
clown: AT-SPI test on this passed -- don't recall exactly which
<MichaelC> issue-584?
<trackbot> issue-584 -- Firefox has introduce a role mapping of grouping for rowgroup (should this be consistent across platforms) -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/584
<MichaelC> issue-585?
<trackbot> issue-585 -- What to do with role=rowgroup? -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/585
mc: And #585?
clown: Seems similar
mc: yes
... Is this something that can be put off to 1.1?
clown: That's the question.
... believe FF wants left as is
mc: Can we pass test cases?
clown: Don't know
mc: Need a reason to not put this off ...
clown: FF wanted this changed
... Q is what IE does
mc: Next 586 ...
<MichaelC> issue-586?
<trackbot> issue-586 -- role option cannot be a child of menu in Mac Role mapping -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/586
<clown> http://www.w3.org/WAI/PF/aria-implementation/#mapping_role_table
clown: Is AxAPI text correct?
... Sounds like jc ok with removing ...
jc: Also text about listbox
<jcraig> ACTION: Joseph to switch AX API "option" expectation back to AXStaticText⊠<nil>⊠'text'⊠[recorded in http://www.w3.org/2013/09/30-pf-minutes.html#action02]
<trackbot> Created ACTION-1270 - Switch ax api "option" expectation back to axstatictext⊠<nil>⊠'text'⊠[on Joseph Scheuhammer - due 2013-10-07].
<MichaelC> close issue-586
<trackbot> Closed issue-586.
clown: Should be done by Tuesday, also 598, on Cyns
mc: 600?
clown: Want Rich to explain
mc 612
clown: under discussion with db
mc 616
<MichaelC> issue-616?
<trackbot> 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
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/616
jc: major blocker for Apple, maybe other ua's as well
clown: Interesting,
... Cyns says it doesn't work on IE, but should
jc: Believe that's a hard sell
<clown> "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."
<clown> <div role-"button" tabindex="0" onkeydown="âŠ" >âŠ</button>
jc: ISSUE-616 expects UA's to change default behavior, and at risk as not supported (except Opera)
clown: Guess need clarification from Cyns on what is meant
... Sometimes actions can be associated
mc: Seems strays into dom activate that remains unfinished
... 3 more issues --
mc 591
jc: Noting that click now means activate in dom spec
... Should trigger click on relevant keypress, i.e. return or spacebar, if element is focused and has 'click' handler registered
... need edit to dom4
<clown> https://www.w3.org/WAI/PF/Group/track/issues/616
mc: remaining issue s need to go to UAIG call ...
Test Planning
<jongund> http://www.w3.org/WAI/PF/wiki/ARIA/UAIG_Tests
jg: Doesn't seem correct, so am checking
mc: I'll go through and look
<MichaelC> http://www.w3.org/WAI/PF/wiki/ARIA/Tests/Testable_Statements#User_Agent_Implementation_Guide_Testable_Statements
<MichaelC> action-1258: see http://www.w3.org/WAI/PF/wiki/ARIA/Tests/Testable_Statements#User_Agent_Implementation_Guide_Testable_Statements
<trackbot> Notes added to action-1258 Write some uaig test cases and expected results starting with test case 102 and working backward.
mc: We need testable statements written wherever @@ is present
... Look where ref is to UAIG
... Noting testing in process, majority of these we have defined we have passes
... Anything to discuss re "uncertain" status denotation?
jc: 85-87 need test file updates -- not changing changes via script
... Assertion is valid, but file needs update
mc: You could do those ...
jc: #31 and #32 I'm waiting on ISSUE-616
... #37 and #38 don't apply to AX API focus pointer
janina: If not applicable, not a pass because we're testing implementability
mc: Seems test files are pretty much complete
... So JG's part here particularly important
jg: OK
mc: So how much testing do we need to complete before we go LC?
... Anything likely from testing that might change UAIG?
clown: Some parts re IE
mc: So invalidate test? Or just expected results?
clown: I've made numerous UAIG changes. Have these been reflected in tests?
mc: Probably not
clown: So important
mc: There's metadata to cross ref
<jcraig> #69 and #71 waiting on ISSUE-612
<MichaelC> 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 [recorded in http://www.w3.org/2013/09/30-pf-minutes.html#action03]
<trackbot> 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].
<MichaelC> action-1271: there are commit logs that might have good pointers
<trackbot> 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.
<clown> https://www.w3.org/WAI/PF/testharness/test?testsuite_id=2&testcase_id=22&platform_id=4
Summary of Action Items
[NEW] 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
[recorded in http://www.w3.org/2013/09/30-pf-minutes.html#action03]
[NEW] ACTION: Joseph to prefix bullet 2 of #keyboard-focus_aria-activedescendant with "For platforms that expose an accessibility focus separately from the keyboard
focus," [recorded in http://www.w3.org/2013/09/30-pf-minutes.html#action01]
[NEW] ACTION: Joseph to switch AX API "option" expectation back to AXStaticText⊠<nil>⊠'text'⊠[recorded in http://www.w3.org/2013/09/30-pf-minutes.html#action02]
[End of minutes]
_________________________________________________________________________________________________________________________________________________________________
Found Scribe: janina
Present: Jon_Gunderson Joseph_Scheuhammer janina Michael_Cooper James_Craig [SAP]
Regrets: Rich_Schwerdtfeger
People with action items: cooper joseph
--
Janina Sajka, Phone: +1.443.300.2200
sip:janina@asterisk.rednote.net
Email: janina@rednote.net
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Protocols & Formats http://www.w3.org/wai/pf
Indie UI http://www.w3.org/WAI/IndieUI/
Received on Tuesday, 1 October 2013 19:09:38 UTC