16:58:14 RRSAgent has joined #aria 16:58:18 logging to https://www.w3.org/2024/05/30-aria-irc 16:58:18 RRSAgent, make logs Public 16:58:19 Meeting: ARIA WG 16:58:27 agendabot, find agenda 16:58:27 jamesn, OK. This may take a minute... 16:58:28 agenda: https://www.w3.org/events/meetings/2b57854a-65cb-421e-b9e0-f9a8da31f160/20240530T130000/ 16:58:28 clear agenda 16:58:28 agenda+ -> New Issue Triage https://bit.ly/4aCpzyr 16:58:28 agenda+ -> New PR Triage https://bit.ly/3x18ZdJ 16:58:30 agenda+ -> WPT Open PRs https://bit.ly/wpt_a11y 16:58:33 agenda+ -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates 16:58:35 agenda+ Additional editor of HTML-AAM - -> Rahim https://github.com/rahimabdi 16:58:38 agenda+ -> CSS: handing the a11y of anchor positioning https://github.com/w3c/html-aam/issues/545 16:58:41 agenda+ -> Issue: CSS Highlights Not Clearly Documented in AAM https://github.com/w3c/core-aam/issues/226 16:58:44 agenda+ Triage Issues... 16:59:08 spectranaut_ has joined #aria 16:59:17 agenda? 16:59:44 Adam_Page has joined #aria 17:00:34 present+ 17:00:50 Francis_Storr has joined #aria 17:01:01 present+ 17:01:06 present+ 17:01:38 aardrian has joined #aria 17:01:39 ray-schwartz has joined #ARIA 17:01:41 scribe: Adam_Page 17:01:43 present+ 17:01:50 zakim, next item 17:01:51 agendum 1 -- -> New Issue Triage https://bit.ly/4aCpzyr -- taken up [from agendabot] 17:02:15 giacomo-petri has joined #aria 17:02:23 present+ 17:02:26 aria#2234 17:02:36 spectranaut_: JSON roleInfo.js not updated 17:02:37 present+ 17:02:58 pkra: these only get updated on recommendations 17:03:13 ... but we can do them more efficiently after PR 17:03:22 jamesn: is it possible to publish as part of TR? 17:03:31 ... if so, that could be the versioned copy 17:03:47 spectranaut_: let‘s discuss in editor’s meeting 17:03:57 spectranaut_: aria#2233 17:04:08 jamesn: this seems like a dupe 17:04:55 ... is it aria#1839 ? 17:05:08 spectranaut_: will you confirm that this is a dupe, giacomo-petri? 17:05:14 giacomo-petri: yes 17:05:32 s/aria#1839/aria#1389/ 17:05:32 pkra has joined #aria 17:05:33 spectranaut_: aria#239 17:05:37 present+ 17:05:41 benb has joined #aria 17:05:45 present+ 17:06:00 siri has joined #aria 17:06:45 aardrian: Chrome may be changing — will dump link into this issue 17:09:14 There is recent activity on this Chromium issue, though not sure it helps: 17:09:14 https://issues.chromium.org/issues/40343523 17:09:57 scotto: the CSS WG needs more a11y participation 17:10:19 s/scotto/sohara/ 17:10:26 q+ 17:10:37 jamesn: it’s hard for them to know when a particular issue has an a11y impact 17:10:43 present+ 17:11:12 aardrian: I volunteer 17:11:58 I appreciate Adam simplified my response. 17:12:10 spectranaut_: core-aam#234 17:13:05 Rahim: do we have documentation on the relationship between content in the DOM and the a11y tree? 17:13:26 jamesn: it’s too difficult to document it in a standardized way for all browsers 17:14:44 spectranaut_: core-aam#234 is editorial 17:14:59 spectranaut_: then we have some follow-up tasks for the monorepo migration 17:15:19 spectranaut_: aria#2232 17:15:39 ... previews will take a little longer to load, but we’ll be fixing that soon 17:15:48 ... skipping over some more editorials 17:16:11 ... pkra’s made an issue for editors to review and finalize 17:16:27 ... another editorial that we‘re trying to remove references to custom css files 17:16:40 spectranaut_: aria#2225 17:17:14 giacomo-petri: ARIA spec is clear from a user agent perspective, but not for authros 17:17:19 s/authros/authors/ 17:17:48 ... when IDREF references an invalid ID 17:18:34 ... I recommend it is important to clarify that there is an author issue if the ID is missing or has not matching element in the page 17:18:48 Rahim: I raised a similar issue on `undefined` and see some overlap 17:18:58 ... how an author provides or doesn’t provide a value 17:19:03 ... empty string, undefined, null, etc. 17:19:12 ... there’s ambiguity in the spec on those assignments 17:19:20 spectranaut_: I’ll link that 17:19:39 ... do these proposals conflict with that? 17:20:00 Rahim: the empty string case is clearly specified, IMO 17:20:33 keithamus: you said there’s a discrepancy between undefined and null. I’m curious about that 17:20:48 ... if it’s serialized HTML, it has no concept of undefined or null 17:21:09 spectranaut_: check out Rahim’s aria#2176 and aria#2177 17:21:11 zakim, next item 17:21:11 I see a speaker queue remaining and respectfully decline to close this agendum, Adam_Page 17:21:17 q? 17:21:20 ack Rahim 17:21:22 zakim, next item 17:21:22 agendum 2 -- -> New PR Triage https://bit.ly/3x18ZdJ -- taken up [from agendabot] 17:21:29 sarah has joined #aria 17:21:34 TheoHale has joined #aria 17:21:41 spectranaut_: a ton of PRs moving to the ARIA spec 17:21:43 present+ 17:21:59 ... nothing to discuss 17:22:01 zakim, next item 17:22:01 agendum 2 was just opened, Adam_Page 17:22:05 zakim, close this item 17:22:05 agendum 2 closed 17:22:06 I see 6 items remaining on the agenda; the next one is 17:22:06 3. -> WPT Open PRs https://bit.ly/wpt_a11y [from agendabot] 17:22:11 zakim, next item 17:22:11 agendum 3 -- -> WPT Open PRs https://bit.ly/wpt_a11y -- taken up [from agendabot] 17:22:28 Present+ 17:22:56 zakim, next item 17:22:56 agendum 3 was just opened, Adam_Page 17:22:58 zakim, close this item 17:22:58 agendum 3 closed 17:23:01 I see 5 items remaining on the agenda; the next one is 17:23:01 4. -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates [from agendabot] 17:23:01 zakim, next item 17:23:01 agendum 4 -- -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates -- taken up [from agendabot] 17:23:18 spectranaut_: any deep dives to schedule? 17:23:37 aardrian: I missed the ariaNotify and want to catch up. How can I? 17:23:49 jamesn: please send me an email and I’ll send you the recording 17:23:57 ... and don’t distribute 17:24:05 daniel-montalvo: you may need Google Drive access 17:24:10 ... just request it if true 17:24:31 zakim, close this item 17:24:31 agendum 4 closed 17:24:32 I see 4 items remaining on the agenda; the next one is 17:24:32 5. Additional editor of HTML-AAM - -> Rahim https://github.com/rahimabdi [from agendabot] 17:24:34 zakim, next item 17:24:34 agendum 5 -- Additional editor of HTML-AAM - -> Rahim https://github.com/rahimabdi -- taken up [from agendabot] 17:24:41 jamesn can you send me the link to the meeting/deep dive. 17:25:22 spectranaut_: please everyone welcome Rahim as a new HTML-AAM editor! 17:25:30 zakim, next item 17:25:30 agendum 5 was just opened, Adam_Page 17:25:38 zakim, close this item 17:25:39 agendum 5 closed 17:25:39 I see 3 items remaining on the agenda; the next one is 17:25:39 6. -> CSS: handing the a11y of anchor positioning https://github.com/w3c/html-aam/issues/545 [from agendabot] 17:25:41 zakim, next item 17:25:41 agendum 6 -- -> CSS: handing the a11y of anchor positioning https://github.com/w3c/html-aam/issues/545 -- taken up [from agendabot] 17:25:53 TheoHale: please send me an email 17:26:29 sohara: we don’t have a place to to outline the CSS a11y semantics 17:26:42 ... anchor positioning is a new feature meant to be used for popovers 17:26:57 ... currently, position:fixed in top layer of browser and you have to use JS to position it correctly 17:27:08 ... this CSS property will associate the elements together so you don’t have to micromanage the location 17:27:32 ... we had talked about there being an `aria-details` relationship with this property 17:27:41 ... so that if someone used it on a non-popover element 17:27:57 ... we could add an aria relationship to communicate that 17:28:13 ... we don’t have CSS-AAM, so maybe we can carve out a section in HTML-AAM 17:28:18 ... after the monorepo migration 17:28:24 spectranaut_: any questions? 17:28:34 ... is there anything controversial here? 17:28:43 aardrian: not for us, but need to read it 17:28:56 ... may prove challenging for devs who are not familiar with surrounding concerns 17:29:17 sohara: part of this is making sure there’s a minimum layer of a11y 17:29:22 aardrian: predictable, if nothing else 17:29:27 sohara: please poke at it 17:29:31 ... post in the issue 17:29:43 ... I or aaronlev will respond 17:30:00 spectranaut_: we spitballed making a CSS-AAM but ended up decided to stick with HTML-AAM 17:30:03 sohara: for now 17:30:15 ... might still be a good idea to spin up, but then definitely need a a bridge to the CSS WG 17:30:26 s/a a/a/ 17:31:29 zakim, next item 17:31:29 agendum 7 -- -> Issue: CSS Highlights Not Clearly Documented in AAM https://github.com/w3c/core-aam/issues/226 -- taken up [from agendabot] 17:31:47 spectranaut_: may not be anything further to discuss here 17:31:51 TheoHale: I need to do more work here 17:32:07 ... but this is a case where CSS did do some good a11y work, but didn’t document it 17:32:21 spectranaut_: should this issue actually be in HTML-AAM? 17:32:42 ... I’ll move it there 17:32:57 zakim, next item 17:32:57 agendum 8 -- Triage Issues... -- taken up [from agendabot] 17:34:16 spectranaut_: aria#482 from Nov 2016 (!!!) 17:34:26 jamesn: we don’t need a feature for the href attribute 17:34:38 pkra: this ties into attribute parity 17:34:53 ... is this something that will come up again? 17:35:06 ... should we have a marker for saying “maybe, in the future, but right now, no”? 17:35:07 q+ 17:35:17 ... but I do support closing this 17:35:39 jamesn: why would anyone ever want to set a different href for the a11y api? 17:36:12 sohara: one use case I can see, and this is not a priority... 17:36:16 ... someone makes div role= 17:36:18 apologies for jumping the queue! 17:36:35 ... someone makes div[role="link"] and wants to set a href 17:36:42 q+ 17:37:25 ... they wanted to make it as close to a hyperlink as possible, but don’t want to use href 17:37:49 ... most people using role="link" are using tons of JS, and this wouldn’t help them 17:38:08 ack sarah 17:38:12 sarah: I agree with pkra 17:38:22 ... “in theory, this might be needed, but it isn’t now” 17:38:44 ... in sohara’s example, other functionality is sabotaged, like opening link in new window from context menu 17:39:16 spectranaut_: so we need to make it easy to find for someone who might log a similar issue in the future 17:39:22 ... so have a label like “not a priority” 17:40:02 aardrian: I would still close it 17:40:25 spectranaut_: let’s pick a label 17:41:50 ... let’s go with "wontfix" 17:42:47 present+ Daniel 17:43:02 spectranaut_: aria#483 17:43:57 pkra: is this for html-aam? 17:44:07 spectranaut_: “not mapped” 17:44:13 pkra: is there something to map it to? 17:44:31 spectranaut_: we’ll close as "wontfix" 17:44:43 spectranaut_: aria#484 17:44:50 jamesn: close it 17:45:04 spectranaut_: closed 17:45:18 spectranaut_: aria#517 17:45:40 pkra: blocked by jcraig’s comments 17:45:41 q+ 17:46:04 sohara: there are platform roles now 17:46:20 ... I don’t think we need this 17:46:25 jamesn: it was only ever for test reasons 17:46:44 q- 17:46:47 pkra: "wontfix" 17:48:18 jamesn: we could just use aria-roledescription, for example 17:48:25 spectranaut_: closed as "wontfix" 17:48:40 ack sohara 17:48:51 aardrian has joined #aria 17:48:57 spectranaut_: aria#521 17:48:57 present+ 17:49:09 ... roles for drag and drop 17:49:57 q+ 17:49:57 TheoHale: is it actually helpful information for AT users? 17:50:15 q- 17:50:17 sohara: propose closing 17:50:47 spectranaut_: closing as "wontfix" 17:50:57 ... aria#524 17:51:05 ... alllow aria-setsize on container elements 17:51:12 q+ 17:51:28 sarah: I can speak about this 17:51:46 ... maybe this can be folded into the other PR 17:51:51 ... for toolbars 17:52:01 ... ref either aria#2158 or aardrian’s PR 17:52:07 ... aria#2170 17:52:25 ... so we could close this in favor of the open PR 17:52:32 ack me 17:52:33 spectranaut_: closed 17:52:54 spectranaut_: aria#542 17:53:05 ... new attribute aria-readonly for role=form 17:53:16 q+ 17:53:52 sohara: I’d argue we don’t need this, it should start in HTML first 17:53:57 ... and HTML doesn’t allow a form to be readonly 17:54:03 ... recommend closing 17:54:06 +1 to scott 17:54:15 ... if you want it to be readonly, just use text 17:54:22 q+ 17:54:24 ... or readonly inputs 17:54:37 q+ 17:54:44 giacomo-petri: I have an example 17:54:48 ... checkboxes don’t support readonly 17:55:06 ... in learning use cases, they sometimes want to show a checkbox but in a readonly state 17:55:19 ... and disabled doesn’t work well 17:55:40 ... edge case scenario 17:55:43 ack giacomo-petri 17:55:55 q+ 17:55:57 spectranaut_: maybe this should be pushed into HTML 17:56:23 ack sohara 17:56:53 jamesn: I agree; there are already options to make it readonly 17:57:09 spectranaut_: closed 17:57:29 spectranaut_: aria#574 17:57:43 ... role="switch" should have additional attr `aria-valuetext` 17:58:00 sohara: I have a dupe for this 17:58:30 https://github.com/w3c/aria/issues/2085 17:58:52 spectranaut_: will close this as a dupe, since there’s more chatter on the new one 17:59:18 spectranaut: we closed every issue we looked at! 17:59:37 zakim, end meeting 17:59:37 As of this point the attendees have been Rahim, Francis_Storr, sohara, Adam_Page, giacomo-petri, ray-schwartz, pkra, benb, keithamus, TheoHale, CoryJoseph, Daniel, aardrian 17:59:40 RRSAgent, please draft minutes v2 17:59:41 I have made the request to generate https://www.w3.org/2024/05/30-aria-minutes.html Zakim 17:59:48 I am happy to have been of service, Adam_Page; please remember to excuse RRSAgent. Goodbye 17:59:48 Zakim has left #aria