<Matt_King> i am here
<Jemma> https://github.com/w3c/aria-practices/wiki/December-10%2C-2019-Meeting
<scribe> scribe: carmacleod
<Jemma> https://pr-preview.s3.amazonaws.com/w3c/aria-practices/pull/1279.html#range_related_properties
mck: question: we don't have a section on every role that supports these properties. Do we need some?
siri: is aria-valuetext independent from aria-valuenow? Or do they go together?
<Jemma> I like the change in the table of aria-valuemin and aria-valuemax
<Jemma> now it is much easier to understand.
jamesn: there's an issue about that - joanie says we need aria-valuenow. screen readers can choose how they want to present the information.
mck: should we add html equivalents for the property descriptions?
carmacleod: I always like to tie in html if possible - I think it's always helpful
siri: how about for indeterminate progressbar - does it need valuenow? Or is just valuetext ok?
mck: I will do more edits here,
and add html column to the table
... I'll add subsections for meter and separator, and have
something ready for next week
<Jemma> https://pr-preview.s3.amazonaws.com/w3c/aria-practices/pull/1274.html#tabpanel
<Jemma> https://pr-preview.s3.amazonaws.com/w3c/aria-practices/pull/1274.html#tabpanel
<Jemma> https://github.com/w3c/aria-practices/pull/1274
mck: this is a simple change
jongund: basically 2 lines -
separated one bullet point from another, in the keyboard
subsection
... tablist used to be a separate paragraph - added to third
list item
<Jemma> this is the change Jon made, "When the first element contained within a <code>tabpanel</code> element is not focusable, it should set <code>tabindex="0"</code> to make it part of the tab sequence."
mck: we should probably not be
talking about tabindex="0" here because that belongs in the
focus section
... [reading] which is typically either the first focusable
element inside the tab panel or the tab panel itself.
... need to handle case where no element in the tabpanel is
focusable - then focus tabpanel itself
<Matt_King> My proposal for 2nd bullet: ◦ When the tab list contains the focus, moves focus to the next element in the page tab sequence outside the tablist, which is the tabpanel unless ...
jongund: I'll take another shot at it writing the 3rd bullet
<Matt_King> ◦ When the tab list contains the focus, moves focus to the next element in the page tab sequence outside the tablist, which is the tabpanel unless the first element containing meaningful content inside the tabpanel is focusable.
jongund: do people like "the first 'meaningful' element"?
https://github.com/w3c/aria-practices/pull/1120
<Jemma> "This PR doesn't seem like the right place for this change. If this isn't going into 1.2 anyway, it could perhaps wait until after we decide how to handle ES6+ syntax, or it could go in sooner using function prototypes instead of classes."
<Jemma> from Sarah
jongund: will change back to using prototype instead of class
<Jemma> https://github.com/w3c/aria-practices/pull/1276
mck: need to add the review
checkboxes
... would like to merge this first thing in January
https://github.com/w3c/aria-practices/projects/7#card-28909395
mck: what we need to know now is
how many of these issues are still valid
... need some help verifying some of these
... can someone look at this issue and decide if it's still
valid? https://github.com/w3c/aria-practices/issues/982
jemma: sarah is assigned to that
one.
... next one doesn't have anyone on it: https://github.com/w3c/aria-practices/issues/1263
<Jemma> https://github.com/w3c/aria-practices/projects/7#card-29202270 by Jon
jongund: https://github.com/w3c/aria-practices/issues/1265 should be fixed in pr 1276
mck: https://github.com/w3c/aria-practices/issues/569
should specify blur behavior
... I'll work on this
... https://github.com/w3c/aria-practices/issues/1267
we should test combo 1.2 with touch
siri: it doesn't work with Android
mck: Siri, please add your touch
results to Jon's PR (1276)
... would love to have some help sorting through this column.
Need to make combo 1.2 solid for the release.
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: Matt_King, carmacleod, Siri, Jemma, jongund, bryan_garaventa, jamesn Present: Matt_King carmacleod Siri Jemma jongund bryan_garaventa jamesn Regrets: mark_mccarthy sarah evan_yamanishi curt_bellew Found Scribe: carmacleod Inferring ScribeNick: carmacleod Agenda: https://github.com/w3c/aria-practices/wiki/December-10%2C-2019-Meeting WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: 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]