16:34:10 <RRSAgent> RRSAgent has joined #aria
16:34:14 <RRSAgent> logging to https://www.w3.org/2024/06/27-aria-irc
16:34:14 <Zakim> RRSAgent, make logs Public
16:34:15 <Zakim> Meeting: ARIA WG
16:34:18 <jamesn> agendabot, find agenda
16:34:18 <agendabot> jamesn, OK. This may take a minute...
16:34:53 <agendabot> Sorry, I did not find an agenda.
16:58:54 <giacomo-petri> giacomo-petri has joined #aria
17:01:14 <sarah> sarah has joined #aria
17:01:40 <spectranaut_> agendabot, find agenda
17:01:40 <agendabot> spectranaut_, OK. This may take a minute...
17:01:41 <agendabot> Sorry, I did not find an agenda.
17:02:46 <katez> katez has joined #aria
17:02:50 <katez> present+
17:03:03 <spectranaut_> agenda: https://www.w3.org/events/meetings/2b57854a-65cb-421e-b9e0-f9a8da31f160/20240627T130000/
17:03:03 <agendabot> spectranaut_, sorry, could not get https://www.w3.org/events/meetings/2b57854a-65cb-421e-b9e0-f9a8da31f160/20240627T130000/ (code 429).
17:03:15 <ray-schwartz> ray-schwartz has joined #ARIA
17:03:15 <jamesn> agenda: https://lists.w3.org/Archives/Public/public-aria/2024Jun/0025.html
17:03:19 <agendabot> jamesn, sorry, could not get https://lists.w3.org/Archives/Public/public-aria/2024Jun/0025.html (code 429).
17:03:28 <ray-schwartz> +present
17:03:46 <Rahim> present+
17:03:48 <spectranaut_> agenda+ new issue triage https://bit.ly/3zewjpf
17:03:59 <jugglinmike> jugglinmike has joined #aria
17:04:12 <jcraig> scribe: jcraig
17:04:21 <giacomo-petri> present+
17:04:28 <jcraig> zakim, take up item 1
17:04:28 <Zakim> agendum 1 -- new issue triage https://bit.ly/3zewjpf -- taken up [from spectranaut_]
17:04:43 <jcraig> https://github.com/w3c/aria/issues/2260
17:04:48 <jamesn> agenda+ [New PR Triage](https://bit.ly/4cfOGsA)
17:04:48 <jamesn> agenda+ [WPT Open PRs](https://bit.ly/wpt_a11y)
17:04:48 <jamesn> agenda+ [Deep Dive planning](https://bit.ly/aria-meaty-topic-candidates)
17:04:48 <jamesn> agenda+ Reminder - no meeting July 4, 2024
17:04:48 <jamesn> agenda+ [Issue: CSS Highlights Not Clearly Documented in AAM](https://github.com/w3c/html-aam/issues/550)
17:04:49 <jamesn> agenda+ [Discussion tracking for ARIA Notification proposal - Scoping / source](https://github.com/w3c/aria/discussions/1958#discussioncomment-9653368)
17:05:00 <jcraig> spectranaut_: scott is not on the call
17:05:25 <aaronlev> aaronlev has joined #aria
17:05:31 <jcraig> is there reason for author to maintain both valuenow and valuetext?
17:05:52 <jcraig> jamesn: does it do anything? is it useful?
17:06:17 <dmontalvo> present+ Daniel
17:06:32 <jcraig> spectranaut_: need more discussion?
17:07:11 <jcraig> scott: no more to say atm
17:07:27 <jcraig> zakim, next issue
17:07:27 <Zakim> I don't understand 'next issue', jcraig
17:07:31 <jcraig> zakim, next item
17:07:31 <Zakim> agendum 2 -- [New PR Triage](https://bit.ly/4cfOGsA) -- taken up [from jamesn]
17:07:49 <jcraig> https://github.com/w3c/aria/issues/2262
17:08:11 <jcraig> scott: add a note to explain non-normative change...
17:08:21 <jcraig> spectranaut_: marked as editorial
17:08:26 <jcraig> keith: I will review
17:08:40 <jcraig> https://github.com/w3c/aria/issues/2261
17:09:21 <jcraig> spectranaut_: editorial on defining "host language attr"
17:09:51 <scotto> scotto has joined #aria
17:09:58 <scotto> present+
17:10:27 <jamesn> q+
17:10:53 <jcraig> ray-schwartz: used language already in the spec... mentions of "host language" in other files. could write a more full definition if we should.
17:11:27 <jcraig> should define "host language" in addition to "host language attribute"
17:12:23 <jcraig> jamesn: add me as a reviewer... i will help ray with the respec addition of a definition
17:12:33 <jcraig> https://github.com/w3c/aria/issues/2259
17:12:42 <jcraig> spectranaut_: no need to discuss
17:13:00 <jcraig> zakim, next item
17:13:00 <Zakim> I see a speaker queue remaining and respectfully decline to close this agendum, jcraig
17:13:04 <keithamus> present+
17:13:08 <jcraig> ack jamesn
17:13:09 <jcraig> zakim, next item
17:13:09 <Zakim> agendum 3 -- [WPT Open PRs](https://bit.ly/wpt_a11y) -- taken up [from jamesn]
17:13:36 <spectranaut_> https://github.com/web-platform-tests/wpt/pull/46769
17:14:17 <Francis_Storr> Francis_Storr has joined #aria
17:18:40 <jamesn> +1 to that
17:18:57 <jcraig> discussion continued with scribe...
17:19:17 <jcraig> aaron mentioned agreeing with the idea to roll the orphaned tests back
17:20:51 <jcraig> deep dive scheduled july 11th
17:22:02 <jcraig> scott mentioned james's teh's comment. don't roll back the html defaults that were already working... mastadon issue from jcsteh comment on list items
17:22:22 <jcraig> zakim, next item
17:22:22 <Zakim> agendum 4 -- [Deep Dive planning](https://bit.ly/aria-meaty-topic-candidates) -- taken up [from jamesn]
17:22:48 <jcraig> spectranaut_: dive this morning on "undefined" (IDL, string vs state, etc)
17:23:11 <jcraig> spectranaut_: on july 11th, we have the orphaned roles discussion
17:23:16 <siri> siri has joined #aria
17:23:19 <jcraig> spectranaut_: any other proposals?
17:23:29 <siri> Present+
17:23:59 <jcraig> spectranaut_: possibly aria issue 2241? CSS reading-flow proposal
17:24:21 <jcraig> jcraig: I'd like to review it
17:25:35 <jcraig> aaron: also familiar with the feature and it's problem with display:contents... add me to the issue too?
17:25:42 <jcraig> zakim, next item
17:25:42 <Zakim> agendum 5 -- Reminder - no meeting July 4, 2024 -- taken up [from jamesn]
17:26:01 <jcraig> spectranaut_: us independence day next week. no meeting
17:26:04 <jcraig> zakim, next item
17:26:04 <Zakim> agendum 5 was just opened, jcraig
17:26:10 <jcraig> zakim, close this item
17:26:10 <Zakim> agendum 5 closed
17:26:11 <Zakim> I see 2 items remaining on the agenda; the next one is
17:26:11 <Zakim> 6. [Issue: CSS Highlights Not Clearly Documented in AAM](https://github.com/w3c/html-aam/issues/550) [from jamesn]
17:26:17 <jcraig> zakim, take up item 6
17:26:17 <Zakim> agendum 6 -- [Issue: CSS Highlights Not Clearly Documented in AAM](https://github.com/w3c/html-aam/issues/550) -- taken up [from jamesn]
17:27:11 <jcraig> spectranaut_: aria editors decided that css rules could be added to html-aam
17:27:15 <jcraig> q+
17:27:58 <spectranaut_> jcraig: my only concern about putting css mappings in html aam is that we are less likely to have css editors/feature developers review this document
17:28:11 <spectranaut_> jcraig: they might be more likely to review a spec called "css-aam"
17:28:25 <spectranaut_> jcraig: less weighed down by all the content in html-aam
17:28:32 <jamesn> q+
17:28:42 <spectranaut_> ack jcraig
17:29:12 <jcraig> jcraig: concern with jamming css rules into html-aam... experts from CSSWG less likely to review
17:29:28 <jcraig> jamesn: starting with this. could spilt off later.
17:29:39 <jcraig> jcraig: fair enough
17:29:49 <jcraig> spectranaut_: rahim?
17:30:03 <jcraig> Rahim: will talk with Scott about it.
17:30:28 <jcraig> spectranaut_: digs into css highlight issue
17:31:12 <jamesn> ack me
17:31:17 <jcraig> what other issues in aria repo relate to CSS mappings
17:31:53 <jcraig> Rahim: i will create a keyword/tag
17:32:21 <Rahim> q+
17:32:28 <jcraig> jamesn: there were other issue tracked, but no simple way to find them all
17:34:11 <spectranaut_> jcraig: not sure there is a paper trail, look at implementations
17:34:18 <spectranaut_> ack Rahim
17:34:49 <jcraig> spectranaut_: some of the "support" may be determined by reviewing the implementation details
17:35:42 <spectranaut_> jcraig: if it is only just a couple rules, then it doesn't make sense to change. if it's more complicated, probably it should be broken off into its own spec
17:36:09 <jcraig> s/to change/to change the name of the html-aam/
17:36:14 <jcraig> zakim, next item
17:36:14 <Zakim> agendum 7 -- [Discussion tracking for ARIA Notification proposal - Scoping / source](https://github.com/w3c/aria/discussions/1958#discussioncomment-9653368) -- taken up [from
17:36:17 <Zakim> ... jamesn]
17:36:24 <jcraig> spectranaut_:
17:36:48 <jcraig> spectranaut_: related to scoping/source.. reads from the issue
17:37:27 <jcraig> notifications can only affect notifications within the same scope... should this be a shared element or something like a shared id string
17:38:19 <jcraig> aaron: element is nice because element already exists… don't need to ask the author for anything
17:38:32 <jcraig> keith api designed that way now
17:38:51 <jcraig> s/keith api/keith: api/
17:39:23 <jcraig> keithamus: maybe the notification ID in the options bag....? don't think so though
17:39:32 <jcraig> aaron: i will ask Doug to clarify
17:39:50 <spectranaut_> next open question from doug: https://github.com/w3c/aria/discussions/1958#discussioncomment-9653385
17:40:01 <jcraig> spectranaut_: asking next aria notify open question
17:40:24 <jcraig> interrupt and flushing... reads from issue linked above
17:41:10 <jcraig> adrian left comment asking for this to be clarified
17:41:49 <jcraig> in the deep dive, doug mentioned odd that higher priority notifications were unable to interrupt lower-priority notifications
17:41:57 <jcraig> jamesn: i agree that's weird
17:43:01 <jcraig> sarah: asked Doug to clarify...
17:44:37 <jcraig> keithamus: my understanding is that the implementation priority is exclusive. higher or lower notifications only affect the same level priority
17:45:01 <jcraig> jcraig: seems like we agree that, as specified, that's not ideal behavior.
17:45:27 <jcraig> sarah: flushing is built into SRs as I understand. is this possible in VO?
17:47:12 <spectranaut_> jcraig: I don't have implementations concerns yet, but it will need to happen. there are enough different ATs that also use speech... we are trying to move anything that makes sense into the engine so it doesn't require duplicated downstream technology. there is some shared AT stuff, but we probably still want to implement as much as possible in webkit
17:49:14 <jcraig> sarah: currently firing aria notify in a particular priority bucket... all interrupt and flushing needs to happen in the Windows SRs... if WebKit did it differently for the sake of downstream ATs on Mac (VO, SC, etc), would that affect the API or implementation?
17:50:09 <spectranaut_> jcraig: part of the problem, is that live regions became more complicated because we relied on screenreaders downstream to handle it. so many implementations outside the webengine... if the scope is web techs, then it should be defined in the web engine it'sself
17:50:47 <jcraig> s/ then it should/ then, as much as possible, it should/
17:52:06 <Francis_Storr> present+
17:52:09 <jcraig> sarah: let's discuss more offline
17:52:24 <jcraig> rrsagent, make minutes
17:52:25 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/27-aria-minutes.html jcraig
17:53:03 <jcraig> zakim, please part
17:53:03 <Zakim> leaving.  As of this point the attendees have been katez, present, Rahim, giacomo-petri, Daniel, scotto, keithamus, siri, Francis_Storr
17:53:03 <Zakim> Zakim has left #aria
17:53:12 <jcraig> chair: spectranaut_
17:53:14 <jcraig> rrsagent, make minutes
17:53:15 <RRSAgent> I have made the request to generate https://www.w3.org/2024/06/27-aria-minutes.html jcraig
18:07:58 <jongund> jongund has joined #aria
20:40:52 <jongund> jongund has joined #aria
21:58:17 <jongund> jongund has joined #aria
23:16:25 <jongund> jongund has joined #aria
23:44:09 <jongund> jongund has joined #aria