16:57:06 RRSAgent has joined #aria 16:57:10 logging to https://www.w3.org/2024/10/24-aria-irc 16:57:10 RRSAgent, make logs Public 16:57:11 Meeting: ARIA WG 16:57:15 chair: ValerieYoung 16:57:23 agendabot, find agenda 16:57:23 spectranaut_, OK. This may take a minute... 16:58:02 Sorry, I did not find an agenda. 16:58:21 katez has joined #aria 16:58:38 present+ 16:59:00 agendabot, find agenda 16:59:00 spectranaut_, OK. This may take a minute... 16:59:01 Sorry, I did not find an agenda. 16:59:17 agendabot, find agenda 16:59:17 spectranaut_, OK. This may take a minute... 16:59:17 Sorry, I did not find an agenda. 17:00:42 scott has joined #aria 17:00:47 giacomo-petri has joined #aria 17:01:40 melsumner has joined #aria 17:02:04 zakk has joined #aria 17:02:27 present+ 17:02:31 filippo-zorzi has joined #aria 17:03:05 pkra has joined #aria 17:03:15 ChrisCuellar has joined #aria 17:03:18 present+ 17:03:21 present+ 17:03:25 present+ 17:03:37 present+ 17:03:41 present+ 17:03:56 agendabot, find agenda 17:03:56 jamesn, OK. This may take a minute... 17:03:57 Sorry, I did not find an agenda. 17:04:01 aaronlev has joined #aria 17:04:27 agenda: https://lists.w3.org/Archives/Public/public-aria/2024Oct/0015.html 17:04:27 jamesn, sorry, could not get https://lists.w3.org/Archives/Public/public-aria/2024Oct/0015.html (code 429). 17:05:06 StefanS has joined #aria 17:05:12 scribe+ 17:05:15 present+ 17:05:19 agenda+ [New Issue Triage](https://tinyurl.com/32y3ka5r) 17:05:19 agenda+ [New PR Triage](https://tinyurl.com/4yw4zvhu) 17:05:19 agenda+ [WPT Open PRs](https://bit.ly/wpt_a11y) 17:05:19 agenda+ [Deep Dive planning](https://bit.ly/aria-meaty-topic-candidates) 17:05:19 agenda+ [9.3 Presentational Roles Conflict Resolution does not consider custom element use cases](https://github.com/w3c/aria/issues/2303) 17:05:20 agenda+ [\[AriaNotify\] Is NotificationId the right name?](https://github.com/w3c/aria/issues/2329) 17:05:20 agenda+ [Inconsistent author/ua restrictions for columnheader / rowheader](https://github.com/w3c/aria/issues/2348) 17:05:20 agenda+ [Inconsistency in allowed uses of placeholder and aria-placeholder](https://github.com/w3c/aria/issues/2347) 17:05:21 agenda+ [Addition: selectedoption element](https://github.com/w3c/aria/pull/2344) 17:05:21 agenda+ [add mapping for html focusgroup attribute](https://github.com/w3c/html-aam/issues/565) 17:05:21 agenda+ [Stop automatically exposing details relation for figure -> figcaption](https://github.com/w3c/html-aam/issues/564) 17:05:25 zakim, next item 17:05:25 agendum 1 -- [New Issue Triage](https://tinyurl.com/32y3ka5r) -- taken up [from jamesn] 17:06:08 spectranaut_: core-aam#238 17:06:08 present+ 17:06:09 q+ 17:06:17 present+ 17:06:27 ... listing downstream AT support for AAMs. 17:06:33 Brett-Lewis has joined #aria 17:06:45 ... sounds interesting. would be good to get input. 17:07:10 jcraig: connects to the other issue 17:07:19 spectranaut_: ok, let's move to aria#2361 17:07:43 ... about shipping features with incomplete API mappings & AT support 17:07:50 jamesn: can we agenda this? 17:07:53 jcraig: sounds good. 17:07:55 q- 17:08:33 spectranaut_: to recap, this was triggered by colIndexText etc on Mac. 17:08:50 aaronlev: it has windows support. 17:09:13 nina has joined #aria 17:09:25 jcraig: we don't plan VO support. There's no webkit implementation right now for lack of OS API. 17:09:56 aaronlev: NVDA and JAWS support it. I think Firefox also has support. 17:10:15 jcraig: part of the concern came from WPT tests passing for chrome & firefox on Mac but it doesn't do anything. 17:10:22 q+ 17:10:39 ... that's somewhat of a limitation of the testing setup since it doesn't do anything. 17:10:54 q- 17:11:03 ... then there are notes on Apple specific in the issue. 17:11:15 spectranaut_: let's continue next week. 17:11:27 ... aria#2359 clarifying tables, grid, treegrid 17:11:45 q+ 17:11:49 scribe+ jcraig 17:11:53 ... from melsumner and scott conversation, let's agenda. 17:12:09 https://github.com/w3c/aria/issues/2359 17:12:19 q- 17:12:22 StefanS: grid allows for more. 17:12:37 spectranaut_: please add to the issue for discussion next week 17:12:42 scribe- 17:12:54 https://github.com/w3c/aria/issues/2357 17:13:00 spectranaut_: assign to daniel 17:13:10 Topic: Neew PRs 17:13:22 zakim, next itemnext 17:13:22 I don't understand 'next itemnext', jcraig 17:13:26 zakim, next item 17:13:26 agendum 2 -- [New PR Triage](https://tinyurl.com/4yw4zvhu) -- taken up [from jamesn] 17:13:30 sarah has joined #aria 17:13:36 present+ 17:13:41 https://github.com/w3c/aria/issues/2360 17:13:58 spectranaut_: scott filed update legend to provide name to optgroup 17:14:33 scott: legend element allowed as customizable select in HTML 17:14:42 open question in the PR 17:15:46 scott: what takes precedence... happy for reviews, but draft PR still pending the HTML discussion 17:16:38 keithamus: will review in the meantime 17:16:56 https://github.com/w3c/aria/issues/2358 17:17:26 jamesn: yes editorial. will merge after speaking with daniel 17:17:30 zakim, next item 17:17:30 agendum 3 -- [WPT Open PRs](https://bit.ly/wpt_a11y) -- taken up [from jamesn] 17:18:29 draft pr https://github.com/web-platform-tests/wpt/pull/48797 17:19:41 jcraig: Snuck in through DOM reflection tests mid-Interop 2024 17:19:48 zakim, next item 17:19:48 agendum 4 -- [Deep Dive planning](https://bit.ly/aria-meaty-topic-candidates) -- taken up [from jamesn] 17:21:17 spectranaut_: remove deepfdive tag from complex dashboard issue https://github.com/w3c/aria/issues/2162 17:21:59 aaronlev: need james teh for deep dive re: https://github.com/w3c/aria/issues/2162#issuecomment-2412328325 17:22:22 katez has joined #aria 17:23:08 no good time to deep dive with all: Australia, US, and EU 17:23:45 spectranaut_: discuss with Jamie... maybe have a two-part deep dive? 17:24:00 giacomo-petri: okay by me 17:24:23 spectranaut_: will coord with jamie and suggest a time 17:24:30 zakim, next item 17:24:30 agendum 5 -- [9.3 Presentational Roles Conflict Resolution does not consider custom element use cases](https://github.com/w3c/aria/issues/2303) -- taken up [from jamesn] 17:24:57 zakim, open item 4 17:24:57 agendum 4 -- [Deep Dive planning](https://bit.ly/aria-meaty-topic-candidates) -- taken up [from jamesn] 17:25:32 aaronlev: melsumner suggested deep dive on https://github.com/w3c/accname/issues/95 17:26:06 will discuss to consider a time at next week's meeting 17:26:15 zakim, next item 17:26:15 agendum 5 -- [9.3 Presentational Roles Conflict Resolution does not consider custom element use cases](https://github.com/w3c/aria/issues/2303) -- taken up [from jamesn] 17:26:58 jamesn: i'm assigned... it's on me in any case. aaronlev is there anything left to clarify from Chrome issues? 17:27:31 happy for others to take this work on too? 17:27:45 sarah: are there custom elements defined in AAMs? 17:27:59 scott: identified as generic 17:28:10 need a change if moving them to none 17:28:33 jamesn: need a way to account for conflict resolution 17:28:41 keithamus: where is that defined 17:28:54 jamesn: hopefully linkable to html def 17:29:17 scott: make them "silly `role=none`s" 17:29:21 DougG has joined #aria 17:29:27 wrapper is none or generic 17:29:45 q+ 17:29:52 they can either be something or contain other things 17:30:42 keithamus: can be confusing. is it an autonomous element with functionality, or just a silly div 17:31:00 q? 17:31:30 scott: you're spot on... in some cases, if you want attrs to the internals, whether light dom or shadow dom... 17:32:42 some attributes are ignored, but some are not... e.g. "gerrymandered" attrs 17:33:06 ack sarah 17:33:20 q- 17:33:35 sarah: i volunteer to make the AAM PR... and help jamesn with presentational roles conflict PR 17:34:19 aaronlev: write the way you think it should work (not necessarily based on chrome implementation) and implementors will review 17:34:34 zakim, next issue 17:34:34 I don't understand 'next issue', jcraig 17:34:40 zakim, next item 17:34:40 agendum 6 -- [\[AriaNotify\] Is NotificationId the right name?](https://github.com/w3c/aria/issues/2329) -- taken up [from jamesn] 17:35:28 DougG: keithamus, clay, and doug are here 17:35:52 q+ 17:35:52 q? 17:35:54 keithamus: name "notificationID in contention... proposing type 17:35:59 ack sarah 17:36:00 q+ 17:36:24 sarah: did we resolve whether this would be part of the initial v1? 17:37:08 keithamus: wanted enumeration of category names, and what would validation look like? unsure, so motivated to not ship it immediately. 17:37:28 happy with a "fast follow" (1.01 release) 17:37:35 ack me 17:38:05 scribe+ 17:38:38 keithamus: I think the functionality is pretty well defined in that we know what we're presenting to AT - a stable identifier so they can reason on the type of message. 17:38:51 ... open question is: how useful is that? We're discussing this with AT and others. 17:39:12 q? 17:39:15 ... semantics around the value are in the air but that I think that doesn't preclude discussing the name. Letter vs spirit of law. 17:39:28 q+ to bikeshed notificationClassName which does not imply enumerated value list 17:39:30 ack jcraig 17:39:30 jcraig, you wanted to bikeshed notificationClassName which does not imply enumerated value list 17:39:30 ... a fixed identifier that's sent to provide AT 17:39:30 ack me 17:39:38 Adam_Page has joined #aria 17:39:58 jcraig: I wasn't aware that this identifier was considered for something like an enumerated list of category names. 17:40:10 ... sounds like you want it to be an enumerated list. 17:40:30 present+ 17:40:42 ... what if we use notification class name 17:40:56 q+ 17:41:06 q+ to see if we can get consensus about whether the option needs a “notification” prefix 17:41:06 ... it seemed an open-ended thing that authors would define. ID would seem to be a unique thing. 17:41:12 ... but it sounds like it's somewhere in between. 17:41:37 keithamus: that sounds about right. It's supposed to be heavily re-usable. 17:42:05 ... we're currently categorizing apps to figure out if they fit into a category for which we could prescribe. 17:42:34 ... it might not be too prescriptive. But we're hoping to get some level of collaboration between authors and AT to work out. 17:42:46 ... so class name seems like a reasonable suggestion. 17:42:50 q+ to discuss the instagram an zoom notifications list 17:43:14 ... to be clear it's a scalar. 17:43:17 ack keithamus 17:43:17 ack keithamus 17:43:52 clay: do we need notification to be in there? 17:44:05 ... could it be notification priority / interrupt / etc 17:44:17 ack smockle 17:44:17 smockle, you wanted to see if we can get consensus about whether the option needs a “notification” prefix 17:44:20 ... is there some other use of "type" that people are concerned about? 17:44:34 ack jcraig 17:44:34 jcraig, you wanted to discuss the instagram an zoom notifications list 17:44:35 jcraig: I don't have a problem nixing that. 17:44:44 sarah has joined #aria 17:44:47 +1 to "type" 17:44:51 ... but I wanted to talk about instagram and zoom notification use cases. 17:45:00 ... in the f2f there were different goals from different stakeholdesr. 17:45:22 ... whether we want AT or platform APIs do the notification management while apps send as much as they want. 17:45:36 ... or if we want the apps to manage. 17:46:09 ... in the draft doc we had a section on this. zoom is short (now?) instagram still quite long. 17:46:22 q+ 17:46:34 ... I don't think that level of granularity has a place in the API. But others in the room had differing opinions. 17:46:49 ack sarah 17:46:53 ... if the latter remains a goal, then I think it needs to be broader. 17:47:07 qv? 17:47:15 sarah: it would help to understand what screenreaders might do here. 17:47:38 ... at tpac, things like earcons came up. jaws customizations per app came up. 17:47:48 ... I would appreciate this kind of a list if we have it. 17:47:50 q+ 17:48:12 ack aaronlev 17:48:38 aaronlev: radical idea: instead of making it very wide and then having to control a potential mess, what if we create a group to brainstorm as many different class names as we can, e.g., in a wiki. 17:48:51 ... then give us a couple of months to discuss those. 17:48:53 q+ 17:49:24 q+ to use "incoming chat" as the straw man example 17:49:30 ... we'll know it won't be everything but we'll know we support those in v1. Then if people come with additional use cases, we can open it up widely. 17:49:42 ... that's easier than boiling it down later. 17:49:54 ack keithamus 17:50:04 keithamus: that's something we're after right now. 17:50:40 ... starting with our own at github. Spent hours to just start with our, asked other teams. 17:51:11 ... to recap sarah, some kind of list so we know what we're talking about before naming this. That's a good takeaway. 17:51:40 jcraig: was using "incoming chat" as as strawman. If we take chat applications, there'll be hundreds. 17:51:57 ... but if github has over 800 types, how much of a chance do we have to come up with a taxonomy. 17:52:09 aaronlev: but would you agree it's useful to do the exercise? 17:52:28 jcraig: yes. just the github list would be valuable in say a gist. 17:52:37 keithamus: right. I can give a few now if that helps. 17:52:52 qv? 17:53:15 ack jcraig 17:53:15 jcraig, you wanted to use "incoming chat" as the straw man example 17:53:31 ... 4 come to mind immediately. 17:53:33 ... dynamic forms, e.g., search. 15 search results. could be aria-live but we have reasons not to. 17:53:40 ... for soft navigations we announce the title 17:53:56 scott has joined #aria 17:54:04 ... select range of checkbox, e.g., issue list. top checkbox selecting 25, announces that. 17:54:27 q? 17:54:32 ... we don't announce receiving notification but if you focus it, the computed label is the number of notification. 17:54:42 jcraig: that's github notifications? 17:54:51 keithamus: yes. that's our intenal. 17:55:09 jcraig: seems like those might boil down? I heard something like status change, count change. 17:55:25 q+ 17:55:27 aaronlev: yes that's what I had in mind. 17:55:35 ... maybe it's 20 instead of 800. 17:55:44 q+ 17:55:55 keithamus: Right. majority is status or count. Some others might fall out of this. 17:56:09 ... then there's live updates, e.g., when a comment comes in. 17:56:20 ... might be we want something more specific there. 17:56:36 ... that's something we've discussed quite a bit, figuring out the direction. 17:57:14 q+ to compare to system notifications levels of control.... per app/domain allow/deny and where/how/persistence.... all "types" or "classes" are left up to the apps' settings. 17:57:14 aaronlev: I could imagine some might feed back into other aria discussions, e.g., characters left for input of post. 17:57:41 zakim, close the queue 17:57:41 ok, spectranaut_, the speaker queue is closed 17:58:12 sarah: one other piece of information I'd welcome is now just how authors are using notifications but also how AT users, incl. speech and braille, would want to receive them, e.g., mute some. 17:58:30 ... would that be served by the type string or, as I think it's right now, by the text string. 17:59:05 keithamus: one of problems is that the strings change, counts or "message from X". 17:59:09 ack me 17:59:09 jcraig, you wanted to compare to system notifications levels of control.... per app/domain allow/deny and where/how/persistence.... all "types" or "classes" are left up to the 17:59:12 ... apps' settings. 17:59:21 sarah: right, it's regexping right now 17:59:37 jcraig: I think this work will touch on what went wrong with aria-live. 18:00:05 ... comparing that to system notifications: users can block entire app, some, does it go away, persist. 18:00:13 ... beyond that it's business logic of the app. 18:00:23 ... instagram has 30/40 types you can shut off individually. 18:00:41 ... so I agree we should talk to AT users. 18:00:52 ... anecdata is "let me turn them off" 18:01:08 ... but having granular control seems like key here. 18:01:30 pkra has joined #aria 18:01:34 zakim, end meeting 18:01:34 As of this point the attendees have been katez, zakk, hdv, ChrisCuellar, pkra, filippo-zorzi, giacomo-petri, StefanS, smockle, scott, sarah, Adam_Page 18:01:36 RRSAgent, please draft minutes v2 18:01:37 I have made the request to generate https://www.w3.org/2024/10/24-aria-minutes.html Zakim 18:01:44 I am happy to have been of service, pkra; please remember to excuse RRSAgent. Goodbye 18:01:44 Zakim has left #aria 18:01:56 s/having granular control /having granular control in the website's settings (not the screen reader settings) / 18:10:53 present+ 18:11:06 rrsagent, make minutes 18:11:07 I have made the request to generate https://www.w3.org/2024/10/24-aria-minutes.html jcraig 18:11:57 s/Topic: Neew PRs// 18:12:09 rrsagent, make minutes 18:12:11 I have made the request to generate https://www.w3.org/2024/10/24-aria-minutes.html jcraig 18:57:41 scott has joined #aria 19:49:37 ChrisCuellar has joined #aria 23:16:29 ChrisCuellar has joined #aria