meeting minutes: August 4, 2016 WAI-ARIA Working Group

Here is WAI-ARIA Working Group meeting minutes.
https://www.w3.org/2016/08/04-aria-minutes.html

JaEun Jemma Ku, PhD
Internet Applications Systems Specialist
University library
University of Illinois at Urbana-Champaign
424 Library, M/C 522
1408 West Gregory Dr.
Urbana, IL 61801
1-217-244-2145
jku@illinois.edu


[W3C]<http://www.w3.org/>
- DRAFT -
Accessible Rich Internet Applications Working Group Teleconference
04 Aug 2016
See also: IRC log<http://www.w3.org/2016/08/04-aria-irc>
Attendees
Present
Joanmarie_Diggs, JaEunKu, Rich_Schwerdtfeger, LJWatson, fesch, Joseph_Scheuhammer, Bryan_Garaventa, Michael, Cooper, Janina
Regrets
Matt_King, michielbijl
Chair
Rich
Scribe
JaEun, JaeunKU
Contents

  *   Topics<https://www.w3.org/2016/08/04-aria-minutes.html#agenda>
1.   issue-1043<https://www.w3.org/2016/08/04-aria-minutes.html#item01>

  *   Summary of Action Items<https://www.w3.org/2016/08/04-aria-minutes.html#ActionSummary>
  *   Summary of Resolutions<https://www.w3.org/2016/08/04-aria-minutes.html#ResolutionSummary>

