<sarah_higley> thanks Jemma! I can't wait to read through those closely
<Matt_King> agenda link: https://github.com/w3c/aria-practices/wiki/October-29%2C-2019-Meeting
<Jemma_> Scribe: Jemma
<Jemma_> All the reviews are done so it is ready to be merged.
<Jemma_> there is mapping issue so we would not do this for this milestone.
<jamesn> https://github.com/w3c/core-aam/issues/53
<Jemma_> https://github.com/w3c/aria-practices/issues/913
<jamesn> although that issue doesn't have mozilla's comments in it
<jamesn> (core-aam 53 , I am looking for their comments
<Matt_King> https://github.com/w3c/aria-practices/pull/1191
<Jemma_> https://github.com/w3c/aria-practices/pull/1191
<carmacleod> Scribe: carmacleod
mck: editorial reviews complete
<Jemma_> I will be back in a second after restarting the computer;
mck: visual design review. Zoe made changes. Was it just to appearance, or css?
<jamesn> colindextext and rowindex text ARIA issue is being tracked in https://github.com/w3c/aria/issues/1102
zoe: both. changed css selectors, layout, and made it ook a bit more modern
mck: creating a raw githack preview...
<Matt_King> https://raw.githack.com/w3c/aria-practices/913-listbox-groups/aria-practices.html
<sarah_higley> https://raw.githack.com/w3c/aria-practices/913-listbox-groups/examples/listbox/listbox-grouped.html
zoe: gave the group box rounded corners, would like to make list items same height
jamesn: single select listbox example 1, if I arrow up and down it moves from unimportant to important features
sarah: separate issue
jamesn: they should be consistent
zoe: agree
sarah: test review isn't checked
but valerie says she did test review, so I'll check it
... only thing missing is a11y review
zoe: I'll do that
<ZoeBijl> Here's the CSS: https://github.com/w3c/aria-practices/pull/1191/files#diff-eaa3af5513d88dc21af506feb5525800
zoe: would be interested to hear people's thoughts on the readability of the css, so maybe can use as a basis for the guidelines
sarah: should we do the css review in a separate issue?
zoe: good point, and I'll link to this issue
<Jemma> this is local css for listbox only.
<ZoeBijl> Code readability issue: https://github.com/w3c/aria-practices/issues/1180
mck: the only other thing in this milestone is changing 1.1 to 1.2
<Jemma> https://github.com/w3c/aria-practices/issues/1225
github: https://github.com/w3c/aria-practices/pull/1120
<ZoeBijl> https://cdpn.io/Moiety/debug/30408bfbd4f8168d4b1d5520f7699353
<ZoeBijl> https://codepen.io/Moiety/pen/30408bfbd4f8168d4b1d5520f7699353
zoe: this is not done yet - it is just me coming up with something that looks good
<Jemma> I have a concern for scope creep of tabbed carousel example.
zoe: it has all of the required
bits that are in the original carousel, it's accessible, and
looks more more modern
... would like to add tooltips to the buttons because they are
currently just icons. up to changing to just text, but I prefer
icons
<Jemma> we have been discussed tabbed carousel example since March 2017
mck: the history on this is that there are carousels in the wild that are not accessible
<sarah_higley> 😂
zoe: don't see the need for 2 separate designs
carmacleod: why does the fushia bar span tabs 1 and 2?
zoe: the bar grows with progress
<Jemma> mck: we need to indicate that which one is the current selection
jamesn: every carousel in the wild is removing stuff, but we are adding more
<Jemma> +1 Jamesn
mck: need to indicate which tab is currently selected
zoe: you could remove the tab stuff and the progress bar and only have the next/play/previous buttons - there are options to make it more minimalistic
<Jemma> jemma: I think it would be ok if we remove red progress bar and indicate the current selection from Zoe's example. Still my biggest concern is that we are starting brand new accessible again.
zoe: I get what you are saying, james, but many real life carousels are not accessible
sarah: I like the look - the extra chrome is ok - had questions about the fushia bar as well
mck: who can do functional testing?
carmacleod: I can
github: https://github.com/w3c/aria-practices/pull/1231
<Jemma> https://github.com/w3c/aria-practices/issues/1212
mck: part of me is wondering whether we should discourage accessible label on these
sarah: I agree that it's not a good pattern. Can we say that you can't name them?
<sarah_higley> ^ sorry, I was unclear. I meant "can we say you can't use aria-label on them?"
mck: we don't think there's value
labelling it unless there's a visible label (for blockquote and
time)
... trying to imagine real world examples of time - labelling
it is probably just going to cause screen reader problems
... blockquote - if there's a visible label, that would work ok
in screen readers
jamesn: I don't like the word "discretionary" in the table - it sounds to "positive"
mck: used to have "Sometimes", "Never", "Occasionally", but that didn't work too well
jamesn: Ok, let's not worry about the word.
mck: we can discourage it in the comments if it's "Discretionary"
<Jemma> I think we need to provide more strong guidance rather than discretion.
mck: currently 108 issues in milestone - need to triage it down to top 15 or so
sarah: I'm happy to help weed out the low-hanging fruit
<sarah_higley> sorry, I have to drop now. I'll check the minutes later for the tag name. Thanks everyone!
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) Succeeded: s/new example/brand new accessible/ Succeeded: s/need/need to provide/ Default Present: Matt_King, sarah_higley, evan, ZoeBijl, carmacleod, CurtBellew Present: Matt_King sarah_higley evan ZoeBijl carmacleod CurtBellew Found Scribe: Jemma Found Scribe: carmacleod Inferring ScribeNick: carmacleod Scribes: Jemma, carmacleod 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]