<Rich> https://lists.w3.org/Archives/Public/public-aria/2016Oct/0034.html

<jamesn> what is the correct URL for webex? I got

<jamesn> The meeting has been cancelled or ended!

<scribe> Scribe: Stefan

ARIA 1.1 CR CFC Decision

<Rich> https://lists.w3.org/Archives/Public/public-aria-admin/2016Oct/0016.html

Rich: 1.1 now CR
... next tep meet with director2 next Wednesdays (26.)

Michael: transition request in between

Rich: next wednesday chair ARIA WG?

Michael: OK

Rich: will fix URL in agenda also

Michael: correct URL is in IRC topic

<jongund> forgot meeting password can someone send it to me

<MichaelC> Updated WebEx info

<Rich> https://www.w3.org/WAI/ARIA/wiki/ARIA_2.0_Issue_Triage

ARIA 2.0 Triage and ARIA 1.2 requirements

Rich: Start with Issue 530 ISSUE-530- https://www.w3.org/WAI/ARIA/track/issues/530)
... Do we need that for ARIA 1.1?
... sounds editorial
... let's put it in ARIA 1.2

Joanie: ok for me

Matt: we have required context already

Rich: they want to do it from the other direction

Matt: we have required context already

Rich: don't remember

Joanie: rowgroup vs. row .. editorial arrows (visual thing)

Matt: we need notes here saying exactly what was inteneded

Joanie: required context role - we have it now

Rich: this editorial change can be made

Stefan: I was insecure about the wording for arrows

STefan arrows -> means rows

<Rich> issue-641?

<trackbot> issue-641 -- Abstract role section allows nameFrom content, and some subclassed roles under section do not allow nameFrom:contents (even definition, img, and math, which seems like they should) -- open

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/641

Joanie: done

<Rich> issue-702?

<trackbot> issue-702 -- The ARIA Roles Model spec states that keyboard support for interactive widgets is optional, not required, which it should be. -- open

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/702

Rich: I have to look at this shoud
... (looking at it) .. nothing found

James: no "must" please#

Rich: spec states that it is optional. on some devices you my not have a keyboard

Matt: content authors are required to manage focus .. strange .. in different sections .. we should change 2.3 probably
... content authorsshould manage focus

<jongund> what about blue tooth keyboards

Matt: on mobile devices there is no keyboard, no must here possible

John: what about bluetooth devices with keyboarfds

Rich: for safari on mobile you don't get reliable keyboard events (?)

Matt: sure?

Rich: yes
... vauestep in ARIA 1.2 - reason for it
... not ideal but we gotta d0 it

<Rich> https://www.w3.org/TR/WCAG20/#keyboard-operation

Rich: kb make all functions available from kb

Matt: does it work without screenreder but with keyboard alone? Bryan: yes
... we need requirement with normative wording inside
... I propose to say this is intentionally not a must

Rich: we do it in triage

Matt: kinda editorial

Rich: any objections to move it to 1.2
... no? Done.

<Rich> issue-1011?

<trackbot> issue-1011 -- For role="text", there needs to be requirements on user agents for overrides, such as controls, events, and other global aria properties, like there is for role="presentation". -- open

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/1011

Rich: we don't do this in 1.2
... could be 2.0 discussion

Matt: yes

Joanie: parts are already covered
... dupe of static text

Rich: yes
... (updating nd closing)

<Rich> issue-103?

<trackbot> issue-103 -- Expand value types for aria-invalid -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/103

<Rich> https://www.w3.org/TR/WCAG20/#keyboard-operation

Rich: leave it as ARIA 2.0? No objections.

<Rich> issue-161?

<trackbot> issue-161 -- Refine live region support -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/161

<Rich> issue-16?

<trackbot> issue-16 -- changes to the same content fragment may come from user and from world -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/16

<Rich> https://www.w3.org/WAI/PF/Group/comments/details?comment_id=10

Rich: web components may give us some help here

Matt: scope is HTML? no minor editorial things

Rich: leave it for 2.0. OK for anyone?

James: chess board example
... live regions should announe WHO did changes on them

Rich: bid change
... big change

Joanie: including it in 2.0 but not closing it yet
... we have some sort of messaging thing in ARIA 2.0

James: mesaging thing should be moved to ACC API STUFF

Matt: fix later

<Rich> issue-366?

<trackbot> issue-366 -- level property should be consistently applied either to leaf or container nodes -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/366

Rich: no author confusion yet detected about this yet
... we leave it in for now

<joanie> issue-443

<trackbot> issue-443 -- ARIA group role should allow the aria-required property -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/443

<Rich> issue-443?

<trackbot> issue-443 -- ARIA group role should allow the aria-required property -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/443

issue-443?

<trackbot> issue-443 -- ARIA group role should allow the aria-required property -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/443

Rich: I think we had this already

Matt: should we allow required on group as for radiogroup?

James: saying required for checkbox is pointless

Matt: required has a tendency to add some noisiness and potemtial confusion
... current set of required in ARIA is ok for me

Rich: leave, move , close?
... consensus is to close with commen "won't fix"

issue-465

<trackbot> issue-465 -- All comboboxes should not implicityly set aria-haspopup=true -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/465

Matt: fixed

Rich: I thought it, too

Rich closing it

issue-506

<trackbot> issue-506 -- Progressbar: Consider whether accessible name should be required -- raised

<trackbot> http://www.w3.org/WAI/ARIA/track/issues/506

Rich: context is clear .. progress

Matt: if cntext is clear we nead no label

Rich: I don't mind closing it

Timeline for 1.1 Authoring Practices

Matt: we do have def of done .. 1.1.PR .. April (?) .. Milestone

<jamesn> https://github.com/w3c/aria-practices/milestones?direction=asc&sort=completeness&state=open

Rih: what's the latest you gonna publish it?

Matt: April

Rich: OK I will tell Michael

James: but then there will be still stuff not in yet

Rich: we should have release date schedule

Matt: final 1.1 and then after that (6 Month) will an updateted release follow

<jongund> bye

Matt: we want align version numbers with ARIA spec but also update the thing without changing that .. our idea are revisions

James: next 1.1. revision will be october 2017

rssagent, make minutes

?

MichaelC what was the command to make minutes?

This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/present_//
Succeeded: s/Joanie: I don't like the arrows (?)//
Succeeded: s/Joanie: rows - may be confusing//
Found Scribe: Stefan
Inferring ScribeNick: Stefan
Present: Joanmarie_Diggs Janina MichaelC JamesN Rich_Schwerdtfeger Matt_King jaeunku jongund
Found Date: 13 Oct 2016
Guessing minutes URL: http://www.w3.org/2016/10/13-aria-minutes.html
People with action items: 

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