See also: IRC log
<Rich> https://lists.w3.org/Archives/Public/public-aria/2016Jul/0090.html
<scribe> scribe: fesch
<Rich> https://www.w3.org/2002/09/wbs/83726/2016-07-07_roledescription_CfC/results
rs: goes over survey responses
on role-descripition yes 4 no 1 concur 8 abstain 1
<Rich> https://www.w3.org/2002/09/wbs/83726/2016-07-07_roledescription_CfC/results
rs: second survey yes 3 no 5 concur 6
first survey - predominately yes - 1 no
rs: based on the survey I think we should go with the first
jn: one no has an
explanation...
... by shutting down ways - you will force developers to do
more and more hacks
... prefer not shutting down the less bad hacks... preferred
the static role -
rs: looking at conversations on the list... should we have an a
ARIA 1.2?
rs" I don't want to do a 1.2 ... and prefer to move on
rs: folks have been waiting for us to finish this up
mc: we could do a 1.2 if
needed
... we only have a couple of folks to do 1.2 and some not... it
takes 6 months minimum
... if we know that we want to do a 1.2, then should we
consider doing in 1.1?
rs: no
... we are holding up ARIA in HTML...
mk: there is nothing left that is burning the house down
rs: the support for this type of functionality is all over the map... the group in general does not feel that strongly for this in 1.1
cs: can put in in the first working draft in ARIA 2...
mk: purpose is to learn and we learned
lw: we did that in webapps... can take a snapshot if stuff is stable
rs: the two James find this feature is important...
mc: implement early means it can be changed...
rs: lets get ARIA 1.1 done
... looks like the group has gone with option 1
... we should start an ARIA 2 editors draft sooner...
cs: github can manage any
updates...
... we could password in a draft...
rs: I don't care about password
role - group has addressed technical issues - hopefully the
security group will come up with something better
... Do we agree the group agrees on option 1?
... Joanie pull in the branch for option 3
<Rich> http://rawgit.com/w3c/aria/action2092option3/aria/aria.html#aria-roledescription
rs: we are picking option 1 in
survey (option 3 branch)
... we are moving to pseudo last call
... how long for comments
mc: one month
... we normally do messaging to - WAI IG, twitter, mailing
lists...
... this is a wide review draft
<Rich> ACTION: mking3 Create strongly wored guidance in the authoring practices for aria-roledescription [recorded in http://www.w3.org/2016/07/14-aria-minutes.html#action01]
<trackbot> Created ACTION-2100 - Create strongly wored guidance in the authoring practices for aria-roledescription [on Matthew King - due 2016-07-21].
<Rich> action-2100?
<trackbot> action-2100 -- Matthew King to Create strongly wored guidance in the authoring practices for aria-roledescription -- due 2016-07-21 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2100
rs: list is for weighing in on a
CfC, we have turned it into technical decisions
... we can't do that, too much chatter
... if you have technical decisions about CfCs do that on
public aria
... that makes it visible to folks
mc: other folks can read it, but
not post
... want to keep noise down on admin list
rs: we would like to make these 3
docs pushed to publication - working drafts
... any objections?
RESOLUTION: Publish First Working Draft Graphics Module AAM, Heartbeat of Graphics Module and SVG AAM
mc: may be ready by end of the month
<Rich> https://www.w3.org/2002/09/wbs/35125/TPAC2016/registrants#ARIA
<MichaelC> Note that URI may not be visible to everyone here
rs: will be setting up meetings, COGA wants 2 hours... asked Janinia will split it up with APA, will meet with TAG for ARIA 2.0
<Rich> https://www.w3.org/WAI/ARIA/wiki/Meetings/TPAC_2016
rs: did anyone add to the wiki?
If you have stuff you want covered at TPAC put on wiki
... need to set up interlocks with other groups...
<Rich> https://www.w3.org/WAI/ARIA/project
rs: we need to look at plans, I don't know if we will make August for ARA I.1
mc: TPAC will interfere with September, what about October?
rs: Jospeh still has an action item list
<clown> https://www.w3.org/WAI/ARIA/track/products/23
<clown> issues/actions for core-aam ^
cs: building the test cases and
harnesses will take a couple of months
... could get testing done by end of September
rs: need to make sure folks have implemented it
mc: can try for Feb for CR and
April for recommendation
... several others will be on the same timeline, Core
AAM...
rs: what about dPub? Can you do that in edge?
cs: we haven't talked about it.
rs: we probably will see it in
webkit and firefox
... may not get edge
... only roles, no properties...
mc: lists docs on same timeline...
rs: has edge looked at SVG at all?
cs: SVG AAM - no
rs: I don't know what will happen
with SVG working group, they lost 2 chairs...
... I think we can get webkit, chrome and maybe firefox
... February may be OK
fe: we can get the tests translated we have the perl scirpt, just need the final form
rs: lets shoot for November for
CR for SVG AAM
... May for PR, June for REC
... may be later for Graphics AAM, only has 3 roles
... we can have a very short CR periiod
... I would enter Graphics AAM a little later than SVG AAM
<MichaelC> SVG Roadmap (out of date?)
mc: In theory they should have
entered CR in Feb 2016... can't predict based on what they
have...
... want to make sure the group knows about the times
<Rich> https://www.w3.org/WAI/ARIA/project
<AmeliaBR> SVG 2 will have a last call WD / first call CR in the next month. Will probably be revised a few times once implementers start actually working on it. There are a few changes that will filter down to SVG AAM, but that should be soon.
lw: does the timeline assume problems?
mc: includes some slack for getting implementations
cs: filling out test
infrastructure will take some time
... we had a discussion on writing the test cases
... we talked about all the pieces that need to be done... one
thing is get the other APIs....
... shane will integrate reporting infrastructure
<MichaelC> Minutes ARIA Test 13 July 2016
cs: I will propose on documenting
stuff in JSON and a dev will work on parsing
... then we will ask others to get testcases...
rs: don't want to repeat ARIA 1.0 want lots of folks to help
jg: shane wants to demonstrate how the current test platform could work with for WPT
cs: some of that already works
jg: we we build a testcase - in a JSON format
fe: we have a perl script for handling the SVG tests
jg: In the next month we will have a clear idea of how it will work
<Zakim> MichaelC, you wanted to ask if you have established a regular meeting time
rrsaggent, make minutes
cs: Jon did we decide to meet in 2 weeks?
jg: yes
<MichaelC> ARIA Test list
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Survey/Survey on CFC resutlss/ Succeeded: s/option 1/option 3/ Succeeded: s/WTT/WPT/ Found Scribe: fesch Inferring ScribeNick: fesch Present: Joanmarie_Diggs Janina Leonie Michiel_Bijl fesch Rich_Schwerdtfeger MichaelC Joseph_Scheuhammer jaeunJemmaku jongund Bryan_Garaventa Agenda: https://lists.w3.org/Archives/Public/public-aria/2016Jul/0090.html Found Date: 14 Jul 2016 Guessing minutes URL: http://www.w3.org/2016/07/14-aria-minutes.html People with action items: mking3 WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]