W3C

- DRAFT -

ARIA APG TF

08 Oct 2018

Agenda

Attendees

Present
jongund, MarkMcCarthy, CurtBellew, jamesn, AnnAbbott, JaeunJemmaku, siri, jemma
Regrets
Chair
MattKing
Scribe
CurtBellew

Contents


Issue Triage

<mck> make log world

New issue triage

<AnnAbbott> mck: apply A label indicating issue type: bug, enhancement, editorial, documentation

<AnnAbbott> mck: apply A label indicating part of APG: code example, pattern, guidance

<AnnAbbott> mck:: apply A milestone indicating our target resolution date

<AnnAbbott> mck: If related to a pattern or code example, it is assigned to a project.

<mck> Link to unlabeled issues that need triage: https://github.com/w3c/aria-practices/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+no%3Alabel

<AnnAbbott> JN will handle #923

yes

you were visible.

<AnnAbbott> jg: will take #917

<siri> no

new toolbar

<mck> Example page: https://rawgit.com/jongund/aria-practices/toolbar/examples/toolbar/toolbar.html

mck: Goal of the issue is to have multiple kinds of elements inside the toolbar
... Some screen readers would assume that only buttons would be in a toolbar. ARIA doesn't have that restriction

<AnnAbbott> test

<AnnAbbott> THX!!!

mck: with JAWS arrowing through the toolbar would pop out of forms mode at times

jg: Never seen a checkbox in a toolbar. Not sure how to style them.
... Is this actually a toggle button that is read as a checkbox by JAWS

<AnnAbbott> mck: would be good to add spinbutton

JamesN: Maybe add a spinbutton instead.

mck: Spinbutton for the font size in particular.
... We could have a spinbutton without an edit box but we do need an example without an edit box.

<AnnAbbott> jn: could have conflict with arrow keys

Correction - mck: We could have a spinbutton with an edit box but we do need an example without an edit box.

<AnnAbbott> jg: use spinbutton for font size

<AnnAbbott> jg: still want example with link?

<AnnAbbott> mck: want to make sure it is supported to have links

jg: our examples can help us encourage what we want authored.

<AnnAbbott> jg: is there a compelling example to use links in toolbar?

jg: Do we want links in a toolbar?

<AnnAbbott> jg: CKEditor has lots of aria bugs

jg: We can add a 'help' link that goes to an empty page...

mck: If it's something we want to discourage then let's not put links in the toolbar. Is there a use case?

<jemma> I think we should keep scope for each example

jg: The help link is the only link I could think of.

<jemma> we can not expand this example forever.

mck: If no one can come up with an example of people wanting to put links in toolbars then we can exclude it from the example.

jn: All the links I see are styled as buttons.

<jemma> https://www.w3.org/TR/wai-aria-practices-1.1/#toolbar

jn: If it looks like a button for a visual user then it should read as a button for a screen reader user.

mck: If it's going to a different page or a different part of the page use a link.

<MarkMcCarthy> I agree. Better to be consistent

ann: Stick with the rule. Doesn't matter what it looks like. ONly what it does.

mck: We will add a spinbutton to the toolbar but no link.

<jamesn> for those that can see it here is a toolbar with a whole bunch of components https://i.imgur.com/nXuoWUb.png

<MarkMcCarthy> That's a good example James

mck: do we support grouping in toolbars

<jamesn> this has a bunch of menu buttons, select lists, button groups (radio) , checkboxes etc.

<jemma> yeah. it has everything. ;-)

<jemma> "A toolbar is a container for grouping a set of controls, such as buttons, menubuttons, or checkboxes."

jn: It looks like a checkbox is a real use case.
... High contrast mode or something like that? Dark mode?

jg: I'll work on adding the spinbutton and checkbox this week
... let me know the consensus on the link

Future meetings and other business

<AnnAbbott> October 22 and 29: No meetings due to 2018 W3C TPAC

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: 2018/10/08 18:00:19 $

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: jongund MarkMcCarthy CurtBellew jamesn AnnAbbott JaeunJemmaku siri jemma
No ScribeNick specified.  Guessing ScribeNick: CurtBellew
Inferring Scribes: CurtBellew
Agenda: https://github.com/w3c/aria-practices/wiki/October-8%2C-2018-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]