W3C

ARIA APG TF

05 Oct 2015

See also: IRC log

Attendees

Present
Matt_King, JamesNurthen, JemmaJaEunKu, Raghu, Michiel_Bijl, IanPouncey, Ann_Abbott, Bryan_Garaventa
Regrets
Jon_Gunderson
Chair
Matt_King
Scribe
annabbott, Ann_Abbott, MichielBijl

Contents


<jamesn> scribe: annabbott

<scribe> scribe: Ann_Abbott

Pattern work status page update https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status

Matt: discuss where we are with example development

Michiel: remove or remark all example code except Alert

James made the edit

Matt: first column needs tabpanel & treeview as Reviewed

Jemma finished checkbox (3 examples) and Jon will review for next week, then move on to radio button

Jemma will review tri-state checkbox with Jon

Jemma: Jon will review tri-state checkbox

Matt: any other table updates needed?

crickets

Landmark navigation pattern review https://rawgit.com/w3c/aria/master/practices/aria-practices.html#landmarks

Ian will draft coding practices

Toolbar pattern review https://rawgit.com/w3c/aria/master/practices/aria-practices.html#toolbar

Matt: next week add to agenda coding practices for examples

Michiel: I'd by HAPPY for you to take over as scribe!

<MichielBijl> scribe: MichielBijl

<annabbott> MILLION THANKS!

Matt: in terms of expectation, Jemma, do you think your checkbox example will be ready next week?

jemmaku: yes

Matt: is the description to desktop-land orientated?

A collection of commonly used function buttons or controls represented in compact visual form.

The toolbar is often a subset of functions found in a menubar, designed to reduce user effort in using these functions. Authors must supply a label on each toolbar when the application contains more than one toolbar.

Authors may manage focus of descendants for all instances of this role, as described in Managing Focus.

jamesn: some problems with toolbars
... people want to put more than buttons in toolbars; like textfields or dropdowns
... how does this work with keyboard interaction; left and right arrows in a textbox behave different than in the toolbar itself

Matt: is there a restriction on the content of a toolbar?

jamesn: no

Matt: does it make sense to have it in the toolbar?

jamesn: the UI designer want's to put it there

bgaraventa1979: then it's not a toolbar
... AT will announce the number of buttons in a toolbar
... putting in other stuff will mess up the count

jamesn: isn't that a AT problem?

yes

Matt: it could be grouped in a grid (toolbar and other stuff like search fields)

jamesn: I'm very much against that

bgaraventa1979: you could use a region; you have quick navigation

jamesn: the problem is that you then get inefficient keyboard navigation

bgaraventa1979 this is what you meant right: http://codepen.io/Michiel/pen/ZbKbLo.html

<jemmaku> +question

+question

IanPouncey: problem with aria is recognising how to use it. Mixing input methods makes it harder.

Matt: that is why I advocate that people don't put stuff inside a toolbar that capture arrow keys.

http://codepen.io/Michiel/pen/ZbKbLo.html

http://codepen.io/Michiel/pen/ZbKbLo

http://s.codepen.io/Michiel/debug/ZbKbLo

Matt: so if we are going to advocate this as a best practise, then I guess, this would require a complete rewrite of the description in APG.
... we could take the first line from the ARIA spec and extend that.
... would a spinbutton be something you would find in a toolbar?

jamesn: for stuff like font-size, indent-size, etc

Matt: could you use a dropdown in a toolbar?

jamesn: as long as you use a pure selectbox (so no combobox)
... I'll add a bug for toolbar

Matt: I don't mind writing toolbar

<jemmaku> so do we use div role region for tool bar?

Uhm, yeah that is what is there, but I'd have to have it checked more thoroughly.

I think Matt just gave it a quick once over

<jemmaku> ok

<jemmaku> thanks.

But that was what Bryan suggested during the call :)

<jemmaku> yeah

<jemmaku> I think it is a good idea.

<jemmaku> Thanks for scribing today

<jemmaku> I will talk to you later

Allows for quick access via keyboard

No problem! Was that the question you wanted to ask when you entered the que?

<jemmaku> it was about region role for toolbar

Yeah okay :)

<jemmaku> we can have sevral regions. right?

Yes

<jemmaku> multiple regions

Yep, you can have multiple; probably should limit it though

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/10/05 18:08:33 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

Found Scribe: annabbott
Inferring ScribeNick: annabbott
Found Scribe: Ann_Abbott
Found Scribe: MichielBijl
Inferring ScribeNick: MichielBijl
Scribes: annabbott, Ann_Abbott, MichielBijl
ScribeNicks: annabbott, MichielBijl

WARNING: Replacing previous Present list. (Old list: James_Nurthen, Bryan_Garaventa, Matt_King, JamesNurthen, AnnAbbott, JemmaJaEunKu, Raghu, Michiel_Bijl, IanPouncey, Ann_Abbott, matt_king)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ James_Nurthen, Bryan_Garaventa, Matt_King, JamesNurthen, AnnAbbott, JemmaJaEunKu, Raghu, Michiel_Bijl, IanPouncey, Ann_Abbott

Present: Matt_King JamesNurthen JemmaJaEunKu Raghu Michiel_Bijl IanPouncey Ann_Abbott Bryan_Garaventa
Regrets: Jon_Gunderson
Got date from IRC log name: 05 Oct 2015
Guessing minutes URL: http://www.w3.org/2015/10/05-aria-apg-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]