<janina> James, it's me!

<janina> Tricky finding the unmute!

<StefanS> scribe: Stefan

<StefanS> Scribe: Stefan

<janina> Yo, Mark!

<StefanS> Scribe: StefanS

New Issue Triage

<aaronlev> i'm dumb, i can't join the meeting

<jamesn> https://github.com/search?l=&q=is%3Aopen+is%3Aissue+repo%3Aw3c%2Faria+created%3A%3E%3D2020-04-16+repo%3Aw3c%2Faria+repo%3Aw3c%2Faccname+repo%3Aw3c%2Fcore-aam&type=Issues

<aaronlev> "Join in Browser or Zoom App" leads me to some kind of MIT login page

<janina> https://www.w3.org/2017/08/telecon-info_aria

<jcraig> try a modern browser

<aaronlev> i used that

https://github.com/w3c/aria/issues/1251

<aaronlev> it used to work in my browser

James: 1.3?

<aaronlev> i'll try on my cell

All: agreed

next: 1244

James: 1.3, no milestones?
... no objections

next item: 1242

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

James: anybody knows this?

Joanie: related to implementing

JCraig: I look into this

James: please add milestone than

next item: 70

JamesN: is 1.2 issue

zazim, next item

No Virtual F2F

JamesN: no bandwidth, no F2F, no mental capacity
... because of situation

Matt: overhelmed by too many things

Aaron: too many hours to focus on ARIA remotely

Additional deep dive / meaty topic meetings

JamesN: additional meeting for ARIA group to discuss single topics
... potentially I will put a poll around
... Tuesday could be potential aditional slot
... also possible one hour before this meeting
... with a 15min break between the meeting

JamesC: well people tend to talk longer in adjacent meeting about same topic..

Carolyn: This call one hour earlier?

JamesN: It might work, will be in the poll

Matt: Moving this meeting earlier will be a huge ask for me

JamesN: I will put all options in the poll

<jcraig> 9 o'clock Pacific is my commute hour... the traffic is terrible.

Aaron: what's good in the deep dives: less partipicants

<Jemma> 9am works for me. it is 11am for me.

Definition of focusable – Carolyn

<jamesn> https://github.com/w3c/aria-common/pull/39

JamesN: merged 1100

Carolyn: it is imformative the terminology section

JamesC: definition of focusable is normative?

Matt: definitions are not normative
... they give hints for interpretation
... they give hints for information

Sina: If i use an object term it must be defined

Carolyn: HTML has already done the definition of focusable
... why not just link to that?

JamesC: HTML def of focusable has probably merit, but need to check the def

Carolyn: there is a concept of inertness

JamesC: inertness in state of flux is problematic

Carolyn: in concept of inertness they dont mention dialog

Sina: 1 2 3 in last call: resolve those before closing issue out?

<jongund_> https://html.spec.whatwg.org/multipage/interaction.html#focusable-area

JamesC: it defines behaviour
... is there a meaningful difference between div not focusable by default and others?

Sina: many old dev bugs related withthat

JamesC: click focusable or entity focusable?

Harris: should we mention that we talk about attributes and not properties?

Sina: what is the question to resolve?

JamesN: whatever we comeup with: is it what browsers do? I think no

Matt: it started in PR exclude/include in ACC tree
... it hs to clearly define acc tree

JamesN: we cannot do this in this timeframe

<Jemma> <div aria-hidden="true">

<Jemma> <a href="#" tabindex="-1">foo</a> <!-- this is focusable -->

<Jemma> <input tabindex="-1"> <!-- so is this, right? -->

<Jemma> </div>

Aaron: we get bugs here automatically

Sina: at the time of focus in hidden content browsers will differe what they do
... we got to put the burden somewhere

Bryan: when something intentionally recieves focus it is possible for browsers to change acc tree, it happens already for role changes

JamesC: you could never hide native focusable elements

<Zakim> jamesn, you wanted to say that this is all sounding like too big a problem for 1.2

JamesN: too big for 1.2?

JamesC: undo, then postpone for later
... it is worth reopening

Sina: preserve conversation on this ticket please

Aaron: I would be cool with changing it doing it only on focus, happy with 1.3 thing

JamesN: deep dive topic
... we have conclusion to shift

Diagram in 5.3 needs fixing/removing – Michael

JamesN: you have created the web page, Michael

Michael: I do the update

Add UA requirements for ARIA 1.1 under combobox #1178 - Matt - https://github.com/w3c/aria/pull/1223 - waiting on changes by Matt

JamesN: this was waiting for changes

Matt: pusheed couple of comments this morning
... JamesC hopefully you have seen this
... wording changed to address issues

<Jemma> https://github.com/w3c/aria/issues/1178

Matt: 5 normative RQ were there, now there are none
... PR is there

JamesN: reviewers?

Matt: do we need pos. feedback from Wilco?

JamesN: he reads on his own
... anyone welcome to review
... waiting for reviews

Matt: massive review effort
... need to make sure not to miss somehing

JamesN: needs some minor fixes

Account for aria-owns - Jon - https://github.com/w3c/aria/pull/1224 - waiting on reviews from James N, James C, Carolyn, Matt

JamesN: please review

Matt: I did review
... ah changed -- rereview

Unclear use of descendent – James

JamesN: can anybody assist me here

Sina: I'll help

<jcraig> https://github.com/w3c/aria/issues/1150

Update Managing Focus – Carolyn

<Jemma> https://github.com/w3c/aria/issues/1121

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

Carolyn: did it 2 hours before using basically MAtts words

Caroly: I just used textbox

Carolyn: step-wise description how to change focus
... new phrase added (id)
... basically a phrase added who controls what

Matt: it is mostly about aria-activedescendant

JamesN: move to 1.3?

Sina: those combinations will work in reality?

Matt: spec is a bit inconsistent hiere, maybe editorial

https://github.com/w3c/aria/issues/1110

JamesC: 1.3 maybe fine for this
... 1.2 not to be shipped officially
... in 1.2 not to be shipped officially
... issue by AvK: number of props with datatypes other than strings
... what to do with these they asked
... my concerns were less relevant after discussion .. minor syntax changes needed
... i propose pull request and work out IDL changes

Sina: type consistency really matter here

JamesC: you can map to default value, you don't need not nullable
... we ave default values in number of places, such as aria-level=2
... enumerated string in nullable cases

Matt: also for aria-selected

JamesC: other places .. setsize
... please comment in issue if you find something

https://github.com/w3c/aria/issues/1110

<Jemma> thanks so much, Stefan.

Matt: there are cases where we don't define a default
... indeterminate values

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/just merge it/merged 1100/
Succeeded: s/witzh /with/
Succeeded: s/Html def /HTML def /
Present: StefanSchnabel1 MarkMccarthy Joanmarie_Diggs harris janina CurtBellew jamesn jcraig BGaraventa carmacleod Matt_King Jemma
Found Scribe: Stefan
Found Scribe: Stefan
Found Scribe: StefanS
Inferring ScribeNick: StefanS
Scribes: Stefan, StefanS

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


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

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


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)