W3C

- DRAFT -

SV_MEETING_TITLE

30 Nov 2015

See also: IRC log

Attendees

Present
JamesNurthen, AnnAbbott, jemma_jaeun_Ku, Michiel_Bijl, Bryan_Garaventa
Regrets
Léonie_Watson
Chair
Matt_King
Scribe
MichielBijl

Contents


<jemma_ku> hi

<jemma_ku> can I get meeting pw?

<jemma_ku> I understand and it is easy pw

<mck> test

<scribe> scribe: MichielBijl

Update pattern work assignments and status https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status

MK: Have edited the first column of the status table
... dialog modal isn't quite ready
... put Jon's name in the edit column for landmarks
... those are the changes that have been made recently
... any takers for menu/menubutton?

JG: me and Jemma can take that

AA: I can help with landmarks.

JN: Jon and Jemma, you still have radio/checkbox group to do.

MK: agenda item for larger topic
... where do we put stuff in the guide related to non interactive widgets
... there may be design patterns like landmarks, but not have them limited to interactive role
... or have a separate section for them
... do you want us to look at your example content first Jon?
... did you do some writing at that link?

JG: started to write some stuff. But looked at overall structure. Need to talk about.
... right now there is a landmark section
... I think we should have a section for non-interactive widgets.
... we have a lot of them: map, list, etc
... help developers find them easier

MK: do we want an index section of the document?
... if we have that in our guide, it would be easier for people who are using it to use it as a reference
... why would you separate interactive and non-interactive, what about cases where it's not clear?

JG: have a section for landmark roles
... me and Ann will propose a solution/example and we'll take it from there

<annabbott> Jon & Ann: landmarks on Dec 14 agenda

Review bug fixes for menu and menubar pattern https://rawgit.com/w3c/aria/apg_menuPattern/practices/aria-practices.html

MK: I'll merge after the call

https://rawgit.com/w3c/aria/apg_menuPattern/practices/aria-practices.html#menu

<jemma_ku> https://rawgit.com/w3c/aria/apg_menuPattern/practices/aria-practices.html#h-menu

MK: removed references to desktop applications

https://github.com/w3c/aria/compare/apg_menuPattern

MK: made keyboard section shorter and added notes to clarify

JN: don't want to add links to everything

AA: remove the link on menu button?

JN: no, links to separate section

MK: interested to know if the keyboard section is an improvement
... the other thing I tried to do is be consistent if we talk about keys

JN: would you tab to a container?
... why not?
... you would tab to it.

MK: you would tab to an element that activates a menu
... if you put on menubar you could tab to a container

JN: I have a question about up/down arrow
... you wouldn't use up/down for first/last if it is vertical

MK: you could
... on the wrapping behaviour
... do we want to enforce it or make it optional
... really like to encourage this

<Birkir> This is highly desirable for large menus (arbitrarily saying 8 menus or more), but for small menus with few items, it is less important.

JN: why do we want this

<Birkir> I'd vote for "optional but nice", to use my invented technical term.

MK: *long story* it's easier if you go through a menu and make up your mind if you're on the last item
... you can just wrap to the first item

AA: so make wrapping optional?

MK: main bug in menu button, don't duplicate anything that is in menu

<jemma_ku> Thanks, Michiel. I sent you an email.

<jemma_ku> I have another meeting in 7 min

MK: thank you all, great feedback

AA: I'm seeing a bunch of other variations on setting properties.

BG: are you removing quotes?

MK: removing quotes and add “to“

MB: I like having the quotes, makes it easier

MK: we don't have it consistently.

MB: maybe later

Review bug fixes for menubutton design pattern https://rawgit.com/w3c/aria/apg_menuPattern/practices/aria-practices.html

NOTE: covered in previous discussion

Review revised descriptive text for example of mixed checkbox https://rawgit.com/a11ydoer/practices/master/examples/checkbox/checkbox-3.html

<jemma_ku> take up item agenda 5

Review revised descriptive text for example of mixed checkbox

<mck> https://rawgit.com/a11ydoer/practices/master/examples/checkbox/checkbox-3.html

MK: semantics typo in first sentence

JK: I'll fix it

MK: third bullet “This set of example” should be “This set of examples”
... how come there are square brackets around role=checkbox?

MB: only makes sense if you're talking about CSS selectors; which we are not

<jemma_ku> michiel, we don't hear you

<jemma_ku> you are on mute

<mck> One way to write it: The <code>div</code> element with role <code>checkbox</code>

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2015/11/30 19:49:43 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/deswign/design/
Succeeded: s/contains/activates/
Succeeded: s/Micheil/Michiel/
Found Scribe: MichielBijl
Inferring ScribeNick: MichielBijl
Present: JamesNurthen AnnAbbott jemma_jaeun_Ku Michiel_Bijl Bryan_Garaventa
Regrets: Léonie_Watson

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 30 Nov 2015
Guessing minutes URL: http://www.w3.org/2015/11/30-aria-apg-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]