See also: IRC log
<jongund_> scribe: jongund
<MichaelC> scribe: jongund_
MC: Any additions to the
agenda
... Look at the l ink to exit criteria
... Much like we have looked at before with ARIA 1.0
... I picked some initial dates
... 13 January 2017 is the earliest date to exit
... Roughly 2 months of working time for testing
... We need to formally ask for implementation
... How risky
JD: I plan to build a ATTA for OS X
JG: I am pretty committed to MSAA+IAccessibl2
JD: I am close to being done
MC: How about OS X
JD: I have not started, but I am
working with Apple on it
... I will need the initial getting started stuff
... I talked to JC at TPAC and he siad it could be done and he
would help
<MichaelC> ARIA Project Plan
MC: The proposed timeline seems OK, we can be later if it does not work out
<ShaneM> what interface does Chrome use on OSX for a11y?
MC: The plan is to go to proposed
recommendation in February
... The features that are at risk, a normative reference to the
KeyBoard Event spec, and it is not at recommendation, then the
document will change to be a recommendation, rather a
requirement
<ShaneM> I think that is fine...
JG: There is not much that can be done right?
MC: That is all I have to say
about the exit criteria
... I will give it another review
JS: There is one other thing, JC has raised an issue of a must statement for aria-roledescription
MC: I need to make a satement that all issues have been dealt with
JS: I think he +1 the current
MC: When did he submit the commit
<clown> issue-1048?
<trackbot> issue-1048 -- roledescription usage should not be limited to elements with defined ARIA roles -- raised
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/1048
JS: Issue 1048
... Raised it yesterday
MC: It is after vote to go to CR
JS: But it is against the CORE-AM
MC: He voted +1 on going to CR
<ShaneM> Did you read the issue? It makes some sense.
MC: He voted to go to CR prior to
raising this issue
... May need to speak to the director, I don't think we want to
hold it up
... If we want to take up this issue a minimum of two weeks and
will increase the scrutiny of the group
... We can put an at risk statement, we can put it against
CORE-AMM and then if is not implemented have it also change the
spec
JS: He wants it removed
... He might be ok to make it a should
MC: It is a process issue
... It will take time and then another directors meeting
JG: Make it at rick
MC: Shane says it is worthwile
issue
... Rich should be
... If I send a transition request today, it can't publish in
October
JG: can't JC lobby other developers to keep it out
MC: We can try it, but it might
blow up in our faces
... I will add this as an at risk statement
... Let's keep the issue clean
... Is there any object with that plane
... Is there any object with that plan
JS: Not from me
MC: I sent a message about an at risk related to ekyboard mapping, the option is OK with you MK
MK: You recommended changing it to a should
MC: It is a rule thing
MK: I understand, we can revisit it in 1.2
MC: Yes
... We should raise that issue now, or we might forget about
it
<MichaelC> issue: revisit normative ref to UI Events KeyboardEvent key Values when it hits rec
<trackbot> Created ISSUE-1050 - Revisit normative ref to ui events keyboardevent key values when it hits rec. Please complete additional details at <http://www.w3.org/WAI/ARIA/track/issues/1050/edit>.
MC: Anything else about CR?
... Ok, I will send out a draft CR announcement
<clown> issue-521
<trackbot> issue-521 -- Expand values for aria-relevant to cover text additions, text removals, text changes, element additions, element removals - ARIA 2.0 -- raised
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/521
<MichaelC> https://www.w3.org/WAI/ARIA/wiki/ARIA_2.0_Issue_Triage
MK: It doesn't fit current
requirements for 1.2
... Remove a button, which I have never done, is that a text
removal
MC: Leave at 2.0?
... Combobox
MK: I think we are addressing right now, it is an AT implementation and authoring issue
MC: We need to think about what
is happening in ARIA
... Maybe move to APG product
MK: I thought we could close the issue
MC: Can we move to ARIA APG and then you can close ot
MK: We have the option if there is aproblem to assign it to ARIA 2.0
<clown> issue-720
<trackbot> issue-720 -- Address deprecationg role="presentation" -- raised
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/720
MC: deprecate ROLE=PRESENTATION,
in ARIA 2.0
... Objections? none
<clown> issue-721
<trackbot> issue-721 -- Expand aria-level to include values for "auto" and "subsection" -- raised
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/721
MC: User agent calculates properties
MK: ARIA 2.0
<clown> issue-743
<trackbot> issue-743 -- Provide author defined description of state and property information -- raised
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/743
MC: Author defined state and
property
... Leave this
<clown> issue-1734
<trackbot> Sorry, but issue-1734 does not exist.
MC: Should spinbutton be a composite role
<clown> issue—1074
MK: We did that
<clown> issue-1074
<trackbot> Sorry, but issue-1074 does not exist.
MC: We discussed that
... It is listed so we can close this issue
<MichaelC> close issue-1034
<trackbot> Closed issue-1034.
MC: New drag and drop
features
... We will want to revisit in ARIA 2.0
... Use of ARIA in all W3C Specs
... I don't think this is an ARIA product
... It would be in ReSpec
... Should we ask APA to take charge of this
SC: Yes
<ShaneM> it would need to be in bikeshed too
MK: It does not fit the charter of this group
<MichaelC> issue-668: Move to APA http://www.w3.org/WAI/APA/track/issues/1001
<trackbot> Notes added to issue-668 Consider if the w3c spec format needs to be updated e.g., to use h1 for sections, after some aria roles like title introduced.
<MichaelC> close issue-668
<trackbot> Closed issue-668.
MC: Closed with a note
<ShaneM> that's awesome!
MK: We have walked through every issue
<ShaneM> can we talk about testing for a minute then?
MC: Every issue for 1.1
... Testing
SC: We have many specs under the
ARIA collection
... Web Platform Test (WPT) maps to the short names of
specs
... We are working to put the ARIA 1.0 test in
... Other specs like SVG have there own aria tests
... We want to group test results by CR
MC: The actual short name is wai-aria-1.1
SC: Really
MC: We may have a short name without the version like wai-aria
SC: Thank you, I will fix
that
... It is just convention
MC: I have not created wai-aria-1.0, I will do that
SC: That should be donw
... SVG aria implementation
... This is the svg-aam-1.0
MC: svg-aam-1.0
SC: Anyone have an opinion on the version being in the directory names
<MichielBijl> +1 to what other specs do
MK: We should do what the other specs do
MC: If it is reasonable to have version sub directories
SC: One of the WPT is dealing
with is META data for sub testing
... Sub directories are one way to deal with this
MK: The recent issues like has-popup
SC: Your right, the people
involved have not seen this issue before
... Thank you for your comments
MC: Any other issues on testing
SC: I am putting in real results from JD testing
MC: We are done on testable statements
MC: SVG2 update?
... SVG is putting in a charter for review, and will can
continue to work on SVG
... Any other agenda items for today?
<MichaelC> trackbot, end meeting
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: jongund Found Scribe: jongund_ Inferring ScribeNick: jongund_ Scribes: jongund, jongund_ Default Present: MichielBijl, MichaelC, Joanmarie_Diggs, Stefan_Schnabel, Jon_Gunderson, jongund, ShaneM, Joseph_Scheuhammer, matt_king Present: MichielBijl MichaelC Joanmarie_Diggs Stefan_Schnabel Jon_Gunderson jongund ShaneM Joseph_Scheuhammer matt_king Regrets: Rich Agenda: https://lists.w3.org/Archives/Public/public-aria/2016Oct/0054.html Found Date: 20 Oct 2016 Guessing minutes URL: http://www.w3.org/2016/10/20-aria-minutes.html People with action items:[End of scribe.perl diagnostic output]