<jemma> jpresent+ jongund

<mck> next item

<jemma> regrets michielbijl

<jemma> brian: not effective in putting focus on leave

<jemma> brian: use aria-own for grouping

<jemma> mk: why do we need aria-lable?

<jemma> jg:tree has grouping label

<jemma> jg:ul has grouping label

<jemma> brian:suggestion is putting role tree item on span

<jemma> mk: grouping is more for setsize and etc

<jemma> mk: treeitem does not own the group

<jemma> mk: treeitem should be in tree or in treeitem

<jemma> brian: if you want to map the structure, you can use aria-own

<jemma> brian: treeitem is already child item, using aria-own

<jemma> brian: the rest will be in accessibility trees

<jemma> mk: you don't want a tree item node named by all of its children

<jemma> jg: grouping element are children of menu item here, not sibling you picked as an example, brian.

<jemma> jg: pos, setsize is used for calculating dom. what I am hearing is that browser is not stably using dom to calculate.

<jemma> brian: right arrow should stay in the expanded node, not the next item

<jemma> jg:keyboard support should be depth first?

<jemma> birkir: if node is open, child is open the focus go to that children.

<jemma> mk: next visible node is not the same as hierarchical structure.

<jemma> mk: there is firefox bug - not calculating correctly poset, set size.

<jemma> mk:Jon, you have feedback from the group members, -grouping, posset, setsize..

<jemma> mk: this is one of situations where we need to code according to spec

<jemma> mk: we can mention when the browser is not working correctly and file the bug so that bugs can be resolved.

<jemma> mk:it seems to odd to use aria-label and aria-labelledby

<jemma> jg: accessible names in trees do not use aria-label, aria-labelledby

<Birkir> What about <li role="treeitem"><span id="foo1">Fruit</spans><ul role="group" aria-labelledby="foo1"><li role="treeitem"">apples</li>...</ul></li>

<jemma> mk: never seen the case, menu is labelled by menu items

<jemma> mk: real question in menuitem, tree item, if you are naming from content, allowable name in tree item or menu item owns tree branches or menus, how should accessible name be calculated?

<jemma> brian: it is not always direct child and parent relationship in tree

<jemma> mk: what is the definition of "level" here?

<jemma> mk: we have to use aria level for every tree item

<jemma> jg: we need to let people know what makes it work.

<Birkir> scribe: Birkir

MK: For now we need to require authors to include aria-setsize and aria-posinset on every treeitem role.
... We need to consider raising normitive requirements for next version of the ARIA spec. The spec is ambiguous about how these things should be built.
... JG: Can you make the tree branch with only tree example, ditto for landmark. Else we will ahve a monstrous merge pull request.

<jemma_> next item

<jemma_> take up item 2

<jemma_> jg: changes: move the buttons to the top

<jemma_> went through some of aria issus and fix responsive issues by adding bootstrap

<jemma_> jg: provide role information, not reveal lable

<jemma_> jg:fixed consistency issues, fix form issue

<jemma_> jg; now we have landmark example for form in the doc

<jemma_> jg:working on show landmark and other functionality in bookmarklet tool so I can add more functionality

<jemma_> mk: I really want this landmark example to be included in next publication.

<jemma_> mk: please include this in the master using pull request.

<jemma_> jg; I will make a pull request by the end of today to merge changes to master

<jemma_> birkir; if there is edtiorial change, I am happy to send out.

<jemma_> mk:best way to request editorial change is creating a git issue.

<jemma_> birkir: I had some comment for keyboard navigation shortcut

" The use of landmarks roles support keyboard navigation to the structure of a web page for screen reader users, and can be used as targets for author supplied "skip links" "

Cange to "screen readers offer keyboard navigation shortcuts to landmark roles".

<jemma_> mk: some editorial change - I may be able to remove target audience since we dont define all the audiences for each doc for the consistency.

<jemma_> next item

<jemma_> https://github.com/w3c/aria-practices/wiki/Design-Patterns-Status

<jemma_> mk: birkir, would you be interested in building accordion exmaple?

<jemma_> IP in the design pattern update table is Ian Pouncey

<jemma_> mk:birkir will contact Ian and find out accordian example status

<jemma_> jg:Jemma and I will be reworking on menubutton and menu bar.

<jemma_> jg: I would like to get feedback on documentation.

<jemma_> jg: documentation template feedback needed I would also want to hear about the issue, synchronization on visual presentation

<jemma_> mk: do you want to treeview example as representative template?

<jemma_> mk: do you want to put this as next agenda item?

<jemma_> mk; If I can make next meeting, I can add this agenda. but I am not sure about my schedule yet. Jame will chair the meeting.

<jemma_> mk:what is menu bar status?

<jemma_> jg: jemma is working on it with Nick, another programmer at U of I

<jemma_> mk: I also want to discuss tree grid when I come back.

<jemma_> who is here

<jemma_> scribe: Jemma/Birkir

<jemma_> rrsagents, make minutes

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)

Succeeded: s/pointset/setsize/
Succeeded: s/dept/depth/
Succeeded: s/naming form/are naming from/
Succeeded: s/till at/by/
Succeeded: s/the day/today/
Succeeded: s/birkir will take over accordion example coding/birkir, would you be interested in building accordion exmaple?/
Succeeded: s/Ian Pouncey/IP in the design pattern update table is Ian Pouncey/
Succeeded: s/isseu/issue/
Found Scribe: Birkir
Inferring ScribeNick: Birkir
Found Scribe: Jemma/Birkir
Scribes: Birkir, Jemma/Birkir

WARNING: No "Topic:" lines found.


WARNING: Replacing previous Present list. (Old list: AnnAbbott, JamesNurthen, MichielBijl, jaeunjemmaku, jaeunjemmku, jongund, matt_king)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ JamesNurthen, AnnAbbott, matt_king, jaeunjemmku, jongund, jaeunjemmaku


WARNING: Replacing previous Present list. (Old list: JamesNurthen, birkir, bryan_garaventa, jaeunjemmaku, jaeunjemmku, jongund, matt_king)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ matt_king, jaeunjemmku, jongund, jaeunjemmaku, birkir, bryan_garaventa

Present: matt_king jongund jaeunjemmaku birkir bryan_garaventa

WARNING: Replacing previous Regrets list. (Old list: leonie)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ michiel


WARNING: Replacing previous Regrets list. (Old list: michiel)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ leonie, mihciel

Regrets: leonie mihciel
Got date from IRC log name: 06 Jun 2016
Guessing minutes URL: http://www.w3.org/2016/06/06-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