See also: IRC log
<trackbot> Date: 14 July 2015
<clown> agenda: this
<clown> agneda+ ACTION-1625 (Joseph, All) Mappings for aria-interactive property.
as the url just loaded in firefox and told me my browser wasn't supported
me tries just the number
<clown> action-1160?
<trackbot> action-1160 -- Janina Sajka to Take at look at MediaStream Recording http://www.w3.org/TR/2013/WD-mediastream-recording-20130205/ -- due 2013-02-13 -- CLOSED
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1160
<clown> action-1661?
<trackbot> action-1661 -- Cynthia Shelly to Propose uia express and uia mappings for aria-description. -- due 2015-07-22 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1661
<clown> action-1660?
<trackbot> action-1660 -- Joanmarie Diggs to Propose the ATK/AT-SPI mappings for aria-roledescription. -- due 2015-06-30 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1660
<clown> action-1662?
<trackbot> action-1662 -- Alexander Surkov to Propose IA2 mapping for aria-description -- due 2015-06-30 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1662
<scribe> scribe: joanie
<clown> action-1625?
<trackbot> action-1625 -- Joseph Scheuhammer to Add interactive property to core mappings that propogates from grid or table to all grid aria grid or table structural elements. the interactive property should have same mapping as defined in issue 633 -- due 2015-09-08 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1625
JS: There was a proposal in the caucus to have an aria-interactive.
<clown> issue-633?
<trackbot> issue-633 -- listbox and tree may contain only static items; badly need interactive widgets that can contain interactive typed items -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/633
JS: That is isue 633.
CS: I thought that was discarded.
JS: It's disappeared.
<clown> https://www.w3.org/Bugs/Public/show_bug.cgi?id=27866
JS: Michael has commented that
it's closed for tables, but we still need to address it for
other objects.
... Ah, this is by Dominic.
... Need to introduce attribute to indicate key handlers.
... But I think that's been replaced with the
aria-hotkey.
... So I don't think we need this.
<clown> action-1505?
<trackbot> action-1505 -- Matthew King to Create an aria-interactive property for issue 633 -- due 2015-05-08 -- CLOSED
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1505
BG: But this interactive propoerty I think is an indication that ATs should not control the interaction.
JS: I'll bring this up at the
next Thursday call and ask if this thing still exists.
... Because it doesn't make sense to propose mappings for it if
it isn't going to be added to the spec.
<clown> action-1322?
<trackbot> action-1322 -- Jon Gunderson to Make some examples for aria-hidden="false" (including a hidden live region) -- due 2014-09-29 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1322
JS: This is an action I
discovered which is way past due on Jon Gunderson to make
examples on aria-hiden="false" including live regions.
... I've emailed to Jon to ask him what this is all about
because I do not know. Also, which is this associated with the
mapping spec?
... I've not yet heard back from Jon.
... Does anyone here know why?
BG: (Requests repeat)
JS: (Repeats it)
CS: Maybe this is for the
authoring guide.
... Why don't we just change it to that product?
JS: Bryan, are you (in the authoring group) still working on 1.1?
BG: Yes.
JS: Ok, I'll transfer it to your group then.
JS: This one and the next one,
I've sent at least three emails related to mapping .
... I've not heard back.
<clown> action-1541?
<trackbot> action-1541 -- James Craig to Investigate and propose mappings for aria-modal property for axapi. -- due 2014-12-02 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1541
JD: I think they have a modal property; don't know about current.
JS: I made that suggestion for modal.
CS: I remember that discussion. I think it's a good idea.
<clown> https://bugs.webkit.org/show_bug.cgi?id=138566
JS: There's an existing WebKit
bug (url above)
... So he's working on it, I guess.
... So we should monitor this bug until it's finished.
JD: I'll CC myself to that bug
and take a look when I get back home.
... If it's easy enough, I might as well do it myself, but I
need a Safari dev environment (which I have at home).
JS: I'll set the date to August 18.
<clown> action-1535?
<trackbot> action-1535 -- James Craig to Investigate the axapi mappings for aria-current. -- due 2014-11-25 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1535
JS: Looking at action-1535, AXAPI
mapping for aria-current. Again, I sent email to James but no
response so far.
... I'm not sure if there is a webkit but filed for this or
not. I'll look.
... There is one:
<clown> https://bugs.webkit.org/show_bug.cgi?id=146012
JS: So I'll add myself to the CC list. On the action I'll note this bug and move the due date to August.
<clown> action-1608?
<trackbot> action-1608 -- Cynthia Shelly to Bring up issue-708 with the html-a11y taskforce. -- due 2015-06-30 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1608
<clown> issue-708?
<trackbot> issue-708 -- The phrase "If not already excluded from the accessibility tree per the rules above" implies that the listed conditions do not override. Is that correct? -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/708
CS: Which relates to issue-708
right?
... I re-read the section and think the current text is
right.
... The text is strangely worded.
... Presentation removes it from the tree unless it's
focusable, etc.
... It's not adding stuff back; it's just exceptions.
JS: I responded to your comment
with another comment.
... Stating I agreed with you with respect to display:none and
visibility hidden and html5 hidden.
... But if it's focusable, etc. It should be exposed.
CS: And that's exactly what the
text says.
... Presentation is ignored in those cases.
... It's awkwardly worded.
... If you agree on my read on that....
JS: I'm not sure I do.
CS + JS: Agreement to work on the wording in the document, but not during the call.
JS: Let me think about it. I'll
take the action on.
... We'll close the action.
RESOLUTION: Close action-1608
JS: I'll add a comment.
<clown> ACTION: Joseph to propose new wording, as an editorial change only to clarify the inclusion rules in section 5.1.2 [recorded in http://www.w3.org/2015/07/14-aapi-minutes.html#action01]
<trackbot> Created ACTION-1681 - Propose new wording, as an editorial change only to clarify the inclusion rules in section 5.1.2 [on Joseph Scheuhammer - due 2015-07-21].
<clown> action-1681?
<trackbot> action-1681 -- Joseph Scheuhammer to Propose new wording, as an editorial change only to clarify the inclusion rules in section 5.1.2 -- due 2015-07-21 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1681
<clown> https://bugs.webkit.org/show_bug.cgi?id=146239
<clown> https://www.w3.org/Bugs/Public/show_bug.cgi?id=28816
JS: In the above issue, Jason
reported that certain roles lacked explicit role
mappings.
... Cynthia replied on the bug what should be done for UIA.
<clown> <p role="banner">
JS: Jason was okay with that, but
we've since found some issues.
... Given <p role="banner"> Firefox mapped it to
ROLE_PARAGRAPH, but then used xml-roles.
CS: In UIA, that would be mapped to group.
JS: For these roles, Firefox always uses the tag.
CS: UIA does not have roles for
document structures.
... The architecture of the APIs is different. Anything that is
not UI, we map to a generic group and then put the role string
in there so the screen reader will say it's a banner.
<clown> <button role="banner">
JS: I'm waiting on Alex and/or Joanie.
<clown> <div role="banner"> is mapped as ROLE_LANDMARK and xml-roles:banner.
<clown> <p role="banner"> is mapped as ROLE_PARAGRAPH and xml-roles:banner.
JD: I would think if a paragraph has a role indicating it's a landmark, it should be mapped as a landmark.
JS: States the mapping differences above.
CS: That is not how ARIA is supposed to work.
JD: I agree with Cynthia.
<clown> I wonder what FF does with <button role="banner">? Probably ROLE_BUTTON and xml-roles:banner.
JD: If the author says "this is a banner" then it's a banner; it's not a paragraph.
<clown> <p role="button"> ROLE_BUTTON.
JD: A paragraph that's a banner makes no sense (to me).
JS: If you have a paragraph with
role button, it's mapped as a button and the paragraph aspect
is lost.
... I've commented on the bug to ask Alex about this to find
out why the paragraph is not being mapped as a landmark in this
particular case.
... Jason has requested info from Alex, Joanie, and
Cynthia.
JD: I will comment.
CS: I think I commented already, right?
JS: Yes you (Cynthia) did.
<clown> https://www.w3.org/Bugs/Public/show_bug.cgi?id=28816#c7
JS: The above URL has my suggested wording.
<clown> - Expose as text string 'navigation' in AriaRole.
<clown> - Group control type with a localized control type based on the AriaRole.
<cyns> change "Group control type with a localized control type based on the AriaRole." to "Group control type with a localized control type of 'navigation'."
<clown> https://www.w3.org/Bugs/Public/show_bug.cgi?id=28816#c8
JS: Jason's latest comment has a list of a bunch more (above URL)
CS: The landmark role we did in Windows 10, they're in Edge.
JS: He's finding no mappings in UIA for article, form, note, and log.
CS: I think we did those in Windows 10.
JS: Could you comment on the bug?
CS: Yes. I'll do that.
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/spec./spec?/ Succeeded: s/Problably/Probably/ Succeeded: s/Window 10/Windows 10/ Found Scribe: joanie Inferring ScribeNick: joanie Present: Joseph_Scheuhammer Joanmarie_Diggs Bryan_Garaventa Cynthia_Shelly Regrets: Rich_Schwerdtfeger Found Date: 14 Jul 2015 Guessing minutes URL: http://www.w3.org/2015/07/14-aapi-minutes.html People with action items: joseph WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]