<trackbot> Date: 04 May 2015

<annabbott> Reviewed Button design pattern - changes made based on group input.

JN: We put in discussion points in check ins
... If the button indicates ....

AA: If the button action indicates a context change

JN: I am happy with it later

AA: After 3rd bullet, indicates a context change

MK: If the button action indicates a change of context, e.g. a wizard

JN: Add another search criteria, maybe appropriate to move focus to another place

MK: For the starting point of the "action"

JN: ... reads the proposal ...

AA and MK: WOW

AA: We know have 5 bullets

JN: Any objections?

none ....

MK: As far as button goes, the next one is checkbox, section 2.7
... I am happy with dual state and tri-state descriptions
... Bikir though he saw some edits..

JN: I will take care of it
... Why is checkbox not a word
... Checkbox is one word in Wikipedia

AA: Dual-state and tri-state are hyphenated words

JN: Fixed spelling error on checkbox
... Anything else?

MK: I did some substaintial updates to links

AA: For checkboxes we have several things referring to a visible label for a group
... Are there cases for no visible label

MK: If there is no visible label that usually no grouping label

JN: Sometimes there is a implied grouping label

MK: Checkbox grouping labels seem to be over used

BG: What about buying paints....
... Depends on how it is arranged, it is not always the case, it sometimes it does add value

MK: In my experience it is over done, grouping of checkboxes is not handled well by AT

JN: WCAG 2.0 requires grouping if it is visible grouping, like a border, even without a border

MK: That is enough for the AT users

JN: If there is a border then it must be conveyed

MK: It can just be styling, when it does it clutters the screen reader

JN: I am not saying you add a label, you can just have a grouping role without a label
... It ismore than just visual styling, they are grouped together

BG: A lot of people use CSS to convey grouping, you can make somethings look related but they really not
... Grouping can be used to differentiate between grouping and non-grouping

MK: Most real groups need to have a label

BG: The role group does have to be used (e.g. MK OL and UL)

MK: Integrating mobile ...., we could just delete grouping references

JN: I am fine with what it says now

AA: I wanted to know if the group needs a label

JN: 1.3.1 is a catch all for that

MK: Let's move on
... The defect helped me to address a number of issues

AA: We are in link now?

MK: Right
... The changes were editorial

JN: Space doesn't execute a link

MK: I thought it did
... Browsers don't support space, screen reader do

JN: I will change that

MK: The second bullet in the ARIA states and roles, that I was thinking of adding to other roles

JN: I am concerned about tabindex > 0

MK: I agree can we say that here?

JN: Doesn't this apply to all of these widgets?

MK: Some we do and some we don't, should we include this bullet or variation ...

JN: I disagree, I want these to be short and sweet

MK: They would vary based on the widgets and widget between widget, getting people to the right place in the document is important

BG: A particular widget needs focus needs ...

JN: I see that all the time, this is general stuff, it is the same on them all

MK: It is not the same, for example ina dialog box you need to put it on something in the dialog box

JN: It depends on how you are doing it

BG: I see this alot, for example radio buttons, and the focus is one a span inside, we need to make it perfectly clear it has to be on the element with the widget role

JN: Repeating it will get in aurhos way

MK: I think the pattern refer ....

JN: I think we should log an issue, I am concerned about consistency

MK: Delete here?

JN: Yes

AA: We are 9 minutes to the end, do we have some house keeping?

MK: I have it hear so you can just delet it and I will copy before I do a pull

JN: Was the note new?
... It is not a link unless you have the HREF
... The Shoft+F10, why is it repeated here?

MK: I think we need it here

AA: I made it down to listbox
... The fifth bulet..., show have a visible label
... People are going to jump all over that

JN: I will delete that

AA: That one stuck out

MK: I didn't finish the selection part, I hope it is done enough
... It was really confusing....
... It should have been a control+/...., hwy didn't it come through

JN: Where did the entity numbers come from, where they in there before?

MK: no
... we do not want to use checked in list, so this ...
... These are just normal listbox keys

AA: I have not heard of them (JN me too)

MK: I am having trouble iwtht he tags in here, so there might be some tag problems

JN: my editor is not throwing any problems, it looks right
... I will look at these to get them right if you can look ...

MK: we need to name our branch ....

JN: Can we just use "wd"?

MK: I am good with that

JN: We need to include the date

MK: No punctuation?

JN: Good with me

MK: Should I include the actual URL?

JN: I think you forgot the number sign

MK: Opps

<mattking> Proposed RESOLUTION: The APG TF submits the following branch as working draft ready for working review. https://rawgit.com/w3c/aria/wd20150504/practices/aria-practices.html

<jamesn> I dunno what you expected, but it ain't here.

<mattking> Proposed RESOLUTION: The APG TF submits the following branch as working draft ready for PF working group review. https://rawgit.com/w3c/aria/wd20150504/practices/aria-practices.html

<mattking> RESOLUTION: The APG TF submits the following branch as working draft ready for PF working group review. https://rawgit.com/w3c/aria/wd20150504/practices/aria-practices.html

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Meeting: Protocols and Formats Working Group Teleconference/Meeting: ARIA APG TF/
No ScribeNick specified.  Guessing ScribeNick: jongund
Inferring Scribes: jongund

WARNING: No "Topic:" lines found.

Default Present: James_Nurthen, Ann_Abbott, Matt_King, Jon_Gunderson, janina, Bryan_Garaventa
Present: James_Nurthen Ann_Abbott Matt_King Jon_Gunderson janina Bryan_Garaventa

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

Found Date: 04 May 2015
Guessing minutes URL: http://www.w3.org/2015/05/04-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