________________________________
<jemma> scribe:JaEun
<jemma> scribe: JaeunKU
<jemma> Topic
<jemma> llst attendees
<jemma> Testable Statements (Coordination) and test case Authoring
<Rich> https://www.w3.org/WAI/PF/testharness/testcases?testsuite_id=4
<jemma> rs: we need to break up testable statement, Michael
<jemma> mc: subgroup has been working on testable statement including Cynthia
<jemma> and other people
<jemma> cyn: made some progress and add info to wiki
<jemma> cyn: can you send me the location of actual statements, Rich?
<Rich> https://www.w3.org/WAI/PF/testharness/testcases?testsuite_id=4
<jemma> mc: Michael sent those
<clown> this url isn't working: https://www.w3.org/WAI/PF/testharness/testsuites?testsuite_id=1 (ARIA 1.0)
<jemma> rs: testing each new feature in aria spec
<jemma> rs: go through the form and added info for expected results
<MichaelC> use https://www.w3.org/WAI/PF/testharness/testcases?testsuite_id=1
<clown> Okay, MichaeC, but that means the link on the testharness page needs fixing.
<jemma> cyn: I translated the test case into json format, open test harness, and look at testable statement, copy html content and I have to go back to container again, human reable stuff.
<fesch> https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions_with_Tables
<jemma> cyn: curent items are pretty hard to make it machine readable format. we would like to have something machine readable with db
<jemma> rs: that is not possible for now.
<fesch> https://www.w3.org/wiki/ARIA_1.1_Automated_Testing#Alternative_Draft_ARIA_Test_Case_Format
<jemma> fred: made a file which put all the test files and I am flexible to make any file type you need for testing
<jemma> mc: testable statement is expected result but it is not one to one relationship with test case.
<jemma> mc: test file lives in git hub
<jemma> cyn: test harness is only place I need to look at for automated testing? is that correct?
<jemma> mc: yes
<jemma> cyn: if there are things that is not going to automated testing, it is helpful.
<jemma> rs: it is only 5
<Rich> https://rawgit.com/w3c/aria/CR-pub/aria/aria.html#sotd
<jemma> mc: we can do create test case for new features in aria
<jemma> using index and other doc
<jemma> rs: we need to writing testable statementss for new or changed ARIA features
<jemma> js: how des this fit with automatically generated test?
<jemma> fred: they were basically copy and paste
<jemma> mc: it has been hard to use generator in filtering what is new and changed one.
<jongund> https://www.w3.org/wiki/ARIA_1.1_Automated_Testing#Draft_ARIA_Test_Case_Format
<jemma> cyn: Microsoft is building testing demo cases using aira 1.1 (jason format) and runs aoutomatic tesitng, expecting human readable. - all the info is in the wiki.
<jemma> rs: something like object attribute is true?
<jemma> cyn: element is the id
<jemma> rs: I would like to see title is done at least
<jemma> rs:while cynthia is working on format, I can do title for test statement.
<jemma> fred: writing testable is possible by human readable ?
<jemma> rs: fred, will you put this in the wik?
<jemma> fred: it may need for svg too for the consistency
<Rich> https://www.w3.org/wiki/ARIA_1.1_Automated_Testing#Alternative_Draft_ARIA_Test_Case_Format
<jemma> fred: there are things pretty straight forward such as name calculation, etc
<fesch> https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions_with_Tables
<jemma> fred: the link includes the result
<jemma> rs: these are also test cases?
<jemma> fred: yes
<jemma> rs; do you want keep this format?
<jemma> fred: yes, if we do have those, we can use perl script
<jemma> fred: whatever aam has can be captured in this kind of table.(In responding to Rich's question such as complex case?)
<jemma> jg: if we revise perl script a little bit, we can still use this structure
<jemma> fred: I think this is pretty human readable and can find errors easily
<jemma> rs:all up for this wikii?
<jemma> fred: all outliers can be taken care of separately but 90% can be taken care of.
<jemma> using this
<Rich> https://rawgit.com/w3c/aria/CR-pub/aria/aria.html#sotd
<jemma> rs: should we work on Michael's exit criteria?
<MichaelC> https://www.w3.org/TR/wai-aria-1.1/#changelog
<jemma> mc: we can refer appendix and Joannie was on top of updating this.
<jemma> rs: we need to break changelog up and assign works.
<jemma> jd: we need come up with net total first such as removing password role.
<jemma> jd: I don't think just dividing the work by date does not make sense. why don't we let John or John's people look over the net change?
<MichaelC> ACTION: cooper to do a ¨net change¨ list in preparation for test case development [recorded in http://www.w3.org/2016/08/04-aria-minutes.html#action01]
<trackbot> Created ACTION-2105 - Do a ¨net change¨ list in preparation for test case development [on Michael Cooper - due 2016-08-11].
<jemma> mc: we need to find net change first.
<jemma> mc: we would not do complete test for CR exit
<jemma> jg: so we would not do any testing for existing ones, only for changes?
<jemma> mc: yes for CR
<jemma> jg: I will send out doc so that Fred can look at it. It is pretty concrete template, so people in india does not need do work from the scratch
<jemma> jg: we hope to do comprehensive testing but we will more focus on testing for CR exit review
<MichaelC> action-2105: talk with Joanie about this
<trackbot> Notes added to action-2105 Do a ¨net change¨ list in preparation for test case development.
<clown> issue-1043
<trackbot> issue-1043 -- -- open
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/1043
<Rich> https://www.w3.org/WAI/ARIA/track/issues/1043
issue-1043
<Rich> http://rawgit.com/w3c/aria/master/aria/aria.html#aria-details
<jemma> rs: publishers want to hide detailes
<joanie> Joanie will work with Michael to come up with a list summarizing the changes we must test.
<jemma> rs: we need to change one sentence
<jemma> rs: make it "should"
<jemma> js: why was it "must" at first?
<jemma> js:they want to have "should" and have reverse relationship in a11y api. they can not have both.
<jemma> rs: Publishers want to hide details button, so put some visual indicator such as "more info" and let user turn on and off
<jemma> janina: not our battle, this is for non AT users
<jemma> rs: target is hidden and there is no mapping
<jemma> js: I would like to think about this.
<jemma> js: plus +0 for me ;-)
<jemma> rs:what do you think about this issue? do you want a survey?
<chaals> [is there any implementation of this?]
<jemma> rs: do you mean API mapping for "implementation"?
<Rich> [do you mean api mappings?]
<chaals> [I mean is there implementation of aria-details that I can test end-to-end]
<Rich> [charles, we need to create the api mappings]
<clown> there are implementations of <details>/<summary> which is one way to cash-in on aria-details, chaals
<Rich> [we have an example of that in the aria spec. using the <details>/<summary> pattern
<clown> [Example 17]
<Rich> http://rawgit.com/w3c/aria/master/aria/aria.html#aria-details
<chaals> [that only applies to a particular form of the local case, where the details are in exactly the same place - except that in details/summary the details are hidden by default]
<Rich> [yes, but you do see a button when the cotent is hidden. publishers want to hide even that]
<chaals> [I'm not surprised they want to hide that]
<Rich> :-)
RESOLUTION: change "must" to "should" in aria details.
<jemma> rs: Joanie, can you change that?
<jemma> rs: do you want me to create the branch?
<jemma> mc: I would recommend to create the branch if it goes out for CFC
<Rich> ACTION: Rich create branch for the CFC for aria-details and the authors must going to an authors SHOULD [recorded in http://www.w3.org/2016/08/04-aria-minutes.html#action02]
<trackbot> Created ACTION-2106 - Create branch for the cfc for aria-details and the authors must going to an authors should [on Richard Schwerdtfeger - due 2016-08-11].
<jemma> rs: is there any other blockers for entering CR? any thing new, Joseph?
<jemma> js: nothing new since last week meeting.
<jemma> list attendees
<clown> https://lists.linuxfoundation.org/pipermail/accessibility-ia2/2014-November/001852.html
<clown> https://lists.linuxfoundation.org/pipermail/accessibility-ia2/2014-November/001853.html
<jemma> rs: when would you be able to publish the working draft?
<jemma> ms: I can start working on it tomorrow and may take two weeks or so.
<jemma> Chair: Rich_Schwerdtfeger
<jemma> s/if there are things that is not going to automated testing it is helpful./knowing that there are things that is not going to be part of automated testing would be helpful.
Summary of Action Items
[NEW] ACTION: cooper to do a ¨net change¨ list in preparation for test case development [recorded in http://www.w3.org/2016/08/04-aria-minutes.html#action01]
[NEW] ACTION: Rich create branch for the CFC for aria-details and the authors must going to an authors SHOULD [recorded in http://www.w3.org/2016/08/04-aria-minutes.html#action02]


Summary of Resolutions
1.   change "must" to "should" in aria details.<https://www.w3.org/2016/08/04-aria-minutes.html#resolution01>
[End of minutes]


From: Richard Schwerdtfeger [mailto:richschwer@gmail.com]
Sent: Wednesday, August 03, 2016 8:40 AM
To: ARIA Working Group <public-aria@w3.org>
Subject: Agenda: August 4, 2016 WAI-ARIA Working Group




Agenda: August 4, 2016 WAI-ARIA Working Group



Time of meeting is 12:30PM EST, 9:30AM PST, 16:30 UTC, duration is 1.5 hours



Webex: https://mit.webex.com/mit/j.php?MTID=m5d67b552441a72bd1f52d696ad273d2e<https://urldefense.proofpoint.com/v2/url?u=https-3A__mit.webex.com_mit_j.php-3FMTID-3Dm5d67b552441a72bd1f52d696ad273d2e&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=O0UZCHuazg7lue4fqeurescWrIh_Il6OoOPDYHvjrTE&e=>

US Toll Number: +1-617-324-0000 Access code:640 582 571 (Mobile Auto Dial: +1-617-324-0000,,,640582571#)



IRC: server: http://irc.w3.org/<https://urldefense.proofpoint.com/v2/url?u=http-3A__irc.w3.org_&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=7ze-zEDpzKbmLW3GudZns9Iv8F3MxqX2wjZWb9scS8c&e=> <http://irc.w3.org/<https://urldefense.proofpoint.com/v2/url?u=http-3A__irc.w3.org_&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=7ze-zEDpzKbmLW3GudZns9Iv8F3MxqX2wjZWb9scS8c&e=>>  , port: 6665, channel: #aria.

Agenda:



1. Testable Statements (Coordination) and test case Authoring

        - Exit Criteria: https://rawgit.com/w3c/aria/CR-pub/aria/aria.html#sotd<https://urldefense.proofpoint.com/v2/url?u=https-3A__rawgit.com_w3c_aria_CR-2Dpub_aria_aria.html-23sotd&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=eTVANh_WqwfEJKq58n7x3PhiUYpjRVOWwJzO66pOT4Q&e=>

        - Test Harness: https://www.w3.org/WAI/PF/testharness/testcases?testsuite_id=4<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_PF_testharness_testcases-3Ftestsuite-5Fid-3D4&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=C-RE6dn-s-J_BI84UqIISRhyJvh-6j-mXg3vwCgS_9E&e=>

2. Blockers for entering CR?





References:



ARIA Test Plan Action Items:



http://www.w3.org/WAI/PF/Group/track/products/5<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_WAI_PF_Group_track_products_5&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=qPVTSrk2xMvjZ4xZ1_kQgoWV2j08FTBz-ynPnypgo2E&e=>



ARIA Implementation Guide:



http://www.w3.org/WAI/ARIA/track/products/23<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_WAI_ARIA_track_products_23&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=SpVXV9Dt0QHSttRIwYmEFLW5CyFUfe6ABHzOh6AzaKU&e=>



ARIA Name Computation Issues and Actions:



http://www.w3.org/WAI/ARIA/track/products/26<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_WAI_ARIA_track_products_26&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=othCRrlmLimZh_RaQnFH4rGz0NPx3gSekvbsFR8aGhQ&e=>



ARIA Test Report:



https://www.w3.org/WAI/PF/testharness/testreport?testsuite_id=1<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_PF_testharness_testreport-3Ftestsuite-5Fid-3D1&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=KaW6aUqC6LQuzad98RUrecLuwLTVslN9zQARv7LcUkA&e=>



ARIA 1.1 Test Plan Issues and Actions:



http://www.w3.org/WAI/ARIA/track/products/25<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_WAI_ARIA_track_products_25&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=mYbBjEWqgcXzZG0Tlnwx_P8J9b0QMo75830DS5mk4K4&e=>



ARIA 1.1 Test Harness:



https://www.w3.org/WAI/PF/testharness/testcases?testsuite_id=4<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_PF_testharness_testcases-3Ftestsuite-5Fid-3D4&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=C-RE6dn-s-J_BI84UqIISRhyJvh-6j-mXg3vwCgS_9E&e=>



WAI-ARIA Extension Process:

https://www.w3.org/WAI/PF/wiki/ARIAExtensions<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_PF_wiki_ARIAExtensions&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=qs-moLQxlEUHlKjsx4DiwN4CFeePSJdwHwBEy4ZGh_Q&e=>



ARIA Working Group Decision Policy

https://www.w3.org/WAI/ARIA/decision-policy<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_ARIA_decision-2Dpolicy&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=MasxnD4k0u7Vnm8poxAaPCwE7vEJiRsPOImVWxDbAmY&e=>

Open actions and issues:

https://www.w3.org/WAI/ARIA/track/products/17<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_ARIA_track_products_17&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=IEGbTo1ttPHEbiXimAwpaja9Q2NXmZ-3UJxvq1qI5HA&e=>



Minutes Last Meeting:

https://www.w3.org/2016/07/28-aria-minutes.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2016_07_28-2Daria-2Dminutes.html&d=CwMCAg&c=8hUWFZcy2Z-Za5rBPlktOQ&r=tYy0Yf6x95Anoyy4MyCJ-w&m=TWfivUKCMbMeIbe0k7PNjtYi1wT9vctwvxhZ2pmxSOA&s=DGcoXZohZxEidBqlgQwTW8MzhLW2gWKkX0KTcd5NLLQ&e=>