<jongund> I am going to be a few minutes late

make logs public

<mck> - Fix for focus ring disappearance on link 3

<mck> - Should there be a warning on link 4 about use of background images? Or, should we remove link 4?

<mck> - Should the accordion headers be changed to use native button or left as link with button role?

<mck> - Should the best-practice structure include named regions for the panels? If so, should the pattern be updated accordingly?

<mck> - Should the structure be based on DL? Or, should DL be replaced with generic div elements?

<mck> - Issue https://github.com/w3c/aria-practices/issues/265

<mck> - Example http://w3c.github.io/aria-practices/examples/disclosure/disclosure-faq.html

<mck> - https://github.com/w3c/aria-practices/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Jan+2017+Clean+Up%22+sort%3Aupdated-desc

<mck> - How much low hanging fruit can we pick off this week?

<mck> - Review assignees on issues in closest reach

<mck> - Reassess next publication date

make log world

makes log public

<scribe> scribe: JemmaJaeunKu

next item

siri: the focus ring disappears in ie11

mb: I would like to suggest to add custom focus style and disable default focus.

<MichielBijl> outline: none;

<MichielBijl> border: 2px solid black;

mb: I will take care of issue 228, disable default focus ring.

next item

<MichielBijl> MB: So, in Windows 10 with High Contrast mode turned on, background images remain in Edge, but not IE11.

jongund: I looked at other social media buttons and background img technique is not used much nowadays.

mck: so we dont

need to worry about that

next item

mck: 1.Q should we change this example to use button element or link with button role?

brian: "In the accordion example here, I already included the scripting for both techniques so it won't matter at all if you change the link into a button or into a focusable div or span instead, so these bases are already covered by reading the JS comments. I'm not opposed to making one of these examples use a button instead of a link, in which case role="button" is not required on the active element."

jongund: what is the mechanism for the indication when a user open one panel and the other will close the panel?

mck: it depends designer's choice
... accordion had heading and optional key which moves focus on heading
... part of problem for accordion is the panels are in between controls.

jongund: focus is on buttons

mck: buttons is wrapped in the heading and focus is on buttons
... assumptions for accordion is reading mode.

rather than form/application mode

jongund: so heading is technically button then.

mck: yes.
... dt is heading role
... in this example, you have to tab through everything and you can not jump over the button unless we implement a special key
... this one demonstrate the pattern well for now. In release 2, in aria 1.1 we can consider looking at examples with using html native element button.
... do we think we need to add aria landmark region info to the pattern?

bryan: region role will be useful for de·mar·ca·tion

mck: I can add those information as option to aria state, property document
... I will add this to pattern design for now and add that for release 2

next item

<MichielBijl> Fixes for issue 228: https://github.com/w3c/aria-practices/pull/281

<mck> https://github.com/w3c/aria-practices/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Jan+2017+Clean+Up%22+sort%3Aupdated-desc

mck: skipping agendum 3 for now

https://github.com/w3c/aria-practices/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Jan+2017+Clean+Up%22+sort%3Aupdated-desc

mck: I will take care of issue #279

I will assign jon and jemma to #224

mck: I will assign jon and jemma to #224

jongund: can you accept my pull request for issue #265?

<jongund> I have to go

I am done with "Identify examples where the charCode property of keypress event is used bug"

This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/for/ for the indication/
Succeeded: s/panels/ panels are/
Succeeded: s/pattern/pattern design for now/
Succeeded: s/menu/ issue #265/
Succeeded: s/brian/bryan/
Succeeded: s/Bryan Garaventa/BryanGaraventa/
No ScribeNick specified.  Guessing ScribeNick: jemma
Found Scribe: JemmaJaeunKu

WARNING: No "Topic:" lines found.

Present: MichielBijl JaEunJemmaKu ShirishaBalusani matt_king jongund Annabbott BryanGaraventa
Got date from IRC log name: 13 Feb 2017
Guessing minutes URL: http://www.w3.org/2017/02/13-aria-apg-minutes.html
People with action items: 

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report