17:00:58 <RRSAgent> RRSAgent has joined #aria
17:01:02 <RRSAgent> logging to https://www.w3.org/2023/08/10-aria-irc
17:01:02 <Zakim> RRSAgent, make logs Public
17:01:03 <Zakim> please title this meeting ("meeting: ..."), jamesn
17:01:03 <pkra> pkra has joined #aria
17:01:06 <jamesn> meeting: ARIA WG
17:01:13 <pkra> present+
17:01:14 <jamesn> agendabot, find agenda
17:01:14 <agendabot> jamesn, OK. This may take a minute...
17:01:16 <agendabot> agenda: https://www.w3.org/events/meetings/ecffaf8b-8aa7-4acc-b238-6088a86cf12f/20230810T130000/
17:01:16 <agendabot> clear agenda
17:01:16 <agendabot> agenda+ -> New Issue Triage https://bit.ly/43VhGRq
17:01:16 <agendabot> agenda+ -> New PR Triage https://bit.ly/3DJr7ZD
17:01:17 <agendabot> agenda+ -> WPT Open PRs https://bit.ly/ARIA-WPT
17:01:20 <agendabot> agenda+ -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates
17:01:22 <agendabot> agenda+ -> TPAC Candidate Issues https://bit.ly/aria-tpac-candidates
17:01:25 <agendabot> agenda+ -> Discussion tracking for ARIA Notification proposal https://github.com/w3c/aria/issues/1957
17:02:06 <Adam_Page> present+
17:02:16 <jamesn> present+
17:02:21 <jamesn> chair: JamesNurthen
17:02:52 <spectranaut_> present+
17:02:55 <jocelyn> jocelyn has joined #aria
17:04:01 <Doug> Doug has joined #aria
17:04:40 <pkra> scribe pkra
17:04:40 <pkra> scribe: pkra
17:04:41 <pkra> zakim, next item
17:04:41 <Zakim> agendum 1 -- -> New Issue Triage https://bit.ly/43VhGRq -- taken up [from agendabot]
17:05:08 <pkra> jamesn: no new issues
17:05:11 <pkra> zakim, close item
17:05:11 <Zakim> I don't understand 'close item', pkra
17:05:14 <pkra> zakim, close this item
17:05:14 <Zakim> agendum 1 closed
17:05:15 <Zakim> I see 5 items remaining on the agenda; the next one is
17:05:15 <Zakim> 2. -> New PR Triage https://bit.ly/3DJr7ZD [from agendabot]
17:05:19 <pkra> zakim, next item
17:05:19 <Zakim> agendum 2 -- -> New PR Triage https://bit.ly/3DJr7ZD -- taken up [from agendabot]
17:06:16 <CurtBellew> CurtBellew has joined #aria
17:06:24 <pkra> jamesn: aria#1993 is about improving contributors data in document.
17:06:51 <pkra> ... better than the fixed list. It seems like a good selection. Based on contributions to the repository.
17:07:08 <pkra> ... contributions will be spec-specific. The list of participants will remain.
17:07:40 <myasonik> myasonik has joined #aria
17:07:45 <pkra> ... we might want to have the evergreen specs simply point to the WG member list
17:07:57 <pkra> spectranaut_: unfortunate not to have fly-by contributors
17:08:03 <myasonik> present+
17:08:13 <pkra> jamesn: if you have any comments, please let us know.
17:08:29 <pkra> ... aria#1991 matching braillelabel prohibiting
17:08:35 <pkra> jamescraig: will review
17:09:11 <pkra> ... we were discussing this last week and want to make sure we don't miss interesting edge cases
17:09:51 <pkra> jamesn: thanks. will try to get Aaron or someone from Chrome with braille path experience.
17:10:54 <StefanS> StefanS has joined #aria
17:11:00 <StefanS> present+
17:11:15 <BGaraventa> BGaraventa has joined #aria
17:11:32 <pkra> zakim, next item
17:11:32 <Zakim> agendum 3 -- -> WPT Open PRs https://bit.ly/ARIA-WPT -- taken up [from agendabot]
17:12:01 <pkra> spectranaut_: I'm handling the core-aam ones.
17:12:06 <BGaraventa> present+ bgaraventa
17:13:34 <pkra> jcraig: generic test is a bigger one. many reviewers already.
17:13:36 <pkra> ... lots of notes
17:13:46 <pkra> ... hopefully those make it easy to review
17:14:04 <pkra> jamesn: my interpretation was that this comes from the different platforms
17:14:16 <pkra> ... having different names?
17:14:43 <pkra> jcraig: yes. we accepted to avoid churn.
17:15:23 <pkra> ... core-aam tests are Val's
17:15:46 <pkra> ... I'll review howard's - 1 review is enough. Rahim maybe too?
17:16:40 <pkra> ... fallback roles. pretty straight forward.
17:16:56 <pkra> ... has reviewers but any are welcome
17:17:07 <pkra> jamesn: more than one is good, especially if complex
17:17:12 <CurtBellew> present+
17:17:43 <pkra> ... can we remove manual tests so we can ignore them in query?
17:17:54 <pkra> spectranaut_: yes. but you won't see them often once this batch is merged
17:18:53 <pkra> jcraig: one very old manual one
17:19:04 <pkra> spectranaut_: not sure it's worth maintaining some of these
17:19:07 <jongund> jongund has joined #aria
17:19:25 <pkra> ... other old ones back to spectranaut
17:20:01 <pkra> ... and that's it.
17:20:05 <pkra> zakim, next item
17:20:05 <Zakim> agendum 4 -- -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates -- taken up [from agendabot]
17:20:19 <pkra> jamesn: let's combine with TPAC planning.
17:21:06 <pkra> ... does anyone want to do either of these? (hidden really hidden, windows/mac implicit roles)
17:21:42 <pkra> ... I'll add them to TPAC in any case.
17:22:01 <pkra> jcraig: windows/mac discussion might be easier at TPAC
17:22:34 <pkra> zakim, next item
17:22:34 <Zakim> agendum 5 -- -> TPAC Candidate Issues https://bit.ly/aria-tpac-candidates -- taken up [from agendabot]
17:22:57 <pkra> jamesn: 11 potential items
17:23:23 <pkra> ... chairs will plan next week
17:23:36 <pkra> ... if there's anything you want to discuss, you need to label it F2F candidate.
17:23:57 <pkra> ... if you're not at TPAC but you want to attend, please comment with location so we can aim for reasonable times for you.
17:24:51 <pkra> jcraig: I wanted to pitch a break out session with browser testing tool, on AOM issue. I'll file a new issue pointing to AOM issue.
17:25:40 <pkra> mattking: could also include AT driver?
17:26:09 <pkra> ... I think that would be good.
17:26:20 <spectranaut_> list of registered: https://www.w3.org/register/tpac2023/registrants#meeting-198
17:27:34 <pkra> jamesn: let's see who's coming.
17:30:03 <pkra> ... again, please add items for TPAC agenda
17:36:10 <Matt_King> Matt_King has joined #aria
17:36:24 <Matt_King> present+
17:36:28 <pkra> zakim, next item
17:36:28 <Zakim> agendum 6 -- -> Discussion tracking for ARIA Notification proposal https://github.com/w3c/aria/issues/1957 -- taken up [from agendabot]
17:36:52 <jongund> jongund has joined #aria
17:37:09 <pkra> Doug: "using arrays confusion". Right now I don't think it makes sense.
17:37:19 <pkra> ... right could be on any element, presented as array
17:37:28 <pkra> ... then could do things, e.g., flush pending.
17:37:49 <pkra> ... browsers won't be able to do much with this as soon as it went to AT
17:38:07 <pkra> ... so probably the browser passes it to API, then array probably only happens on the AT level
17:38:16 <pkra> ... so array seems wrong. grouping is probably still helpful.
17:38:21 <jamesn> q?
17:38:27 <pkra> ... if people agree, then what should be done.
17:39:14 <pkra> mattking: on the app side, if there's a situation where it's aware of a lot of notifications and you want to manage this
17:39:34 <pkra> ... do we need something in the API that would help with queue management
17:39:45 <pkra> ... e.g., chat app, 15-20 notifications, on different threads
17:40:02 <pkra> ... and app wants to provide feature to manage that.
17:41:03 <pkra> Doug: on windows, platform notification API, e.g., progress bar ticking away. if everytime the percentage changes, the synthesizer would be jammed with starting sound.
17:41:27 <pkra> ... so instead it allows not constantly interrupt.
17:41:41 <pkra> ... allowing AT to complete voicing and then take the next latest one.
17:41:45 <pkra> ... but that's really on the AT side.
17:42:26 <pkra> ... I'd imagine AT allowing users to prioritize notifications. Not sure how often we'll see that.
17:42:55 <pkra> mattking: right. I have definitely run into it. But I can see how the API is treated as a dispatcher.
17:43:07 <pkra> Doug: yes, I can imagine that users set verbosity to control.
17:43:22 <pkra> mattking: see that in meetings. joining, leaving, raising hand, chat etc
17:43:39 <pkra> ... seems like the app could have verbosity setting
17:43:51 <pkra> Doug: we discuss having the burden on the app side or the AT side
17:44:03 <jamesn> q+
17:44:10 <pkra> ... hard to make it generic.
17:44:51 <jamesn> ack me
17:45:07 <pkra> jamesn: I'd lean towards doing a lot of this in the AT rather than the app
17:45:27 <pkra> ... almost feels like you'd want priorities. E.g., starting leaving at beginning on meeting.
17:45:49 <pkra> ... would want that but not have to do that in the settings of the app
17:46:18 <pkra> mattking: I think that AT could only do the big hammer. The app would have to do the detailed ones.
17:46:30 <pkra> jamesn: but I'd hope they can handle the most common use cases.
17:46:44 <pkra> ... if we say apps have to do this, we may miss out on a lot of usefulness
17:47:14 <pkra> mattking: not saying they have to but an option. E.g., workout app I want it speaking, control interval, verbosity etc.
17:47:55 <pkra> zakim, end meeting
17:47:55 <Zakim> As of this point the attendees have been pkra, Adam_Page, jamesn, spectranaut_, myasonik, StefanS, bgaraventa, CurtBellew, Matt_King
17:47:57 <Zakim> RRSAgent, please draft minutes
17:47:58 <RRSAgent> I have made the request to generate https://www.w3.org/2023/08/10-aria-minutes.html Zakim
17:48:05 <Zakim> I am happy to have been of service, pkra; please remember to excuse RRSAgent.  Goodbye
17:48:05 <Zakim> Zakim has left #aria
18:06:50 <bkardell_> bkardell_ has joined #aria
18:31:17 <jongund> jongund has joined #aria
18:49:20 <jongund> jongund has joined #aria