<mck> make log world

<scribe> scribe: MichielBijl

Review fix for issue #14: Tab Panel keyboard interaction https://github.com/w3c/aria-practices/issues/14

MK: First three are related, but let's take them up in turns. Hope to close them all.

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

MK: We had feedback on the keyboard interaction.
... Have noted feedback James mentioned a couple minutes ago (more typo stuff)
... Will fix these before I close issue number 14

Review fix for issue #40: Work on orientation for tabs https://github.com/w3c/aria-practices/issues/40

MK: Will split up keyboard interaction for horizontal and vertical tabs

AA: Should we add the meat to the matter (stuff on vertical tabs for keyboard interaction)

MK: Trying to avoid redundancy within the list
... Logged this feedback, will fix and close issue

Review fix for issue #41: Include aria-labelledby on the tabpanel https://github.com/w3c/aria-practices/issues/41

MK: Closing issue based on review in this meeting

Discuss core.css changes in pull request 62: Updated treeview examples https://github.com/w3c/aria-practices/pull/62

MB: Changes to core.css should be a separate pull request

MK: I'll talk to Jon about the changes

MB: Are the styles especially for treeview?

JG: We're moving the list of different examples into the APG right?

MK: Yes

JG: Should we link to different examples in the examples themselves?

MB: I would opt for links in the APG

MK: Yes, I'd opt for simplicity

MB: Can you take those changes out Jon?

JG: Probably better for me to update it

MK: Jon, can you make a separate pull request to pull the links into the APG?

JG: Allright, I can do that
... Will try to do it this week

Issue #12: code review guide https://github.com/w3c/aria-practices/issues/12

MB: Suggest moving it into a docs subfolder. That way it gets copied to gh-pages due to the generation. Would be available at w3c.github.io/aria-practices/docs

<IanPouncey> https://github.com/w3c/aria-practices/issues/66

MK: Main goal, accelerate high quality contributions
... Should we include requirements for high contrast mode?
... Could make sister page for accessibility best practices

IA: I'll add it to issue 12 and add it to the page.

AA: Examples we add to the APG should be accessible
... HCM included

IA: Bit trickier with the changes in Windows 10.
... Cameron suggested using jshint to check code.

Review status of current example development work https://github.com/w3c/aria-practices/wiki/Design-Patterns-Status

MK: Should we merge alert dialog and modal dialog?

MB: Design patterns are independent of role right?
... If they're the same pattern with slightly different announcement or something I would merge them.

MK: Yeah I sort of agree with that.
... All the other stuff is basically the same
... Alert dialog will read the the entire thing
... Modal dialog will read title and thing that receives focus

*all sort of updates to the overview being discussed*

https://github.com/w3c/aria-practices/issues/20

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)

Found Scribe: MichielBijl
Inferring ScribeNick: MichielBijl
Present: AnnAbbott JamesNurthen IanPouncey MichielBijl Matt_King TeresaBoers jongund
Got date from IRC log name: 22 Aug 2016
Guessing minutes URL: http://www.w3.org/2016/08/22-aria-apg-minutes.html
People with action items: 

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