<trackbot> Date: 24 October 2014

<jongund> hello

MC: We can't create sub-components in Bugzilla. Could use design pattern name in bug title, or could add a custom field when filing bugs - although the field wouldn't be exclusive to the ARIA component.

<scribe> scribe: Léonie Watson

<scribe> scribenick: LJWatson

LW: Suggest put design pattern title in bug title.

MC: For terminology clarity - product is ARIA, component is APG 1.1.

MK: We could have "Pattern name: Title summary"

BG: Use brackets?

MC: Helps to keep it simple.

BG: What about "APG-pattern-"?

LW: Lots of false positives with design pattern titles like "link" "checkbox" "button" etc.

MC: "Pattern-Design-pattern-name", for example "Pattern-Media-player-widget".

MK: Ok, we'll go with it.

Link design pattern

http://www.w3.org/TR/wai-aria-practices/#link

LW: It uses "tab chain", and rest of document uses "tab sequence" and "tab order" too. Confusing.

MK: The Shift f10 is Windows specific, possibly Linux too, but not on Apple platforms.

JG: Is that for author defined context or platform defined?

MK: Either.

JG: Should be author's responsibility to define correct platform shortcuts.
... As an author I don't think about context menus for native links, why should I have to for role link?

MK: Hmm. Don't know. Trying it now...
... FF does not open standard link context menu when role=link.

LW: Design pattern doesn't mention tabindex.

JG: If it's something the browser should do it needs to go into the implimentation guide.

BG: Not sure browser should handle it. What if want to provide own context menu? Which takes priority?

MK: You can take over the context menu on a standard link though.

BG: Simulated link has no resource locator.

MK: Would href work?

BG: Doubt it.

LW: Could we include a note to say the design pattern won't produce a context menu?

JG: Good warning to include.

MK: ARIA spec doesn't say anything about context actions.

BG: Make it more clear that interaction/navigation is the author's responsibility.
... Specify that onclick isn't sufficient on a non-interactive element.

Examples repo

MK: We want to get a repo for custom examples.

MC: Suggest we create a folder within the current APG repo for examples.
... Well get GT-pages setup.

MK: "Examples" would be a good name for that folder.

+1

MK: Need to discuss in editors meeting?

MC: No, not for this I don't think.

<scribe> ACTION: Léonie to create examples directory in practices Github repo, and add link example. [recorded in http://www.w3.org/2014/10/24-aria-apg-minutes.html#action01]

<trackbot> Created ACTION-1521 - Create examples directory in practices github repo, and add link example. [on Léonie Watson - due 2014-10-31].

LW: Suggest we files separate bugs for separate issues.

MK: Even if they relate to same pattern?

MC: Would suggest separate bugs, yes.

<MichaelC> https://www.w3.org/Bugs/Public/

MC: Suggest we use the wiki for work planning, Bugzilla for specific bugs and/or Github for bugs against examples.

MK: Filing bugs.

BG: DOes link pattern mention hasPopup?

MK: No, doesn't need to. Perhaps should be a note to that effect?

BG: What about when overriding default context menu?

MK: A hover menu?
... Even with Shift f10 that fails WCAG.

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/coponent/component/
Succeeded: s/metnion/mention/
Found Scribe: Léonie Watson
Found ScribeNick: LJWatson
Present: Matt_King Léonie_Watson Bryan_Garaventa Jon_Gunderson Michael_Cooper
Found Date: 24 Oct 2014
Guessing minutes URL: http://www.w3.org/2014/10/24-aria-apg-minutes.html
People with action items: l onie

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