<scribe> scribe: jcraig
Zakim. next item
<jamesn> https://github.com/w3c/aria/issues/1286
Is it possible to expose descendants of childrenArePresentational? #1286
jamesn: sounds like AAM
issue
... propose closing or getting Steve to take into HTML-AAM or
validation.
jcraig: seconded. this should be moved to HTML-AAM
jamesn: either way, this isn't an ARIA issue, either another spec or a browser bug
https://github.com/w3c/aria/issues/1284
ARIA WG input on HTML dialog focus behaviour #1284
jamesn: doesn't need milestone... maybe project
<jamesn> https://github.com/w3c/accname/issues/83
moving to 1.2 milestone of accname
https://github.com/w3c/aria/pull/1287
review volunteers?
adding sina and jongund
and jcraig
jongund: https://github.com/w3c/aria/pull/1224
<jongund> https://github.com/w3c/aria/pull/1224
jamesn: it's on the agenda for later in the call
back to meaty topic... need to agree on the discussion item.
<jamesn> https://github.com/w3c/aria/issues?q=is%3Aopen+is%3Aissue+label%3Adeep-dive
at-shortcuts https://github.com/w3c/aria/issues/1257
dialog modal or non https://github.com/w3c/aria/issues/1210
jamesn: no deep dive next week
Matt_King: agreed
<jamesn> https://github.com/w3c/aria/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22ARIA+1.2%22
https://github.com/w3c/aria/issues/1277
"menuitemradio/menuitemcheckbox shouldn't support aria-expanded. Maybe radio should?"
<joanie> https://github.com/w3c/aria/pull/1278#issuecomment-635509892
Matt_King: I think we landed on "no restrictions"
<joanie> From the call:
<joanie> don't support aria-expanded on radio
<joanie> do support aria-expanded on menuitemradio and menuitemcheckbox
<joanie> do remove the multiple inheritance (i.e. remove checkbox from menuitemcheckbox superclasses, and remove radio from menuitemradio superclasses)
joanie: discussed 2 weeks ago
<joanie> Also, I will move the javascript fixes for prohibited attributes to a PR in aria-common so that the code is not lost.
https://github.com/w3c/aria/issues/1275
Cleanup menuitemradio grouping author requirements
PR waiting for merge
https://github.com/w3c/aria/issues/1151
PR https://github.com/w3c/aria/pull/1224
jongund: tried to resolve any
comments as received
... Aaron wanted it limited to specific roles.
... Matt may be concerned about that edit... Matt didn't want
it limited...
Matt_King: I think that's okay.
jcraig: I abdicated further reviews on this one... stated my opinion and will defer to group decision.
<jamesn> https://github.com/w3c/aria/pull/1261
Final PR https://github.com/w3c/aria/pull/1261
already discussed
<jamesn> https://github.com/w3c/aria/issues/1185
alev: Firefox would have a hard time implementing this because FF now supports Mac API which is different
possibly later
implementation cost would be preventative...
I think we all agree that focused things should be exposed...
(more nuance than I can minute)
mitigation 1 and 2 , ignore aria-hidden when focus inside, and allow aria-hidden=false on rendered elements inside aria-hidden=true
mitigation 3, expose to virtual buffer
expose all focusable to virtual buffer
jcraig: not sure mitigation 3 is actionable yet see #focusabilty channel in w3c slack.
alev: use case, tools like select to speak and speak text under mouse mouse
if aria-hidden, hover text would not work... a hidden but visible state may be useful there
maybe aria-filterable=redundant
lets start with the easier non-controversial items first
table it for ARIA 3.7
jamesn: 2.0 it is
Matt_King: what are the easy items vs the items to defer
jamesn: each are individual issues so we can milestone these appropriately
#1185 to 2.0
alev: 1254 1255 1256
all 1.3 milestones
Matt_King: in aria-hidden=false on hidden subtree
alev: James Teh said in aria-hidden=false on aria-hidden=true subtree would be okay as long as aria-owns is not included in the intermediately ancestor chain
<jamesn> this is what I am picturing as being a problem....
<jamesn> <div aria-hidden=true><div aria-owns=a></div></div>
<jamesn> <div id=“a” role=“dialog” aria-hidden-false>abc</div>
Matt_King: irrelevant (example) because body is hidden
would (variant example) work?
alev: I think so, yes
should have jcsteh list some concrete examples that would be problematic
alev: need to note it in the spec b/c of interoperability. We would not want Chrome to do something that FF could not implement
issue 3?
is there an issue #?
<jamesn> https://github.com/w3c/aria/issues/1104
10 AM Pacific meeting next week, not the earlier meaty topic.
Matt_King: ARIA-AT demo will be on the 25th
MichaelC_: confirming the 25th for ARIA-AT
This is scribe.perl Revision of Date Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: jongund, Joanmarie_Diggs, Greta, MarkMccarthy, jcraig, jamesn, CurtBellew Present: jongund Joanmarie_Diggs Greta MarkMccarthy jcraig jamesn CurtBellew Regrets: PeterKrautzberger CarolynMacLeod HarrisSchneiderman SinaBahram ScottOhara Found Scribe: jcraig Inferring ScribeNick: jcraig 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.)[End of scribe.perl diagnostic output]