See also: IRC log
<trackbot> Sorry, but this channel isn't in my configuration.
<trackbot> If you want to associate this channel with an existing Tracker, please say 'trackbot, associate this channel with #channel' (where #channel is the name of default channel for the group)
trackbot: this is aapi
<trackbot> Sorry, clown, I don't understand 'trackbot: this is aapi'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.
trackbot, associate this channel with #aapi
<trackbot> Associated this channel with #aapi.
<trackbot> Sorry, but this channel isn't in my configuration.
<trackbot> If you want to associate this channel with an existing Tracker, please say 'trackbot, associate this channel with #channel' (where #channel is the name of default channel for the group)
trackbot, associate this channel with #pf
<trackbot> Associated this channel with #pf.
action-891?
<trackbot> ACTION-891 -- Matthew King to write testable statements for aria-describedby -- due 2012-03-05 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/891
<scribe> agenda: this
<scribe> scribenick: clown
action-891?
<trackbot> ACTION-891 -- Matthew King to write testable statements for aria-describedby -- due 2012-03-05 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/891
http://www.w3.org/WAI/PF/aria-implementation/#mapping_state-property_table
really a question for Cynthia, but she is not here.
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
http://www.w3.org/WAI/PF/aria-implementation/#keyboard-focus_tabindex
resolution: keep the "Controlling focus with tabindex" secition in the UAIG, and write test cases for it when the UAIG is in CR. They will most likely pass.
resolved: keep the "Controlling focus with tabindex" secition in the UAIG, and write test cases for it when the UAIG is in CR. They will most likely pass.
RESOLUTION: keep the "Controlling focus with tabindex" secition in the UAIG, and write test cases for it when the UAIG is in CR. They will most likely pass.
DB: want to use the rest of the time to work on my action.
action-983?
<trackbot> ACTION-983 -- David Bolter to create MSAA/IA2 special case test cases from existing generated test cases for the tables. -- due 2012-03-14 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/983
action-1102?
<trackbot> ACTION-1102 -- David Bolter to get someone to look at the SHOULD statements in the Role Mapping table. Can these be changed from "SHOULD be exposed" to "expose as" -- due 2012-07-25 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1102
<davidb> http://www.w3.org/WAI/PF/aria-implementation/#mapping_role_table
DB: a button that gets an
aria-pressed attribute after the page has loaded, might not be
exposed as a toggle button.
... if you change the role in MSAA, you should destroy the
object, and create a new one.
JS: that's in the spec, for all
AAPIs.
... if aria-pressed is present from the beginning, any reason
to not expose as toggle button?
DB: let me check the code.
... actually it should work dynamically as well. So, it should
work in FF.
JS: next one is listbox role. under AT-SPI
DB: looking at ATK.
... feel like asking joanie if that is correct — that a
LIST_BOX becomes a MENU when owed by a combobox.
... found a ATK to UIA mapping that suggest it becomes a
menu.
... I'm inclined to remove the 'SHOULD be' here.
<davidb> was here http://www.mono-project.com/Accessibility:_UiaAtkBridge
JS: next one is option. if the OPTION has a parent that is MENU, then the OPTION is exposed as MENU_ITEM.
DB: I'm ok with removing the SHOULD.
JS: next one is aria-label and
Apple's AX. I'll ask James about that one.
... next is aria-level, in the IA2 column.
DB: I'm trying to understand the
purpose of that statement,
... I guess it's trying to say that the cleaned up a11y tree
structure should match the aria-level value.
... I would take it out.
<scribe> ACTION: Joseph to replace the "should be" the sentence "The structure should be reflected in the accessibility tree as directed by aria-level" with "is". [recorded in http://www.w3.org/2013/01/10-aapi-minutes.html#action01]
<trackbot> Created ACTION-1145 - Replace the "should be" the sentence "The structure should be reflected in the accessibility tree as directed by aria-level" with "is". [on Joseph Scheuhammer - due 2013-01-17].
JS: next is aria-owns
DB: the IE team may be doing
something dangerous here, namely, changing the structure of the
a11y tree.
... FF doesn't do that. It would make the code fragile.
... these "should"s probably predate the columns...
... probably make these actual SHOULD (normative).
JS: that's a question for
Cynthia, since the "should be" is in the UIA columns.
... also there is a "should not be" in the IA2 column. Change
that to an "is"?
JS; "is not"
https://www.w3.org/WAI/PF/testharness/testcases/edit/110
<scribe> ACTION: Joseph to change the "should not" in "The accessibility tree should not be modified." to "is not" for aria-owns property in UAIG state/properties table. [recorded in http://www.w3.org/2013/01/10-aapi-minutes.html#action02]
<trackbot> Created ACTION-1146 - Change the "should not" in "The accessibility tree should not be modified." to "is not" for aria-owns property in UAIG state/properties table. [on Joseph Scheuhammer - due 2013-01-17].
JS: next one is aria-posinset.
Looks same as aria-level.
... one more under menu, a "SHOULD not be"
DB: I don't know what that is
talking about.
... needs more text to explain what that is about.
<scribe> ACTION: David Bolter to explain ATK/AT-SPI menu role mapping "SHOULD NOT be" note. [recorded in http://www.w3.org/2013/01/10-aapi-minutes.html#action03]
<trackbot> Created ACTION-1147 - Bolter to explain ATK/AT-SPI menu role mapping "SHOULD NOT be" note. [on David Bolter - due 2013-01-17].
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: clown Inferring Scribes: clown WARNING: No "Topic:" lines found. Default Present: [Mozilla], [GVoice] Present: David_Bolter Joseph_Scheuhammer WARNING: Fewer than 3 people found for Present list! Regrets: Cynthia Agenda: http://lists.w3.org/Archives/Public/wai-xtech/2013Jan/0015.html Got date from IRC log name: 10 Jan 2013 Guessing minutes URL: http://www.w3.org/2013/01/10-aapi-minutes.html People with action items: bolter david joseph WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]