<jongund> Welcome Valarie!
<scribe> scribe: matt king
mc: acccname published on tuesday as cr
will be in cr for month
we already have all test data
graphics-amm published on tuesday and have transition request to pr in director's hands.
hoping to publish as pr on tuesday.
upcoming first pwd of 1.2 aria, core-aam, and apg
jn: goal to get dne as soon as possible. might not make it before matorium
Need to hit dates for the charter.
Mjn: want to have everything ready before july 2 so can be published after july 13
<jamesn> https://www.w3.org/WAI/ARIA/wiki/Meetings/TPAC_2018
jn: People can ideas for topics to that meeting page.
so we can work out how to plan the agenda.
registration is open.
link is in wiki page for agenda.
early registration is before july 31.
gets more expensive after that.
Invited experts can qualify for some funding, details on registration page.
There is alos a diversity fund available.
<MichaelC> https://www.w3.org/blog/2018/06/diversity-at-w3c-launch-of-tpac-diversity-scholarship/
mc: there is a blog post about diversity fund.
Dealdline is july 15.
No new issues in the last week.
Issue 777
<jamesn> https://github.com/w3c/aria/issues/777
jn: Dominic logged tis. not clear what to do about case sensativity
we don't have anything in spec that deals with it.
jn: about casensativity of values, e.g., true/false/etc.
webkit and blink do case sensitive comparisons, firefox is insensitive.
jn: aria in html doc says ther canse sensitive.; says they must lower case.
mk: Shall we add to state and property processing.
jn: seems like the place to do
it.
... Marco says that all html attributes are case
insensitive
in his firefox blog.
<jamesn> https://bugzilla.mozilla.org/show_bug.cgi?id=1407167
jg: I agree that we should do what html does; make case insensitive.
bg: when does it need to be done
jn: in 1.2 time frame
bg: I can commit if not urgent
jn: I will assign to you.
<jamesn> https://github.com/w3c/aria/issues/778
<jamesn> In ARIA 1.1, we added the requirement that authors MUST name their regions. Then, in the Core AAM, we added conditional mappings: Expose as a landmark if it has an explicit name; don't expose as a landmark if it lacks a name.
<jamesn> It has been suggested that we do something similar for the form role. See #514). This issue was closed and moved to Core-AAM for the conditional mappings (w3c/core-aam#11). However, we cannot take steps on that Core-AAM issue until we decide what to do in the ARIA spec itself.
jn: This issue suggest we treat nameless form elements like nameless sections and nameless regions.
mk: Strongly agree we should do this
jn: me too
mk: I will take this one.
jn: any disagree with the proposal?
jg: I support it.
<jamesn> https://github.com/w3c/aria/issues/742
<jamesn> role="searchbox" is mentioned once in the text as an element that role="combobox" must contain or own. Further text only mentions textbox. The characteristics table below the text does not mention searchbox, only textbox.
<jamesn> https://www.irccloud.com/pastebin/PDQyYkg2/
<jamesn> It seems that it should either be clarified that searchbox is also an appropriate role, which sounds plausible because it is a subclass role of textbox.
<jamesn> Or if that is not the case, remove the mention of searchbox.
The searchbox role is mentioned once but the text is not consistent and the table is not either.
<jamesn> https://www.w3.org/TR/wai-aria-1.1/#combobox
do we want to support searchbox as a combo input?
mk: I am OK with trying it. Not sure what AT will do with it.
jn: This is an editorial change
I'm not aware of AT treating a searchbox different frm a combo. doubt would cause a problem.
mk: I'm aware of differences.
jn: html type search is rendered diff from html type text
by some browsers.
not sure it would impact AT
mk: the motivation behind having
searchbox cold be alignment with native mobile AX apis.
... willing to take this issue
jn: that's end of planned agenda. We could go through more issues or we can end early.
<jemma> Thanks
presetnt+ valerie_young
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Present: jamesn MichaelC jongund jemma matt_king bryan Regrets: Melanie Joanie No ScribeNick specified. Guessing ScribeNick: mck Found Scribe: matt king Found Date: 21 Jun 2018 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]