17:00:22 RRSAgent has joined #aria 17:00:27 logging to https://www.w3.org/2024/07/25-aria-irc 17:00:27 RRSAgent, make logs Public 17:00:28 Meeting: ARIA WG 17:00:37 jamesn has joined #aria 17:00:40 agendabot, find agenda 17:00:40 spectranaut_, OK. This may take a minute... 17:00:41 agenda: https://www.w3.org/events/meetings/2b57854a-65cb-421e-b9e0-f9a8da31f160/20240725T130000/ 17:00:41 clear agenda 17:00:41 agenda+ -> New Issue Triage https://bit.ly/3ydLizB 17:00:41 agenda+ -> New PR Triage https://bit.ly/3zVR35B 17:00:44 agenda+ -> WPT Open PRs https://bit.ly/wpt_a11y 17:00:46 agenda+ -> Deep Dive/TPAC planning https://bit.ly/aria-meaty-topic-candidates 17:00:48 agenda+ -> Clarify spec treatment of value "undefined" (i.e., as equivalent to invalid value, initial condition for state/property usage) https://github.com/w3c/aria/issues/2280 17:00:52 agenda+ -> CSS text-transform should not affect computed name https://github.com/w3c/accname/issues/239 17:00:55 agenda+ -> Values table for aria-multiselectable/aria-current are missing "undefined" https://github.com/w3c/aria/issues/2176 17:00:58 agenda+ -> Discussion tracking for ARIA Notification proposal - Interrupt and Flushing and Understandability https://github.com/w3c/aria/discussions/1958#discussioncomment-9653385 17:01:23 present+ 17:02:11 katez has joined #aria 17:02:38 present+ 17:02:48 present+ 17:03:29 Mario has joined #aria 17:04:36 CurtBellew has joined #aria 17:04:47 giacomo-petri has joined #aria 17:04:50 present+ 17:04:52 sohara has joined #aria 17:04:58 present+ 17:04:59 scribe: jamesn 17:05:17 scribe+ 17:05:25 zakim, next item 17:05:25 agendum 1 -- -> New Issue Triage https://bit.ly/3ydLizB -- taken up [from agendabot] 17:06:04 spectranaut_: Will handle the prettier error in the editors meeting 17:06:14 https://github.com/w3c/accname/issues/244 17:06:26 Siri has joined #aria 17:06:27 spectranaut_: there is some discussion and a suggestion 17:06:29 present+ 17:06:48 bryan: should probably be discussed 17:07:11 spectranaut_: would be easier to discuss from a PR If there is a clear direction 17:07:21 https://github.com/w3c/html-aam/issues/553 17:07:35 spectranaut_: aaron provided the mappings 17:07:46 q+ 17:07:56 spectranaut_: might be a good first issue for someone who wants to get involved in mappings 17:08:08 ack smockle 17:08:16 smockle: Would like to take that on 17:08:22 sarah has joined #aria 17:08:51 Last new issue is a doc issue. Rahim assigned himself 17:09:00 DougG has joined #aria 17:10:07 StefanS has joined #aria 17:10:31 present+ 17:11:00 17:11:01 OliverH has joined #aria 17:11:02 alisonmaher has joined #aria 17:11:06 zakim, next item 17:11:06 agendum 2 -- -> New PR Triage https://bit.ly/3zVR35B -- taken up [from agendabot] 17:11:06 present+ 17:11:14 present+ 17:11:23 https://github.com/w3c/aria/issues/2293 17:11:45 spectranaut_: would like reviews - is editorial and a good small issue to review 17:12:13 Rahim & Curt volunteer to review 17:12:24 https://github.com/w3c/aria/issues/2292 17:13:18 scott: follow on to not using the title attribute for name prohibited. This required to create a new grouping in the HTML-AAM Acc namre computation 17:13:38 scott: added a prohibited name section and some revisions to other sections 17:15:59 scott: would like implementors to push ahead with non-landmark footer/header roles before adding those to the prohibitied section 17:16:09 spectranaut_: adding Rahim 17:16:22 scott: suggest aaron 17:17:11 spectranaut_: will result in implementation changes so should ask implementors 17:17:26 https://github.com/w3c/aria/issues/2291 17:17:43 Present+ 17:18:56 spectranaut_: added reviewers 17:19:21 https://github.com/w3c/aria/issues/2290 17:21:58 OliverH: clickable can be added to anything 17:22:11 spectranaut_: this is triage so we're not opening that now 17:23:50 zakim, next item 17:23:50 agendum 3 -- -> WPT Open PRs https://bit.ly/wpt_a11y -- taken up [from agendabot] 17:24:03 spectranaut_: no new ones 17:24:08 zakim, close this item 17:24:08 agendum 3 closed 17:24:09 I see 5 items remaining on the agenda; the next one is 17:24:09 4. -> Deep Dive/TPAC planning https://bit.ly/aria-meaty-topic-candidates [from agendabot] 17:24:11 zakim, next item 17:24:11 agendum 4 -- -> Deep Dive/TPAC planning https://bit.ly/aria-meaty-topic-candidates -- taken up [from agendabot] 17:24:49 spectranaut_: lets go through the list and see if we still need to deep dive them 17:25:20 https://github.com/w3c/aria/issues/2162 17:25:29 spectranaut_: lots of discussion 17:25:39 giacomo-petri: still needs discussion 17:26:02 giacomo-petri: will try to organize to see if we can discuss during TPAC 17:26:18 jamesn: can we F2F candidate this one? 17:26:34 https://github.com/w3c/aria/issues/2147 17:27:25 spectranaut_: are folks interested in discussing this 17:27:40 sarah: is the topic flowto or how to make flowcharts work 17:27:57 scott: flowto will not really solve that problem 17:28:08 sarah: a bunch of work needs to be done up front 17:28:26 spectranaut_: lets remove deep dive issue as no one is pushing it forward 17:28:38 https://github.com/w3c/aria/issues/2137 17:29:07 remove deep dive from this 17:29:31 also remove deep dive from https://github.com/w3c/html-aam/issues/506 17:29:40 https://github.com/w3c/aria/issues/1951 17:29:49 remove this too 17:30:00 https://github.com/w3c/accname/issues/95 17:33:37 zakim, next item 17:33:37 agendum 5 -- -> Clarify spec treatment of value "undefined" (i.e., as equivalent to invalid value, initial condition for state/property usage) 17:33:39 ... https://github.com/w3c/aria/issues/2280 -- taken up [from agendabot] 17:34:28 Rahim: link to deep dive minutes 17:34:41 Rahim: in the issue - a couple of specifics here 17:34:53 Rahim: Is an invalid value treated the same thing as an undefined value? 17:35:02 Rahim: Should the spec explicitly state that the undefined value/string is not an initial condition for authors to use (e.g., aria-expanded="undefined") in expectation of a downstream ARIA state change? 17:35:21 q+ 17:35:34 spectranaut_: https://github.com/w3c/aria/issues/2280#issuecomment-2250963784 17:36:01 spectranaut_: is an invalid string the same as undefined 17:36:48 spectranaut_: what does undefined mean for a switch? 17:37:07 spectranaut_: that is the only place invalid is discussed 17:37:37 keithamus: a little confused - are we talking about "undefined" or the JS primitive of undefined? 17:37:56 keithamus: is this IDL reflections or HTML attributes 17:38:02 Rahim: I think both 17:38:15 Rahim: multiple ways to set these things 17:38:45 keithamus: there is no undefined primitive in HTML - using setAttribute always a string 17:38:54 IDL is subtly different 17:39:08 keithamus: how the HTML spec deals with enumerated attributes 17:39:24 q+ 17:40:06 ack keithamus 17:40:26 Rahim: there is no clarity about the invalid value default and missing value default 17:40:37 keithamus: the attribute reflection rules around IDL mapping 17:41:49 keithamus: effectively 1110 needs a bit of a cleanup of the various IDLs - once we go through each attribute then can map out the invalid and missing states. The DOM string IDL reflection then becomes valid 17:42:07 Rahim: undefined value and string are not the same thing 17:42:13 ack sohara 17:42:15 ack sohara 17:42:35 sohara: that part of the spec was written before IDL existed for aria 17:42:47 q+ 17:43:14 sohara: we should just know that undefined as a string couldn't be that 17:43:45 ack keithamus 17:43:49 sohara: we need to investigate what browsers are doing with the undefined string right now 17:43:52 q+ 17:44:06 ack sarah 17:44:07 keithamus: undefined as an attribute maps to something useful in aria? 17:44:18 sarah: have done the investigation 17:44:37 sarah: there are now a bunch of issues but will find it 17:44:53 sarah: the string undefined is not being treated as the value undefined 17:45:21 qv? 17:45:34 q+ 17:45:47 sohara: does the undefined string do anything useful in aria? 17:45:58 sohara: noticed that it at least primed the browser 17:46:29 sohara: if i change the state of a button with expanded undefined then the browser would expose the state change 17:46:41 q+ 17:47:06 sohara: very corner case where found it actually had some implementation practicallity 17:47:13 ack smockle 17:47:13 q+ 17:47:30 https://github.com/w3c/aria/pull/2172#discussion_r1596119911 17:47:35 https://jsfiddle.net/pobwvgs9/ 17:47:36 q+ 17:47:59 smockle: undefined behaviour in different browsers 17:48:00 ack keithamus 17:48:05 keithamus you're right, setAttribute + undefined does set the string 'undefined' for the aria-* attributes I tested, I think I was mixing it up with IDL reflection 17:48:52 keithamus: undefined to prime the browser. Browsers have a concept if something exists on a node. It is reasonable to put that in the bucket of these are invalid states. You could probably prime the browser with foo 17:49:00 ack Rahim 17:49:03 i.e. el.setAttribute('aria-expanded', undefined) results in , and el.ariaExpanded = undefined not 17:49:51 Rahim: wanted to add that a confusion was it wasn't clear how it was being specificied - markup vs setAttribute vs IDL - authors may expect the same behaviour 17:50:12 keithamus: IDL is the special case as JS has a concept of undefined but HTMl doesn't 17:50:32 keithamus: assumes strings and puts in the quotes for you 17:50:47 keithamus: HTML and setAttribute assume stringzs 17:51:10 keithamus: if you set null in IDL will have a missing value 17:51:56 Rahim: HTML reflection is much clearer 17:52:53 keithamus: HTML IDL reflections are very clear. The ARIA mixin 17:53:14 keithamus: TLDR we need to define missing and invalid value defaults for each of the attributes 17:53:30 ack sarah 17:53:37 keithamus: we may need to define a custom algorithm for some of the IDL mappings 17:54:01 sarah: string vs value undefined - not seeing any difference in actual mapped APIs 17:54:55 sarah: not seeing any different for invalid value vs undefined 17:55:12 spectranaut_: are we getting closer to an answer 17:55:51 sarah: agree with keith that the string is an invalid value not a missing value 17:56:16 Keith and I were assigned this: https://github.com/w3c/aria/issues/2281 17:56:37 Rahim: believe this will cover the issue we are discussing 17:57:09 keithamus: going to be difficult to achieve due to existing code which may depend on this behaviour 17:57:32 spectranaut_: will mark this as a duplicate of 2281 17:57:54 q+ 17:58:25 ack jamesn 17:58:49 jamesn: it sounds like a use case that there might be errors from validators on 17:59:15 jamesn: invalid values would fail validators for the priming use case 17:59:41 q+ 18:00:34 jamesn: suggests specing it 18:00:46 OliverH has joined #aria 18:00:51 ack jamesn 18:00:59 zakim, end meeting 18:00:59 As of this point the attendees have been smockle, katez, Rahim, giacomo-petri, CurtBellew, sohara, StefanS, alisonmaher, keithamus, Siri 18:01:01 RRSAgent, please draft minutes v2 18:01:03 I have made the request to generate https://www.w3.org/2024/07/25-aria-minutes.html Zakim 18:01:10 I am happy to have been of service, jamesn; please remember to excuse RRSAgent. Goodbye 18:01:10 Zakim has left #aria