W3C

- DRAFT -

May 7, 2019 ARIA Authoring Practices Task Force Telecon

07 May 2019

Agenda

Attendees

Present
mck, AnnAbbott, EricE, evan, jongund, zcorpan, siri, dbass2, Matt-King, CurtBellew, MarkMcCarthy, JemmaJaeunKu, carmacleod, jamesn, BryanG
Regrets
StefanS, EvanY
Chair
Matt King
Scribe
AnnAbbott, Ann

Contents


<AnnAbbott> Scribe: AnnAbbott

<jemma> Scribe: Ann

<jemma> https://github.com/w3c/aria-practices/wiki/May-7%2C-2019-Meeting

Review carousel feedback

<Zakim> jamesn, you wanted to say maybe introductions?

Round of introductions

mck: put out carousel in Jan as simplest example

<MarkMcCarthy> https://github.com/w3c/aria-practices/issues/971

mck: : Pause Stop always visible is in Jon's PR

Jon's PR is Issue #1007: https://github.com/w3c/aria-practices/issues/1007

<jemma> https://www.w3.org/TR/2019/NOTE-wai-aria-practices-1.1-20190207/examples/carousel/carousel-1/carousel-1.html

jg: this is the old one, not newest

https://raw.githack.com/w3c/aria-practices/issue1007-visible-pause-carousel/examples/carousel/carousel-1/carousel-1.html

<jongund> https://raw.githack.com/w3c/aria-practices/issue1007-visible-pause-carousel/examples/carousel/carousel-1/carousel-1.html

<jamesn> +1 to color contrast issues with the buttons when not focused

jg: higher contrast on buttons on hover
... has other carousel examples that can be included

jn: this example does fail WCAG 2.1

mck; if fails WCAG 2.1, we shouldn't include

jn: remove buttons from image (exist outside image)
... don't show buttons unless focus goes to area?

siri: wants controls shown or users don't know it is a carousel

<Jesse_Hausler> Jemma, https://www.lightningdesignsystem.com/components/carousel/

mck: to pass WCAG 2.1 proposal, what are the options?

jn: buttons exist out of image or contrast passes

Jesse: our example is tab based - buttons are off image
... pause button is disabled when focus moves into carousel and on hover

mck: buttons outside image and persistent is preferable

jn: contrast must be 3:1

<Jesse_Hausler> Text on backgrounds guidelines, https://www.lightningdesignsystem.com/accessibility/guidelines/text-on-backgrounds/

Jesse: sharing link

mck: buttons outside image seems better

jg: buttons currently are not opaque

mck: move all buttons outside image

<Sarah> I just mentioned eye control and dragon/voice control as cases that might have issues with buttons hidden behind hover/focus states

mck: second choice is to make button contrast compliant

<Sarah> James kind of mentioned this already, but are dual-tone buttons (e.g. a black circle with a white arrow) in consideration?

Carolyn: buttons could pass contrast if they had 3 pixel border

<jamesn> +1

<jemma> +1

<MarkMcCarthy> +1

<jemma> easy fix

<CurtBellew> +1

<jamesn> (I wasn't aware of a 3px requirement)

Update on date picker

jg: not in state to discuss - making changes

Disclosure-based site navigation

<siri> Iam also not aware of it, please send me the link if you find any :)

https://github.com/w3c/aria-practices/issues/1028

mck: don't have enough examples to replace menubar for site navigation
... buttons with aria-expanded
... to make another version of site navigation example

<jongund> https://aitg.disability.illinois.edu/courses/widgets/slide30.html

mck: links follow button in tab order
... instead of having links load dummy page, reload same page with new content

Jesse: disclosures next to each other are considered an accordion

mck: accordion always has header
... there is no accordion role
... goal is to have this be as lite-weight as possible (bare bones)
... accordion pattern contains things that just feel like noise for this example
... Volunteers?

jg: would be happy to help someone who volunteers
... only one remains open at a time, correct?

mck: no mouse behaviors included in requirements

<jemma> https://www.usa.gov/

mck: shouldn't do anything automatically
... except close prior menu of links

<Sarah> I don't think my mic is working anymore -- I've been trying to say that I can make it if you're looking for someone

jg: lots of variations on this pattern

<jemma> Thanks, Sarah!

mck: Carolyn did a boatload of work on mouse behavior

Carolyn: will be happy to include

mck: longterm goal is to have multiple examples with documented differences

<jemma> carolyn, do you have an open issue in git?

Future meetings and other business

next meeting: May 14, 2019

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/05/07 18:57:50 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Present: mck AnnAbbott EricE evan jongund zcorpan siri dbass2 Matt-King CurtBellew MarkMcCarthy JemmaJaeunKu carmacleod jamesn BryanG
Regrets: StefanS EvanY
Found Scribe: AnnAbbott
Inferring ScribeNick: AnnAbbott
Found Scribe: Ann
Scribes: AnnAbbott, Ann
Agenda: https://github.com/w3c/aria-practices/wiki/May-7%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: 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]