See also: IRC log
<clown> agenda: this
JS: Quick reminder that next week North America is on Daylight Saving Time.
<clown> action-2012
<trackbot> action-2012 -- Joseph Scheuhammer to UIA mapping for role="region" (Github issue #243) -- due 2016-02-12 -- PENDINGREVIEW
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2012
<clown> action-2013
<trackbot> action-2013 -- Joseph Scheuhammer to UIA mapping for role=navigation (GIthub issue #242) -- due 2016-02-12 -- PENDINGREVIEW
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2013
<clown> action-1667
<trackbot> action-1667 -- Joseph Scheuhammer to Update the mapping spec for aria role region to reflect its landmark inheritance as defined in the aria 1.1 spec. -- due 2016-02-26 -- PENDINGREVIEW
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/1667
<clown> action-2012
<trackbot> action-2012 -- Joseph Scheuhammer to UIA mapping for role="region" (Github issue #243) -- due 2016-02-12 -- PENDINGREVIEW
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2012
<clown> https://github.com/w3c/aria/pull/272
JS: Cynthia has this pull
request.
... URL above.
<clown> https://github.com/w3c/aria/commit/5b29b85d5d4ebee1b374bef2f887b8b6dd72cac9
JS: She makes changes to the various landmark roles for UIA.
CS: These are all similar.
... We added two new properties: landmark-type and
localized-landmark-type.
... The latter is a user-facing string.
... A number of the landmarks are not direct mappings, in which
case we use "custom" and then a localized landmark type string
for the specific name.
... For ARIA, the localized control type and localized landmark
type strings will always be the same.
... For HTML, the localized control type will be the same as
HTML, and the localized landmark type will be the ARIA
string.
... This is what the landmark is called (header versus banner,
for example).
... Adding the localized landmark type based on ARIA will make
them available in verbose mode.
... I did make some of the strings more user-friendly (e.g.
"contentinfo" to "content information")
<clown> http://rawgit.com/w3c/aria/uia-landmarks/core-aam/core-aam.html#role-map-banner
JS: The URL above has Cynthia's
changes.
... (reads from table)
CS: The fact that the landmark type is non null means Narrator will pick it up.
JS: Everyone ok with this?
(Group discusses the nature of the names of various landmark types)
<clown> https://github.com/w3c/aria/commit/8b9a91717b14a5e91f2ce6d576fcc182ef032aca
JS: The only problem I had is
that it changed the phrase "control type/role" to "Control
Type."
... I went through the document and made this change for the
rest of the Core AAM.
<richardschwerdtfeger> +1
CS: It looks fine.
JS: Then I will push all those
changes in and close the relative actions.
... And the github issues as well?
CS: Yes.
<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
<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
<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
<clown> http://rawgit.com/w3c/aria/ACTION-1569-%282%29/core-aam/core-aam.html#uia
JS: Here's the URL (above) with
the text.
... This is Jason's branch.
<clown> http://rawgit.com/w3c/aria/ACTION-1569-%282%29/core-aam/core-aam.html#uia
CS: It's in 1.3.2.
JS: Cynthia gave me new text for an example for treeitem control type for UIA.
CS: It's just an example to illustrate control types in UIA.
JS: I am just asking Cynthia if this is ok.
CS: I noticed one nit, namely that tree items are not actually sentient.
RS: But a tree item is not always expandable.
CS: It is in UIA.
RS + JS: What are the leaves called?
CS: I believe they are still tree
items, but they might be links or buttons.
... The purpose of this example is to explain what is required
versus optional, and what control patterns are.
... For instance a tree item must be expandable, it might or
might not also be scrollable.
... If this example is confusing, I could come up with a
different one.
... Or we could just say this is good enough for now.
JS: I think it's good enough for now, but Rich seems to have concerns.
CS: The goal of the example is to
show how control patterns can be mixed together.
... Does it address that goal?
BG: Does leaf node count for checkable item state?
CS: A tree item could have
children that are, among other things, checkable.
... You can add any pattern to any item.
... But by default, expand/collapse is the only required
pattern for tree item.
JS: Jason Kiss is the one who
suggested these sections be added.
... Rich, do you have a better example?
RS: What about a slider?
CS: I don't think that's a
control type, but a pattern (range).
... There is a slider control type.
... But it doesn't have a required control type.
... Which is why I didn't pick it for this example.
RS: Scrollbar?
CS: Has no required patterns.
RS: It's not required to scroll?
CS: I could use radio button, but
radio button is not allowed to have the toggle pattern.
... (Reviews other controls for better example, and finds no
better option.)
RS: Any reason why we don't use the 'code' tag in this text for the UIA tree item control type?
CS: Probably a good idea that we do that.
JS: This text is on Jason Kiss's branch, by the way.
CS: Suggestion: Go ahead and commit this and then give me a new issue or action to fix the rest (e.g. 'code' tags)
JS: It's showing up in the spec now, but it's in a branch.
<clown> https://github.com/w3c/aria/pull/279
JS: There's a pull request from
Jason (above).
... And he's still working on it, so I'm not ready to commit it
to master.
... If you go to that URL, you'll see I added some things.
CS: So I would need to make changes to Jason's branch?
JS: Yes.
(Action reassigned to Cynthia with note to make edititorial changes discussed)
<clown> https://www.w3.org/WAI/ARIA/track/actions/2032
JS: Note added to
action-2032.
... You might want to email Jason to tell him you're working on
his branch.
<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 don't think I have any new
information.
... Before last week's meeting, I posed a question in WebKit's
bugzilla.
<clown> https://bugs.webkit.org/show_bug.cgi?id=138566#c23
JS: And I haven't gotten an answer.
JD: Did you try what I
suggested?
... Assign this to me to try what I am suggesting you do. I
have a current trunk build of Safari.
<clown> ACTION: Joanie to run the webkit aria-modal test file to see what happens vis-a-vis the background. [recorded in http://www.w3.org/2016/03/08-aapi-minutes.html#action01]
<trackbot> Created ACTION-2038 - Run the webkit aria-modal test file to see what happens vis-a-vis the background. [on Joanmarie Diggs - due 2016-03-15].
<clown> action-2038
<trackbot> action-2038 -- Joanmarie Diggs to Run the webkit aria-modal test file to see what happens vis-a-vis the background. -- due 2016-03-15 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2038
<clown> action-2008?
<trackbot> action-2008 -- Joseph Scheuhammer to Handle concept of description property for UIA -- due 2016-03-01 -- PENDINGREVIEW
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2008
JS: I just saw this come in
today.
... (Reads from comment)
We are adding a UIA property called "FullDescription" in addition to the existing "Name" and "HelpText" properties and "LabeledBy" and "DescribedBy" relationships It is not yet in public builds. I will update UIA mappings to include it.
JS: And you assigned this to me.
CS: Because it was due today.
JS: So I'll assign it back to you
and re-set the status to open.
... And once you've made the edits, reassign it back to me.
action-2036
<trackbot> action-2036 -- Richard Schwerdtfeger to Modify aria-kbdshortcut based on group feedback -- due 2016-03-06 -- OPEN
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2036
CS: I looked at what's available
in UIA.
... My notes are in action-1635
action-1635
<trackbot> Sorry, but action-1695 does not exist.
<richardschwerdtfeger> https://rawgit.com/w3c/aria/action2036/aria/aria.html#aria-keyshortcuts
<cyns> https://www.w3.org/WAI/ARIA/track/actions/1695
CS: UIA has a couple of things in
the ballpark, but neither are an exact match.
... Accelerator key are typically Ctrl (e.g. Ctrl+S to
save)
... Access keys (also called mnemonics) are the things where
the underline shows up when you hold down the Alt key.
RS: Mnemonics typically give focus to something, but not activate them.
CS: That's not the case in menus, which is where they are frequently used.
RS: Accelerators always invoke.
CS: Yes.
... I think Accelerator key is closer, but it does
invoke.
... And there was some discussion about whether invoking was
required or optional.
RS: Our aria-kbdshortcuts is for
documentation.
... But it won't give it focus.
CS: The way that it seems to work
in UIA is that if it's put on something invokable, it invokes;
otherwise it gives is focus.
... I'm not sure if exposing aria-kbdshortcuts in this fashion
is going to cause a change in user interaction.
RS: So when it's exposed in your API....
CS: I think that wires it up to
be invoked.
... In the case of a link, it should invoke; in the case of a
text field, it should focus.
RS: That's ok because it's essentially a click.
CS: Yes, invoke is click.
RS: If you click on a text field,
it's going to focus.
... So I think that's ok.
CS: Either one is fine, if we
want to scope it tightly for 1.1.
... On a set that's larger, I think I can do that too.
... My concern is that if we do so, Windows is going to start
doing things.
RS: I'm a little worried about it because if you do the invoke, it would happen under the covers.
CS: UIA is a two-way API; ARIA is a one-way API. It's a mismatch.
JD: I am pretty sure the spec
specifically states that no action is supposed to occur as a
result of the exposure.
... And that the author is required to do all the
user-interaction implementation.
... It's just notifying ATs of the existence of this
property.
CS: I may be able to do this on
my platform, but I'm not yet sure.
... I'll dig a bit more and see if these things can be
separated.
<scribe> scribenick: joanie
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/Dayligh/Daylight/ Succeeded: s/expandible/expandable/ Succeeded: s/action-1635/action-1695/ Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Found ScribeNick: joanie Inferring Scribes: joanie Default Present: Joanmarie_Diggs, Bryan_Garaventa, Joseph_Scheuhammer, Cynthia_Shelly, Rich_Schwerdtfeger Present: Joanmarie_Diggs Bryan_Garaventa Joseph_Scheuhammer Cynthia_Shelly Rich_Schwerdtfeger Found Date: 08 Mar 2016 Guessing minutes URL: http://www.w3.org/2016/03/08-aapi-minutes.html People with action items: joanie WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]