<MichielBijl> mck: can you please include the correct meeting URL next e-mail?

<MichielBijl> https://github.com/w3c/aria-practices/issues/26

<MichielBijl> mck: https://github.com/w3c/aria-practices/issues/26

<MichielBijl> Meeting: ARIA Authoring Practices

<MichielBijl> https://github.com/w3c/aria-practices/issues/26

<MichielBijl> meeting: ARIA Authoring Practices

<scribe> scribe: AnnAbbott

Title of meeting: ARIA Authoring Practices

Title of this meeting is wrong - this is the ARIA Authoring Practices

next item

next item

JG: has not had time to check
... successfully checked in some examples, however
... estimates he needs 2 weeks more

next item

Review resolution of issue 25 "Rename tab panel design pattern" https://github.com/w3c/aria-practices/issues/25

<mck> https://rawgit.com/w3c/aria-practices/master/aria-practices.html#tabpanel

<MichielBijl> http://w3c.github.io/aria-practices/#tabpanel

mck: changed title to "Tabs"
... from "Tab panel"

<jemma> A tabbed interface is a set of layered sections of content, known as tab panels, that displays one panel of content at a time.

mck & group: Tabs are a set of layered sections of content, known as tab panels, that display one panel of content at a time.

MB: change "Terms for understanding Tab Panels include" to "Terms for understanding Tabs include"

mck: change "Tabbed interface" to "Tabs or Tabbed interface"
... change "A set of tabs and associated tab panels." to "A set of tab elements and associated tab panels"
... change "Tab list" "The set of tabs" to "The set of tab elements"
... need to ensure that using "Tab" , include "element"

<Birkir> tabs is the name of the pattern, we need to make sure to refer to the multiple of "tab" as "tab elements", to avoid confusion.

mck: remove the sentence referring to complex widget.

<MichielBijl> mck: dump line: “A collection of tab elements and their associated tab panels is a complex widget, because it performs show/hide actions as well as moving the user's point of regard around within the content.”

<MichielBijl> MB: done

<jemma> A default tab is specified that is active when the tabbed interface component is initialized.

<jemma> Ann and Teresa are asking about this.

<MichielBijl> PROPOSAL: There should be one active tab element when the tabs are initialised.

mck: change " A default tab is specified that is active when the tabbed interface component is initialized." to "one tab element is active when the tabs are initialised.
... will work on language for orientation

<mck> i think my phone died ... one moment

AA: I think terms that are aria roles should be links

<Birkir> change "The active tab is placed into the tab order. " to "When a tab is activated, the previously active tab is removed from tab order and replaced by the activated tab."

mck: working on keyboard section

include link to "managing focus"

MB: changing tab to tab element"
... tab key references get confusing

<jemma> birker has concerns about "The user reaches the tabbed panel component by pressing the tab key until the active tab title receives focus."

mck: remove that sentence
... tab key moves focus to the active tab element in the tab list

Birkir: aria-labelledby is missing

from tab panel

take up item 3

<MichielBijl> https://github.com/w3c/aria-practices/pull/39

JG: needs to leave call early and asking to review combo box examples next week

mck: goal for dialog is just to log issues

<MichielBijl> http://w3c.github.io/aria-practices/#dialog_modal

mck: has not started combining under one section and then define specifics in subsections

AA: second sentence is pretty confusing

mck: last bullet in kbd section - want to delete "Enter"

Group agrees as there is no special function of Enter in dialog

Birkir: change "Escape: closes the dialog without taking any action" to "Escape: activates the close button".

mck: thinks first bullet under Note needs example.

<MichielBijl> MB: +1 to remove

MB: or move first bullet to last bullet
... make second bullet the first bullet

mck: third bullet: add word 'typically'
... initial focus should go to the least destructive action.
... three or four more notes are possible for this section

<Birkir> What about "If one of the dialog action items deletes or submits user data, but other options do not, make sure to place initial focus on one of the elements taht do not."

Group agrees to delete first bullet - no objections

jemma: looking for documentation on use of h1

Birkir: what about focus going to dialog container?

<jemma> *thanks, michiel

<MichielBijl> https://dir.rawr.eu/research/dialog/index.html

rsagent, make 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/PROPOSAL: There should be one selected tab element when the tabs are initialised.//
Succeeded: s/MB/Birkir/
Found Scribe: AnnAbbott
Inferring ScribeNick: annabbott
Present: jongund MichielBijl jemmaJaeunKu AnnAbbott TeresaBoers JonGunderson Birkir IanPouncey MattKing Bryan_Garaventa
Found Date: 09 May 2016
Guessing minutes URL: http://www.w3.org/2016/05/09-aria-apg-minutes.html
People with action items: 

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