<trackbot> Date: 01 June 2015

<scribe> scribe: jamesn

New example development planning wiki page (James)

Listbox pattern review https://rawgit.com/w3c/aria/master/practices/aria-practices.html#Listbox

<mattking> Listbox pattern bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=28085

JN: we looked at some of it

MK: Did something with the checkboxes section
... It was worded very differently before.

MK": was very different before and wanted people to take a look atg it

MK: there was previosuly a bunch of text explaining the selection style in listboxes where you see a check next to list items
... It was written in such a way that it was confusing in that it made it sound like theyu were checkboxes not options

http://www.jqueryrain.com/?Bxwy2bPt

JN: I guess this is a combobox not a listbox
... sorry for derailing the topic...

MK: Is the description ok? and is the structure ok?

AA: should we state what to do if you need interactive elements in a listbox

MK: don't have a widget

JN: we use F2 to switch to an interactive mode for the option

BG: doesn't talk about aria-activedescendent working for focus on listboxes

<mattking> If focus is set to the container with role listbox then aria-activedescendant must be used to refer to the option that has the visual focus indicator.

MK: I think we need a section on navigation between widgets like we have on navigation within widgets

BG: in the case where you havea single select list of options which have checkable states such as in settings dialogs. Same concept as in tree

so aria-checked is simply a state of an option but doesn't indicate anything about the selection of the listbox

MK: In a multi-select if you use selection model 1 then we should stick to aria-selected to mean selected

BG: yes i think they should be kept seperate

MK: If you are displaying a checkbox then perhaps a dev would think you should just set aria-checked

BG: actually works better in IE. Wouldn't necessarially have the same functionality as in the design pattern
... they should be treated seperately

MK: I don't think there are very many people who get hung up on a screen reader saying checked or selected

BG: if it conveys that muliple items are checked or selected. The weird thing for developers will be the implementation details.

MK: on the same page there
... what i am wondering is whether there should be any mention of aria-checked here

JN: what we are saying is that it is good as it is

MK: avoiding aria-checked is a good thing as it adds to confusion

BG: the reason I bring it up is that i have seen devs do this
... I have seen themm stuickl a real checkbox inside the option element

JN: perhaps worry more about ahving a good exmaple with checkboxes that does it correctly

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: APG TF/
Found Scribe: jamesn
Inferring ScribeNick: jamesn
Present: Ian James Matt Ann Bryan_Garaventa
Regrets: Leonie

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

Found Date: 01 Jun 2015
Guessing minutes URL: http://www.w3.org/2015/06/01-aria-apg-minutes.html
People with action items: 

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