meeting minutes for Thursday, 23 August - ARIA Working Group

https://www.w3.org/2018/08/23-aria-minutes.html


See below for the text version of the minute.

Jemma

Accessible Rich Internet Applications Working Group Teleconference
23 Aug 2018
Attendees
Present
MichaelC, jemma, Stefan, jamesn, janina, curtbellew, melanierichards
Regrets
MattKing, IrfanAli
Chair
JamesNurthen
Scribe
Jemma
Contents

  *   Topics<https://www.w3.org/2018/08/23-aria-minutes.html#agenda>
1.   F2F in Q1<https://www.w3.org/2018/08/23-aria-minutes.html#item01>
2.   New Issues since last meeting – Triage ONLY<https://www.w3.org/2018/08/23-aria-minutes.html#item02>
3.   TPAC Agenda - https://github.com/w3c/aria/issues/806<https://www.w3.org/2018/08/23-aria-minutes.html#item03>
4.   New Issues since last meeting – Triage ONLY<https://www.w3.org/2018/08/23-aria-minutes.html#item04>
5.   PR Reviews – can we merge the following?<https://www.w3.org/2018/08/23-aria-minutes.html#item05>
6.   TPAC Agenda - https://github.com/w3c/aria/issues/806<https://www.w3.org/2018/08/23-aria-minutes.html#item06>
7.   Issue 787 – Required states and properties with default values<https://www.w3.org/2018/08/23-aria-minutes.html#item07>
8.   Role Parity – Block and Inline roles<https://www.w3.org/2018/08/23-aria-minutes.html#item08>
9.   Misc Issue Processing<https://www.w3.org/2018/08/23-aria-minutes.html#item09>

  *   Summary of Action Items<https://www.w3.org/2018/08/23-aria-minutes.html#ActionSummary>
  *   Summary of Resolutions<https://www.w3.org/2018/08/23-aria-minutes.html#ResolutionSummary>

________________________________

<jamesn> trackbot, start meeting

<jamesn> agendaagenda+ F2F in Q1 - 2019?

<scribe> scribe:Jemma

F2F in Q1

jn: any preference to have a meeting before CSUN or after?
... we are ruling out having the f2f right before CSUN
... Michale will communicate that with Judy.

New Issues since last meeting – Triage ONLY
TPAC Agenda - https://github.com/w3c/aria/issues/806


jn: please add topic to this git hub issue if you have any meeting topic suggestion

New Issues since last meeting – Triage ONLY

https://github.com/w3c/aria/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+created%3A%3E%3D2018-08-16+


jn: it seems to be editorial issue

https://github.com/w3c/accname/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+created%3A%3E%3D2018-08-16+ Core AAM –

<jamesn> /github.com/w3c/accname/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+created%3A%3E%3D2018-08-16+ Core AAM –//github.com/w3c/core-aam/issues/20

PR Reviews – can we merge the following?

<jamesn> https://github.com/w3c/aria/pull/799


<jamesn> https://pr-preview.s3.amazonaws.com/w3c/aria/799/ff8cd29...f8b1624.html


For issue #700, made the following changes to the option role section in index.html: Remove sentence from description that states there is an default value of false fore aria-selected on option elements. Remove aria-selected from required states and properties row of attributes table. Add aria-selected to supported row of attributes table. Remove default value for aria-selected from implicit values row of attributes table. Note: This cascades to treeitem so that ar

carole: it looked fine to me.

jn: any opposition for merging it?
... no objection

RESOLUTION: we have agreement for merging 799

TPAC Agenda - https://github.com/w3c/aria/issues/806

Issue 787 – Required states and properties with default values

jn: https://github.com/w3c/aria/wiki/Required-Properties-with-Default-Values

... option aria-selected: false will be removed as we discussed
... if it is required, we can define the default value, if not, figure out what to do.

stefan: non required status should also have default value.
... every state of aria property should have the default value.

jn: question is coming from vaildating author code.

stefan: defining the default value is for the fall back for API mapping

jn: defining the default value is for the fall back for API mapping

stefan: I would prefer to make it simple and consistent- discussion of slider orientation example)

brian: actually, it depends on the widgets we are talking about.
... aria -checked is required in checkbox. but not in tree widget.

carole: having default fall back value may be a good one as Stefan suggested.
... in case it was not given by the author

it seems to be a good idea to put required default value to core aam

melani/carole: it seems to be a good idea to put required default value to core aam

jn: it would be good to go through the list and find out what is required or not. https://github.com/w3c/aria/wiki/Required-Properties-with-Default-Values


carole: I will review it

jn: example - heading aria level vs spin button required value

Role Parity – Block and Inline roles

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


jn: topic context - creating two general role based on aria f2f meeting

https://github.com/w3c/aria/pull/805


matt's comment-https://github.com/w3c/aria/issues/699#issuecomment-415056187


carole: jn's point - issue of mixing the style with semantics

<jamesn> https://github.com/w3c/aria/wiki/Plans-regarding-role-parity#generic-role


stefan: we can think about what would be the benefit of having block and inline

jn: please add info to the issue so that we can make a decision based on those.

Misc Issue Processing

rrsagents, make minutes

Summary of Action Items
Summary of Resolutions
1.   we have agreement for merging 799<https://www.w3.org/2018/08/23-aria-minutes.html#resolution01>