IRC log of aria on 2025-10-09
Timestamps are in UTC.
- 17:00:03 [RRSAgent]
- RRSAgent has joined #aria
- 17:00:07 [RRSAgent]
- logging to https://www.w3.org/2025/10/09-aria-irc
- 17:00:07 [spectranaut_]
- agendabot, find agenda
- 17:00:07 [agendabot]
- spectranaut_, OK. This may take a minute...
- 17:00:07 [agendabot]
- agenda: https://www.w3.org/events/meetings/5a155237-d896-464b-9c5f-6dd1654293ae/20251009T130000/
- 17:00:07 [agendabot]
- clear agenda
- 17:00:07 [agendabot]
- agenda+ -> New PR Triage https://github.com/search?q=is%3Aopen+is%3Apr+created:%3E=2025-10-02+repo:w3c/aria&type=Issues
- 17:00:07 [agendabot]
- agenda+ -> WPT Open PRs https://bit.ly/wpt_a11y
- 17:00:07 [Zakim]
- RRSAgent, make logs Public
- 17:00:08 [Zakim]
- Meeting: ARIA WG
- 17:00:08 [agendabot]
- agenda+ -> TPAC planning https://tinyurl.com/ariaf2fcandidate
- 17:00:08 [spectranaut_]
- chair: ValerieYoung
- 17:00:09 [agendabot]
- agenda+ -> CSS: handing the a11y of anchor positioning https://github.com/w3c/html-aam/issues/545
- 17:00:12 [agendabot]
- agenda+ -> Should ARIA boolean-like attributes behave like HTML boolean attributes? https://github.com/w3c/aria/issues/2639
- 17:00:15 [agendabot]
- agenda+ -> ARIA IDL updates: enumerated attribute conversions, new "enumerated" wai-aria type, IDL examples https://github.com/w3c/aria/pull/2484
- 17:00:23 [Francis_Storr]
- Francis_Storr has joined #aria
- 17:00:49 [giacomo-petri]
- giacomo-petri has joined #aria
- 17:00:57 [hdv]
- present+
- 17:01:03 [Adam_Page]
- Adam_Page has joined #aria
- 17:01:43 [Stefan]
- Stefan has joined #aria
- 17:01:55 [front-endian-jane]
- present+
- 17:01:57 [Stefan]
- present+
- 17:02:14 [elguerrero]
- elguerrero has joined #aria
- 17:02:21 [Adam_Page]
- present+
- 17:03:01 [katez]
- katez has joined #aria
- 17:03:12 [hdv]
- scribe: hdv
- 17:03:12 [katez]
- present+
- 17:03:18 [chrishtr]
- present+
- 17:03:30 [hdv]
- Zakim, take up next
- 17:03:30 [Zakim]
- agendum 1 -- -> New PR Triage https://github.com/search?q=is%3Aopen+is%3Apr+created:%3E=2025-10-02+repo:w3c/aria&type=Issues -- taken up [from agendabot]
- 17:03:34 [filippo-zorzi]
- present+
- 17:03:38 [jcraig]
- present+
- 17:03:40 [elguerrero]
- present+
- 17:04:05 [Francis_Storr]
- present+
- 17:04:09 [hdv]
- chrishtr: is it all open PR we're looking at or a filter?
- 17:04:15 [hdv]
- spectranaut_: all PRs on ARIA
- 17:04:28 [hdv]
- spectranaut_: created in the last week
- 17:04:32 [chrishtr]
- https://github.com/w3c/aria/pull/2577
- 17:04:48 [hdv]
- chrishtr: I was wondering about #2577, is there a process in this meeting to make progress on that?
- 17:05:08 [hdv]
- spectranaut_: if you want to discuss is at the next, you can always `agenda+` it
- 17:05:11 [Rahim]
- present+
- 17:05:18 [spectranaut_]
- https://github.com/w3c/aria/pull/2577
- 17:05:21 [hdv]
- spectranaut_: we can look at it right now
- 17:05:29 [hdv]
- chrishtr: I'd like to understand if there's anything blocking landing it?
- 17:05:38 [hdv]
- spectranaut_: we don't land until there are 2 implementations
- 17:05:55 [hdv]
- jcraig: I thought there was a scenario with one implementation and support from another, or some variant of that?
- 17:06:02 [hdv]
- spectranaut_: let's check our documentation
- 17:06:14 [Daniel]
- present+
- 17:06:32 [hdv]
- chrishtr: this one has a positive decision from Gecko and Webkit
- 17:06:41 [giacomo-petri]
- present+
- 17:07:04 [hdv]
- spectranaut_: the reason we're hesitant to land it is that we'd have to pull it from the spec when we want to release if there's no implementation, which is extra work
- 17:07:10 [Jacques]
- Jacques has joined #aria
- 17:07:40 [hdv]
- spectranaut_: so ideally we'd like to be more clear on whether they actually plan to have it somewhere in the near future
- 17:08:00 [sarah]
- sarah has joined #aria
- 17:08:03 [hdv]
- chrishtr: would a comment from them suffice?
- 17:08:09 [hdv]
- spectranaut_: yes that'd help
- 17:08:23 [hdv]
- Jacques: this would need platform APIs probably
- 17:08:30 [hdv]
- keithamus: yes you're right on that
- 17:08:48 [hdv]
- spectranaut_: yes it's just a platform API
- 17:08:56 [hdv]
- chrishtr: is testing in WPT a requirement for new things?
- 17:09:11 [hdv]
- spectranaut_: we'd like it but it's not blocking
- 17:09:51 [hdv]
- keithamus: I can't make a firm commitment at this point but will say GitHub sponsored this a while ago and if one of them would be interested in landing it I would be happy to coach them through it
- 17:10:13 [hdv]
- chrishtr: for purpose of landing this, that's probably not firm enough?
- 17:10:21 [hdv]
- spectranaut_: exactly
- 17:10:38 [hdv]
- jcraig: I'll give you another not firm enough statement… we certainly intend to at some point but don't have a timeline at this point
- 17:10:50 [spectranaut_]
- https://github.com/w3c/aria/pull/2650
- 17:10:52 [hdv]
- spectranaut_: ok, let's talk about the next PR… from jcraig
- 17:11:00 [hdv]
- jcraig: it's 6 years in the making
- 17:11:24 [hdv]
- jcraig: we had full review across the board
- 17:11:38 [hdv]
- jcraig: and not quite good enough support from Chromium
- 17:12:08 [hdv]
- jcraig: this has been a long time coming and I would love to see it merged during or before TPAC
- 17:12:33 [chrishtr]
- q+
- 17:12:50 [hdv]
- jcraig: reason there is a new PR is that previous ones were before Prettier and other tooling so wasn't worth redoing. So it's the same content but a fresh PR
- 17:13:17 [Rahim]
- q+
- 17:13:20 [hdv]
- jcraig: keithamus specificially would be nice to have review this as we haven't had a Mozilla review for it yet, we did have a Google review before
- 17:13:25 [hdv]
- keithamus: I'll happily review it
- 17:13:55 [spectranaut_]
- ack chrishtr
- 17:14:01 [hdv]
- chrishtr: jcraig, who reviewed from Google?
- 17:14:15 [hdv]
- jcraig: Aaron Leventhal and Brian @@@ and I think Valerie
- 17:14:29 [hdv]
- chrishtr: is implementation (in WebKit) straightforward?
- 17:14:37 [siri]
- siri has joined #aria
- 17:14:46 [hdv]
- Rahim: relatively easy aside from finding descendant nodes matching the criteria; but yeah pretty easy
- 17:15:05 [hdv]
- Rahim: didn't have to implement anything new, methods I used were already available
- 17:15:13 [spectranaut_]
- q?
- 17:15:34 [hdv]
- jcraig: we thought it'd help with @@@ search, but authors didn't like it so we switched to depth first search… should be easy enough either way
- 17:15:40 [spectranaut_]
- ack Rahim
- 17:15:40 [hdv]
- chrishtr: will check with people from Blink so we can unblock this
- 17:15:42 [Rahim]
- WebKit PR for nameFrom: heading: https://github.com/WebKit/WebKit/pull/43080
- 17:16:03 [siri]
- present+
- 17:16:11 [hdv]
- Rahim: quick question for jcraig on the PR… (2650)
- 17:16:33 [hdv]
- Rahim: re roles affected: I wasn't aware form and region get name from heading?
- 17:16:56 [hdv]
- jcraig: great question, could you put it in the PR? that was from the previous patch, hadn't looked back to check why we had it for form and region
- 17:17:03 [spectranaut_]
- q+ matt
- 17:17:29 [spectranaut_]
- ack matt
- 17:17:51 [hdv]
- matt: I thought we left region out of this… because it requires a name and if you don't explicitly add a name the region the AT will ignore it?
- 17:18:13 [hdv]
- jcraig: yes… but this PR and previous PR had changed that. Will take that as a note, this is why I rerequested review
- 17:18:38 [hdv]
- matt: that change to name from region happened at a point that may have been before the last review?
- 17:18:46 [hdv]
- matt: and we also changed dialog during that time?\
- 17:18:55 [hdv]
- matt: could become a tricky validation role?
- 17:18:59 [hdv]
- s/role/rule
- 17:19:09 [hdv]
- jcraig: I'll take these notes
- 17:19:21 [hdv]
- matt: we'll need to think about how it affects validation and authoring rules and normative statements
- 17:19:34 [hdv]
- jcraig: if you want to review this, matt, I'll add you
- 17:19:51 [siri]
- q+
- 17:19:55 [hdv]
- matt: simplest way to move it forward may be… that it doesn't affect region or form
- 17:20:07 [hdv]
- jcraig: if that's the right solution it would be easiest, but if it's the wrong solution probably not?
- 17:20:35 [spectranaut_]
- ack siri
- 17:20:37 [hdv]
- spectranaut_: any more comments on this PR?
- 17:21:09 [hdv]
- siri: may be good to have names from headings, but if the author wants can they override this?
- 17:21:24 [hdv]
- jcraig: this never overrides names from authors, aria-labelledby and aria-label would override
- 17:22:06 [hdv]
- siri: in the next version of ARIA, having labels requirement changes, how does this work?
- 17:22:36 [hdv]
- jcraig: previously for dialogs it explicitly said it must have a label now it says SHOULD
- 17:23:21 [hdv]
- spectranaut_: then we have two more issues that are editorial, we don't need to talk about them
- 17:23:24 [hdv]
- Zakim, take up next please
- 17:23:24 [Zakim]
- agendum 2 -- -> WPT Open PRs https://bit.ly/wpt_a11y -- taken up [from agendabot]
- 17:24:10 [hdv]
- spectranaut_: there is a new PR from Mike… for web features
- 17:24:21 [hdv]
- mike: I can have a look over this
- 17:24:34 [hdv]
- Zakim, take up next please
- 17:24:34 [Zakim]
- agendum 3 -- -> TPAC planning https://tinyurl.com/ariaf2fcandidate -- taken up [from agendabot]
- 17:25:06 [hdv]
- spectranaut_: just a reminder, we'll be planning to agenda soon, please add F2F candidate issue asap if you have them
- 17:25:38 [hdv]
- Zakim, take up next please
- 17:25:38 [Zakim]
- agendum 4 -- -> CSS: handing the a11y of anchor positioning https://github.com/w3c/html-aam/issues/545 -- taken up [from agendabot]
- 17:26:08 [hdv]
- Daniel: Peter sent regrets
- 17:26:24 [hdv]
- spectranaut_: Peter wrote in the issue we have two implementations for anchor positioning
- 17:26:35 [hdv]
- spectranaut_: should we wait for Peter for this one?
- 17:26:42 [Matt_King]
- Matt_King has joined #aria
- 17:26:53 [Matt_King]
- present+
- 17:27:00 [hdv]
- spectranaut_: let's discuss in another week
- 17:27:02 [sarah]
- present+
- 17:27:03 [Jacques]
- present+
- 17:27:20 [hdv]
- chrishtr: if next week I can make sure Chrome folks are present
- 17:27:21 [hdv]
- Zakim, take up next
- 17:27:21 [Zakim]
- agendum 5 -- -> Should ARIA boolean-like attributes behave like HTML boolean attributes? https://github.com/w3c/aria/issues/2639 -- taken up [from agendabot]
- 17:28:09 [hdv]
- Rahim: James raised a good question re how ARIA attributes are different from HTML attributes
- 17:28:31 [hdv]
- s/ARIA attributes/ARIA IDL attributes
- 17:28:36 [hdv]
- s/HTML attributes/HTML IDL attributes
- 17:28:52 [hdv]
- Rahim: if you use `aria-required` with empty string, it results in false
- 17:29:03 [keithamus]
- q+
- 17:29:06 [hdv]
- Rahim: should boolean-like ARIA attribute behave like HTML boolean attributes?
- 17:30:16 [hdv]
- jcraig: some will equate to false, some are true/false/undefined, where undefined is a separate value than false and it means something different which implementation figures out
- 17:30:36 [hdv]
- jcraig: it's based on element or some other determinable aspect of the DOM
- 17:30:39 [giacomo-petri]
- q+
- 17:30:42 [hdv]
- jcraig: there's a lot of overlap that's possible
- 17:30:53 [spectranaut_]
- ack keithamus
- 17:31:09 [hdv]
- keithamus: there are a couple of attributes in HTML that behave the same as these, that have enumerated keywords of true and false
- 17:31:17 [hdv]
- keithamus: like spellcheck, writing suggestions and draggable
- 17:31:46 [hdv]
- keithamus: all three, I think, reflect the content attribute and resovle to true or false but that's not reflected to the IDL
- 17:31:54 [hdv]
- keithamus: i don't think it's particularly alien for these properties to do what they do
- 17:32:00 [giacomo-petri]
- q-
- 17:32:03 [front-endian-jane]
- q+
- 17:32:27 [hdv]
- keithamus: this has a higher degree of web compat risk and potentially paints us into a corner, would have a stronger objections to this than I did to the prior work for enumerated attributes
- 17:32:35 [hdv]
- Rahim: I figured as much, thanks James and keithamus
- 17:32:59 [hdv]
- Rahim: now that we've migrated a lot, might be worth looking at more of these attributes and ensure to align with best possible IDL types
- 17:33:05 [jcraig]
- q+
- 17:33:06 [spectranaut_]
- ack front-endian-jane
- 17:33:34 [hdv]
- front-endian-jane: this would also cause a number of problems on the author side of things, as there's so much documentation about this. On the author side we can see more confusion about how HTML does booleans than how ARIA does booleans
- 17:33:45 [giacomo-petri]
- q+
- 17:33:48 [spectranaut_]
- ack jcraig
- 17:33:53 [hdv]
- front-endian-jane: not a 100% against this, but if we change this it could cause a lot of uproar among authors
- 17:34:19 [hdv]
- jcraig: I also vote for the enumerated string values, also considering the extensibility argument that keithamus brought up
- 17:34:37 [hdv]
- jcraig: because it's never been boolean, we can be sure there's no authors that are using this for comparison
- 17:34:49 [hdv]
- jcraig: so there's near zero web compat risk
- 17:34:57 [spectranaut_]
- ack giacomo-petri
- 17:35:02 [hdv]
- jcraig: and there's no web compat benefit to changing it to boolean as far as I can tell
- 17:35:48 [hdv]
- spectranaut_: wanted to add to author confusion point that jcraig brought up… I see a lot of code with aria-disabled=true/false, eg aria-disabled=false. Can imagine changing this would cause a lot of problems with authors
- 17:35:54 [hdv]
- s/spectranaut_/giacomo-petri
- 17:36:27 [hdv]
- jcraig: to clarify, giacomo-petri… when the author set the value to false, what wouldn't work?
- 17:36:40 [hdv]
- jcraig: wouldn't it still be an invalid value?
- 17:36:50 [hdv]
- jcraig: that falls back to false?
- 17:37:25 [hdv]
- front-endian-jane: I can't remember the exact details, but I've seen something similar to what giacomo-petri was saying
- 17:37:31 [jcraig]
- s/near zero web compat risk/less web compat risk for enum than boolean/
- 17:37:35 [spectranaut_]
- q?
- 17:38:37 [hdv]
- keithamus: I think the general thing to take away from this, enumeration with a string true or false is probably a bad idea, want to use aliases like on or off instead… if we had something like aria-checked=on or =checked, might have eleviated some of this
- 17:38:46 [hdv]
- Zakim, take up next
- 17:38:46 [Zakim]
- agendum 6 -- -> ARIA IDL updates: enumerated attribute conversions, new "enumerated" wai-aria type, IDL examples https://github.com/w3c/aria/pull/2484 -- taken up [from agendabot]
- 17:39:20 [hdv]
- Rahim: more IDL fun!
- 17:39:29 [hdv]
- Rahim: got some good feedback from James and Anne
- 17:39:52 [keithamus]
- q+
- 17:39:58 [hdv]
- Rahim: first issue, aria-haspopup… I believe true and menu are synonyms… which is the canonical value, true or menu? and how should ARIA reflection works when this is provided?
- 17:40:00 [spectranaut_]
- ack keithamus
- 17:40:57 [hdv]
- keithamus: I think we should define it such that it's not the string 'true'… I think there's already mechanics for the canonicalisation of keywords
- 17:41:18 [hdv]
- keithamus: so if there was a string 'true' in the DOM it would be returned as 'menu' in the IDL still
- 17:41:25 [jcraig]
- q+
- 17:41:26 [hdv]
- keithamus: so just depends on which way we would canonicalise
- 17:41:59 [jcraig]
- ack me
- 17:42:01 [hdv]
- Rahim: in IDL reflection, do we want 'true' or 'menu' to reflect as the same values, should they be synonyms?
- 17:42:31 [hdv]
- jcraig: wanted to ask Matt_King… sorry if you're the wrong person… wasn't there a point we made 'true' the canonical value?
- 17:42:37 [spectranaut_]
- q+
- 17:42:58 [hdv]
- Matt_King: in 1.1… I'm not sure if it became an antipattern… what happened was the original values were only added to get some compromise in what we needed for just the combobox role
- 17:43:08 [hdv]
- Matt_King: we kept true as a synonym to menu for compatibility
- 17:43:46 [hdv]
- Matt_King: I kind of lean into keithamus's direction… based on how aria-haspopup has been used now… quite a few people argued for using the values of haspopup in other places than combobox, particularly buttons
- 17:44:06 [hdv]
- Matt_King: not sure if there's consensus on that… can't see what the problem would be of making menu the canonical value
- 17:44:20 [jamesn]
- jamesn has joined #aria
- 17:44:51 [hdv]
- spectranaut_: re Rahim's question just wanted to say re how ATs handle these values… aria-haspopup=true is handled as aria-haspopup=menu in accessibility APIs
- 17:44:58 [hdv]
- spectranaut_: so menu is the defualt
- 17:44:59 [spectranaut_]
- https://w3c.github.io/core-aam/#ariaHaspopupTrue
- 17:45:18 [hdv]
- s/defualt/default
- 17:45:32 [hdv]
- Rahim: ok so 'menu' would be the canonical keyword with 'true' as a synonym
- 17:45:52 [hdv]
- Rahim: someone asked me… why would aria-haspopup return null instead of false?
- 17:46:22 [hdv]
- Matt_King: it's like aria-pressed… if you have a button where it's not set it's null but if there is one it's false
- 17:47:22 [hdv]
- jcraig: may be different if there's a native control that uses aria-haspopup where we'd use undefined as the missing or invalid value
- 17:47:24 [spectranaut_]
- ack spectranaut_
- 17:48:12 [hdv]
- Rahim: ok so aria-haspopup will return undefined state which is null
- 17:48:24 [hdv]
- Rahim: false and empty string return false I believe
- 17:48:53 [hdv]
- Matt_King: this could be one of the places where we want 'false ' to return 'undefined' because we had 'true' return 'menu'… enumerated things that initially, in ARIA 1.0 was a boolean
- 17:49:01 [hdv]
- Matt_King: maybe we should go away from false entirely here
- 17:49:08 [hdv]
- jcraig: not sure if undefined is any better in that regard
- 17:49:45 [hdv]
- Rahim: so sounds like 'false' remains a valid keyworrd?
- 17:49:52 [hdv]
- jcraig: have to think about that some more
- 17:50:07 [hdv]
- keithamus: would be open, but would probably raise similar conversations up until this point, especially regarding web compat
- 17:50:22 [hdv]
- keithamus: if we start returning entirely new values, a lot of guidance may have to be updated
- 17:50:54 [hdv]
- jcraig: hm maybe not worth doing in that case
- 17:51:18 [hdv]
- Rahim: next question, how do I specify undefined in the attribute values table?
- 17:51:27 [hdv]
- Rahim: please review that when you look at the PR
- 17:51:45 [hdv]
- Rahim: there's some overlap between concepts of undefined state, and the "undefined" string value
- 17:52:19 [hdv]
- Rahim: last time I took away it's okay to use an undefined state, but undefined string value is provided to the content attribute it would be for a missing value default
- 17:52:28 [hdv]
- Rahim: folks that are interested, please take a look at that section
- 17:53:45 [hdv]
- Rahim: when MDN talks about content attributes, they list undefined as an actual value, which I think wasn't the intention, it was for the absence of the value to be undefined
- 17:54:57 [hdv]
- Rahim: another question, last time we talked about this there seemed to be consensus to add an undefined state. My question is should all ARIA attributes that support null be specified as an undefined state?
- 17:56:50 [hdv]
- Rahim: there's an explainer linked from the PR description, it has a table for all the updated attributes,
- 17:56:57 [hdv]
- Rahim: should everything that has `null` be undefined state?
- 17:57:05 [hdv]
- jcraig: I think that's probably editorial errata in the past?
- 17:57:29 [hdv]
- keithamus: I think I mentioned a while ago… I think we don't have to have the undefined state, if we don't mention it in prose
- 17:57:50 [hdv]
- keithamus: there might be no point in labeling a state… labeling them the undefined state might make it more confusing
- 17:58:08 [hdv]
- jcraig: i recall you suggested 'no state'
- 17:58:24 [Rahim]
- q+
- 17:58:54 [hdv]
- jcraig: I recall because we had the string value of undefined that had previously been there, we wanted the reflection to match that
- 17:59:01 [hdv]
- jcraig: even if the string value you assigned could map to something else
- 17:59:14 [hdv]
- jcraig: but not sure if there's a benefit to keeping that in this scenario
- 17:59:42 [hdv]
- jcraig: re Rahim's question , to my recollection everything we call null also means undefined
- 18:00:09 [hdv]
- Rahim: re undefined state discussion, Anne chimed in and discouraged us from going with no state
- 18:00:23 [hdv]
- Rahim: he recommended we name that state
- 18:00:33 [hdv]
- Rahim: will follow up with him and perhaps keithamus and jcraig
- 18:01:41 [jcraig]
- s/I recall because we had the previously assignable string value of "undefined" that had previously been there, we wanted the reflection to match that/I recall because we had the string value of undefined that had previously been there, we wanted the reflection to match that conceptually, hence the named Undefined State/
- 18:02:37 [jcraig]
- s/but not sure if there's a benefit to keeping that in this scenario/but not sure if there's a benefit to keeping that in this scenario over the NoState suggestion (Update: There is not. Either fine with me.)/
- 18:23:29 [spectranaut_]
- zakim, make minutes
- 18:23:29 [Zakim]
- I don't understand 'make minutes', spectranaut_
- 18:23:36 [spectranaut_]
- zakim, end meeting
- 18:23:36 [Zakim]
- As of this point the attendees have been hdv, front-endian-jane, Stefan, Adam_Page, katez, chrishtr, filippo-zorzi, jcraig, elguerrero, Francis_Storr, Rahim, Daniel, giacomo-petri,
- 18:23:39 [Zakim]
- ... siri, Matt_King, sarah, Jacques
- 18:23:39 [Zakim]
- RRSAgent, please draft minutes v2
- 18:23:40 [RRSAgent]
- I have made the request to generate https://www.w3.org/2025/10/09-aria-minutes.html Zakim
- 18:23:47 [Zakim]
- I am happy to have been of service, spectranaut_; please remember to excuse RRSAgent. Goodbye
- 18:23:47 [Zakim]
- Zakim has left #aria