<mck> https://github.com/w3c/aria-practices/wiki/October-9%2C-2017-Meeting

<scribe> scribe: AnnAbbott

MK: essential editing should be able to be finished by end of month
... open issues will go into 3Q2017

Issue 413 - KeyBoard navigation for xOS

Paragraph to discuss: Although users of Mac OS X are familiar with using the Command key instead of the Control key, the Command key is typically reserved for desktop applications and OS-level integration. Until device and platform independence can be addressed in WAI-ARIA 2.0, the primary Control modifier key for WAI-ARIA widget interaction is specified as Control on all platforms,...

scribe: including Mac OS X.

MK: doesn't call out difference between Mac OSX and Windows

JN: as long as dev has documented what does what, should be good

MK: would be more comfortable if a Note calls out the difference via Keyboard section

AA: do we really have to document that?

https://github.com/w3c/aria-practices/wiki/October-9%2C-2017-Meeting

AA: can't we point them to an Apple doc so we don't have to maintain?

JK: #2 seems like too much work

AA: meat of matter needs to go in the Keyboard section

MK: issue also appears in selection pattern/composite

BG: would rather leave it up to the browser
... more important to list what controls widget type

MK: doesn't feel like that paragraph can remain in published version

<mck> in spin button it says:

<mck> ◦ Standard single line text field keys, such as Left Arrow, Right Arrow, Shift + Left Arrow, Shift + Right Arrow, and Delete, for cursor movement, selecting

<mck> text, and text deletion.

<mck> Proposal: Supports standard text input, editing, and selection keys based on browser support for native HTML input type text or contenteditable.

MK: and delete paragraph in question entirely

AA: agree

JG: agree

MK: where text input is mentioned, use Proposal and remove mention of specific key

Action 1 above

<trackbot> Error finding '1'. You can review and register nicknames at <http://www.w3.org/WAI/ARIA/track/users>.

2) write mapping section, then add Note here it pertains

Issue 47: Add note addressing validation errors resulting from aria-expanded on menuitem elements to Menu and Menubar patterns and examples

<mck> http://w3c.github.io/aria-practices/examples/menubar/menubar-1/menubar-1.html

<mck> Currently, using aria-expanded on elements with role menuitem triggers HTML validation errors because the ARIA specification does not yet support doing

<mck> so. The ARIA working group plans to resolve this issue in the next version of the specification. Until a version of ARIA that resolves

<mck> the issue

<mck> becomes a W3C recommendation, it is safe to ignore these validation errors. Alternatively, since only a few browser and assistive technology combinations

<mck> exploit this feature of the pattern, it can be omitted from implementations.

AA & JN agree

<mck> http://w3c.github.io/aria-practices/#menu

MK: will add Note and aria-expanded to 2.16 also
... also contains bold text to see note below

AA: completed review of scrollable listbox

JK: done with combobox review

<jemma> https://github.com/w3c/aria-practices/issues/464

MK: Oct 30 deadline for review of doc prior to publish notification
... 7-day CFC end of Nov planned
... need to be DONE by 10/23 which will allow for bug cleanup early Nov
... hold off on carousel example
... wants 1.0 combobox pattern included if possible

JG: will try

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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: jamesn AnnAbbott JaeunJemmaKu Bryan_Garaventa jongund matt_king
Found Scribe: AnnAbbott
Inferring ScribeNick: AnnAbbott

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 09 Oct 2017
Guessing minutes URL: http://www.w3.org/2017/10/09-aria-apg-minutes.html
People with action items: