See also: IRC log
<clown> agenda: this
<clown> - Also bugzillas:
<clown> https://www.w3.org/Bugs/Public/buglist.cgi?component=Core%20AAM&product=ARIA
<clown> https://www.w3.org/Bugs/Public/buglist.cgi?component=AccName%20AAM&product=ARIA
<clown> https://www.w3.org/WAI/PF/Group/track/products/26
<scribe> scribe: Joanmarie_Diggs
<cyns> thank you!
<clown> ACTION-1569?
<trackbot> ACTION-1569 -- Joseph Scheuhammer to Create a section that describes AAPI differences -- due 2016-02-23 -- PENDINGREVIEW
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/1569
JS: I incorporated all of Jason's
and Cynthia's changes.
... I pushed them and asked for feedback.
CS: I did my action item about changing the example.
<clown> https://lists.w3.org/Archives/Public/wai-xtech/2016Feb/0050.html
JS: Jason replied (see
above).
... He wants to change the end of the second paragraph.
... He wants us to not use "accessible" as a noun.
CS: I tend to agree with him.
JS: I pointed out that it's used this way throughout the document.
CS: You can give him an action item if he wants to change it.
JS: Is it especially egregious?
CS: Up to you if you want to make the change or ask him to do it.
JS: It might be referencing the glossary, which would make it more challenging.
CS: You could also make a glossary entry with accessible used as a noun, which might be less work.
JS: The next issue Jason
mentioned: (Joseph reads text of 1.1)
... Jason wants to drop the word "static"
... I thought about it a bit.
... And I thought it's correct because you need ARIA to get
across the correct semantics.
... So the DOM does not represent the correct semantics.
CS: But it says "structure and
state".
... That could mean accessibility structure and state, or DOM
structure and state, or....
... And it's introductory material.
JS: Jason raised a similar issue
(Joseph reads from email)
... Jason suggested that the text suggests ATs only use
accessibility APIs for interactive content.
... Which of course is not correct (any longer).
... I responded to him that I agree and that this text should
be updated.
... He has a recommended rewrite for the UIA section.
... Cynthia responded.
<clown> https://lists.w3.org/Archives/Public/wai-xtech/2016Feb/0051.html
<clown> https://lists.w3.org/Archives/Public/wai-xtech/2016Feb/0053.html
JS: (Reads from Cynthia's reply at above URL)
CS: The last thing that was written there is fine.
JS: Where's "there"?
CS: In his email.
... The way that he phrased it is better.
<clown> action-1585
<trackbot> action-1585 -- Joseph Scheuhammer to Add to the section on differences among aapis highlighting the features of uia. -- due 2016-01-15 -- PENDINGREVIEW
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/1585
CS: But with the example I redid,
that may not work.
... The button example he uses in his rewrite is incorrect.
JS: So I should use your (Cynthia's) text in the rewrite?
<clown> action-2032
<trackbot> action-2032 -- Joseph Scheuhammer to Provide a new example for the accessibility api explanatory text. -- due 2016-03-01 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2032
JS: That replaces the example. What else should we change?
CS: Can you munge them together and we can look at them next week?
JS: Yes.
CS: I will be reviewing the
complete UIA column next week.
... I may just do a pull request as I don't think we need to
have a discussion about each cell in that table.
JS: Since we didn't test UIA last time, we need to test everything this time.
(Some discussion about restoring the UIA Express column)
JS: We need to talk to Alex Surkov about this.
CS: I think it was about the HTML-AAM.
JS: We removed it from Core. Jason asked if we should remove it from HTML-AAM?
CS: Alex pointed out that some implementations (i.e. Firefox) may still use it.
JS: Does this imply anything about testing?
CS: It might.
... And we don't know if we have a testable implementation of
UIA Express.
... Unless Alex wants us to use Firefox to test for UIA
Express.
JS: We have plan for differences
amongst Accessibility APIs:
... I'll tell Jason to go ahead with the accessible
objects.
... I'll munge the changes.
<clown> https://github.com/w3c/aria/pull/272
JS: Your (Cynthia's) github pull request for landmarks: I'm fine with that, but if we make your change here, we need to do it everywhere.
CS: I don't think that's the only change I made.
JS: No, the rest I'm fine with.
<clown> https://github.com/w3c/aria/commit/5b29b85d5d4ebee1b374bef2f887b8b6dd72cac9
<clown> ACTION: cynthia to change the phrase "Control type/role" to "Control Type" throughout the Core-AAM [recorded in http://www.w3.org/2016/03/01-aapi-irc]
<trackbot> Created ACTION-2037 - Change the phrase "control type/role" to "control type" throughout the core-aam [on Cynthia Shelly - due 2016-03-08].
<clown> action-2037
<trackbot> action-2037 -- Cynthia Shelly to Change the phrase "control type/role" to "control type" throughout the core-aam -- due 2016-03-08 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2037
CS: Go ahead and merge the
current pull request.
... And give me an action to do the other changes to "control
type".
<clown> action-1593
<trackbot> action-1593 -- Cynthia Shelly to Compare implementations of AAPI managed states and look for gaps. -- due 2016-03-04 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/1593
JS: We talked about this briefly last week.
CS: I didn't get to this one
yet.
... Let's move it to the 29th.
... And when are we doing test file creation?
CS: I had an action due today to create a test case.
action-1373
<trackbot> action-1373 -- Cynthia Shelly to Create a test case for when aria-posinset and aria-setsize are provided explicitly on some but not all elements. -- due 2016-03-01 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/1373
CS: I'd like to align this with
when the other test case writing takes place.
... Testing starts after last call?
JD: When is last call?
JS: I think the plan is, because we've been doing heartbeats regularly now, we choose the last heartbeat for last call.
CS: There's no way all the test cases will be written by March 11th.
JS: I'll add a note that the due date for this action should coincide with test case creation.
<clown> action-1541
<trackbot> action-1541 -- Joseph Scheuhammer to Investigate and propose mappings for aria-modal property for axapi. -- due 2016-02-08 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/1541
JS: I did a little research. And
found the above in the Apple documentation.
... There is a accessibility-modal property of a window.
<clown> https://bugs.webkit.org/show_bug.cgi?id=138566#c23
<clown> @property(getter=isAccessibilityModal) BOOL accessibilityModal
JS: The method is isAccessibilityModal()
<clown> A Boolean value that determines whether the window is modal.
JS: The documentation states the
above.
... That tells the AT programmer what to look for, but not what
to look for in the accessibility inspector.
<clown> https://bugs.webkit.org/show_bug.cgi?id=138566#c23
JS: So I commented on the bug
associated with the implementation.
... I asked them what to put in the accessibility
mappings.
... I haven't gotten a reply.
JD: If memory serves me, they
don't expose the property; the act upon it being present.
... For instance, if an aria-modal dialog became active, the
page content underneath would be treated as if aria-hidden were
true.
... I think. I am not Apple.
JS: So how do we test it?
JD: Hypothetically, if you had a
page with text and an OK button that triggered the appearance
of an aria-modal dialog, then you would activate the button and
then look in the accessibility tree to verify that text and
that button were not in the accessibility tree.
... And you would probably also want to verify that upon
dismissing the aria-modal dialog, the original content was
re-added back to the accessibility tree.
JS: Rich and Alex are not
here.
... There is an email thread.
... We'll put it off to next week since Rich is not here.
<clown> object:state-changed:invalid_entry
ATK_STATE_INVALID_ENTRY
Indicates that the object has encountered an error condition due to failure of input validation. For instance, a form control may acquire this state in response to invalid or malformed user input.
<clown> http://w3c.github.io/aria/core-aam/core-aam.html#mapping_events_state-change
ATK_STATE_INVALID
Indicates an invalid state - probably an error condition.
<clown> issue-1013
<trackbot> issue-1013 -- Is there a need for an aapi event for aria-errormessage -- open
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/1013
JS: I raised the above issue.
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) Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** No ScribeNick specified. Guessing ScribeNick: joanie Found Scribe: Joanmarie_Diggs Default Present: Joanmarie_Diggs, Cynthia_Shelly, Joseph_Scheuhammer Present: Joanmarie_Diggs Cynthia_Shelly Joseph_Scheuhammer Regrets: Rich_Schwerdtfeger Bryan_Garaventa Found Date: 01 Mar 2016 People with action items: cynthia WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]