<jamesn> scribe: jemma

10-minute discussion: Review actions needed to finish landmarks and math

*thanks james

mk: landmark works looks good

ann: I am fine with as far as html5 section there

<boerst> I'm fine with that

<jamesn> https://rawgit.com/w3c/aria/JN_Landmarks/practices/aria-practices.html

mk: suggest to move landmark as guides

is there way to merge/pull the landmark work to the guide

jn: he will do merge the doc

group agrees to merge the work

mk: should math be part of this aria discussion?

jg: birker and bryan are trying to get information for best practice for math role

mk: math role has a place for guide

jn: there is github issue about math role

mk: would we bring this to the agenda item?

jg: I will help to bring this to agenda items

ann: how about AT for the math role?

jn: role=math is not brand new in aria 1.1

jg: will bring the math role agenda in three weeks
... after all my travel

<jamesn> https://github.com/w3c/aria/issues/290

mk: created the issue and will assign to jon gunderson

<jongund> jongund

ann: why do we assign the issue to jon?

<jongund> I don't know

<jongund> OK

mk: this, math role is agenda for May 9

ann: math role is not in design pattern

jn: section 1.0 version has math role as a separate section

next topic

next item

jn: james already set up a github issue in github
... for this
... we are trying to move issues to github from bugzilla
... we can put multiple labels for the issues

mk: apg label for now

<jamesn> https://github.com/w3c/aria/issues/323

mk: actionable/sortable would not be easy to be integrate "grid"
... I would prefer not to see different section for each layout grid/sortable grid/

jn: good point
... ie. dialog - there are common part such as keyboard nav..in spite of different dialog type/usage
... grouping for grid will help people to see whole picture first rather than sticking to one specific grid example

mk: editorial work will be needed
... merging the same content section

into one such as keyboard and more

jn: we can show general section, not only subset of the grid

mk: grid is now usable as generic layout container for interactive element
... take out tabular data and reward it
... explaining generic feature which distinguish grid from table and then talk about different usage of grid
... then keyboard features..
... title is rid starting with generic description and talk about one for layout grid and the other for data ggrid
... that way we can capture UX designers' attention James is talking about

jn: made a git hub issue for this

mk: how would we want to address focus management strategy inside grid?
... different screen reader case when using jaws and voice over for grid
... if it is more about focus management, not screen reader management, the description will fit into non keyboard section
... will try to make one keyboard section for now for both type of grids
... will see how the group thinks

jn: the same behavior like that of excel - tab in and make the cell active and edit the data
... use tab to edit the cell

or edit box

mk: will add a link to tree grid from grid section

ann: need distinction of table from grid

<jamesn> https://www.w3.org/TR/wai-aria-1.1/#grid

mk: need to rewrite the grid description such as removing the paragraphe "This can be achieved by ...." and more
... I will take this action item

<jamesn> https://github.com/w3c/aria/issues/323

Re-title to "Grid" Have 2 sub-sections within the description for "Data Grids" and "Layout Grids" Keyboard Section Need to add something about navigating to the cell or the content (Matt to write) Re-write description section to remove information which is no longer relevant in ARIA 1.1 and to add content about new features in ARIA 1.1

next item

next item

Review new examples and update pattern work assignments https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status

jn: taking out drag and drop from pattern status

mk: drag and drop is deprecated
... we may do something better - control pattern in aria 2.0

jn: we will update Grid section in design pattern table after we edited authoring practice guide

jg: any update on combo box so that we can add combo box example?

mk: very close to be done with combo box
... in apg

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/spec/guide/
Succeeded: s/resolution/guides/
Succeeded: s/issue/issues/
Succeeded: s/mozila/bugzilla/
Succeeded: s/ann/mk/
Succeeded: s/rid/grid/
Succeeded: s/designer/designers'/
Succeeded: s/case/screen reader case/
Succeeded: s/think/thinks/
Succeeded: s/for/like that of/
Succeeded: s/box/edit box/
Succeeded: s/2.2/2.0/
Found Scribe: jemma
Inferring ScribeNick: jemma
Present: Teresa Matt Ann James Jemma Jon
Regrets: Michiel Leonie Birkir Bryan

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

Got date from IRC log name: 18 Apr 2016
Guessing minutes URL: http://www.w3.org/2016/04/18-aria-apg-minutes.html
People with action items: 

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