W3C

- DRAFT -

ARIA Authoring Practices Task Force Telecon

21 Apr 2020

Agenda

Attendees

Present
MarkMccarthy, jongund, carmacleod, mck, Jemma, james, curt
Regrets
ZoeBijl, SarahHigley
Chair
Matt King
Scribe
Jemma

Contents


<mck> agenda: https://github.com/w3c/aria-practices/wiki/April-21%2C-2020-Meeting

<scribe> scribe: Jemma

new agenda reqeust

no new agenda

Tabbed carousel

car: changed some of wording

https://github.com/w3c/aria-practices/pull/1120#discussion_r412359403

mck: by default page load, do we want to load captions out of images?

jongund: I disagree

if Jon thinks that the design is not what that they want and it will not be used because of that, that is valid concern.

mck: Decision: Right now defaulting showing the caption and allow users to change their preference.

James: I like the way it is and let's ship it.

car: (Going through edited text..)

Jon: preferred reduced motion was added to css by Sarah

mck: your os setting will determine when the second check box is checked.

car: I will add those system setting info regarding reduced motion initialization..

jon: I will check the code for initializaiton.

car: Sarah just wanted to make sure that we followed the implementation what we talked last week.

Third checkbox: Auto-rotation is disabled.

sri: aria described by content is too long

mck: aria described by is pretty normal for providing further info.
... length itself is not the concern.

aria descrbed by information is "This option improves accessibility for users with visual impairments and people who are distracted or confused by auto-rotation by disabling the auto-rotation feature and removing the start/stop button from the user interface. Users can use the tablist to manually navigate through the slides."

car: how about redoing visual review since we have some changes?
... in particular to focus styling - dotted line around focus.

jongund: we can do solid line if we want to.

<carmacleod> Coming soon in Chrome/Edge: https://blog.chromium.org/2020/03/updates-to-form-controls-and-focus.html

mark: I will finish the visual and accessiblity review for carousel

Combobox example

<carmacleod> github: https://github.com/w3c/aria-practices/issues/1375

mck: so we can put aria hidden on tabbable image?

jongund: to open popup like click in mobile we coded mouse up and down event

<carmacleod> https://w3c.github.io/aria-practices/examples/combobox/combobox-autocomplete-list.html

mck: screen reader users hear state combobox and state button "collapsed" next things. The questions is whether state button creates the distraction. what would be better for users - it is button or image part of the combobox? The issue could be something visual enhancement of combo box.
... This is extended to mobile touch issues.(This is why we talk about touch, click, or mouse up above)

james: more complexity we add, there is more chance to mess up. Screen reader foucs is more desirable that hiding it.

<MarkMccarthy> jamesn has convinced me

+1 for james

mck: in this case, drop down icon is truly redundant

james: focus and double tap the field will open the field.

it is like that of date picker example

mck: we will still use aria states - expanded and collasped.
... consensus is we want editable comobo box and both elements will be accessibile - input and button.

menubar final check in

PR 1356 - update menubar editor js/high contrast

PR 1359 - update menubar navigation js/high contrast

https://github.com/w3c/aria-practices/pull/1356

mck: both are ready to go in terms of editorial perspective.

car: not sure about that
... menubar does not look menubar anymore.

<siri> +1 for Jon

jon: arrow and grouping indicate design affordance.

<MarkMccarthy> +1 jongund

car: menu selection does not selected background like that of chrome menu selection
... outline and change background for selected menuitem

<MarkMccarthy> MarkMccarthy: or Windows' File Explorer menubar / ribbon might be a good example to look at too

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: 2020/04/21 19:09:11 $

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)

Succeeded: s/those info/ those system setting info regarding reduced motion initialization./
Succeeded: s/length/length itself/
Succeeded: s/nomal/normal/
Succeeded: s/backgound/background/
Present: MarkMccarthy jongund carmacleod mck Jemma james curt
Regrets: ZoeBijl SarahHigley
Found Scribe: Jemma
Inferring ScribeNick: Jemma
Agenda: https://github.com/w3c/aria-practices/wiki/April-21%2C-2020-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]