W3C

– DRAFT –
ARIA Editors Teleconference

14 May 2025

Attendees

Present
BGaraventa, Daniel, jamesn, pkra, scotto, spectranaut
Regrets
-
Chair
Pkra
Scribe
pkra

Meeting minutes

Duplicates requirements of Selectors aria#2521

pkra: anne asked to remove these two normative statements about CSS. They're just very old pieces of the spec.
… scotto went ahead and made a PR with the first part.
… I'm wondering what do we do here.
… remove it seems fine, even if it's technically normative.
… but then I wondered about CSS being a host language.

scotto: I agree with Anne. We can add an ote.

pkra: agree. Is there anything we should do wrt CSS being sort-of a host language?
… html has a clear statement. CSS doesn't quite fit.

jamesn: it's not really a host language, more ancillary. Like we have JS

pkra: right, but we have IDL for DOM
… ok. I can help with the PR.

scotto: https://drafts.csswg.org/selectors/#attribute-selectors should be the place.

jamesn: maybe use xref.
… if we can.

scotto: happy for pkra to take over.

<Daniel> Selectors 4

pkra: will do.

scotto: the other section could maybe adjusted to incorporate that information.
… something like "any host language supporting styling via CSS, should support ARIA attributes are per CSS..."

Need a process for new CSS features and accessibility mappings / review aria#2496

pkra: this is about the carousel stuff.
… cf. https://www.sarasoueidan.com/blog/css-carousels-accessibility/

scotto: very detailed deep dive.
… there's a lot of discussion around CSS doing this kind of stuff, going back to last TPAC.
… in OpenUI we discussed new menubar elements, directionality for that, affecting arrow navigation.
… this touches both HTML and CSS. Unclear how CSS like this would affect other things.
… and then it's unclear how it should affect accessibility.
… whatwg has an accessibility requirement in their issue and pr templates to ping ARIA. It would be good if CSS WG did the same.

jamesn: maybe we can have a chairs meeting with them.
… there's a risk that the volume will be too large.
… are there others?

scotto: contents is an obvious one. inert is currently discussed. reading-flow is another.
… alice might be good to talk to.

jamesn: will do.

Links to terms using `class='termref' are not updated based on specStatus -- Is this expected behavior? aria#2516

daniel: I filed this. termref links don't link to the specs in the same maturity level.

jamesn: and there are probably not all the same since refs work differently now.

daniel: if we're happy with the current situations, then that's probably ok.

jamesn: I think terms are fine.

daniel: if we want to just link to respec, then I wonder why we keep doing this.

pkra: so then we're on the topic of moving completely to respec

spectranaut_: would be good.

pkra: maybe we should do another hackathon to get that moving.

Different id for assistive technology definitions in ARIA 1.2 and 1.3 aria#2515

Daniel: I can take a look.

Deprecate presentational children aria#2509

daniel: I added it to the board.
… but didn't mean to add it to agenda+

revise approach to documenting deprecation aria#2436

daniel: this connects to ACT discussion last week.

pkra: do we have a label for ACT now?

spectranaut_: we have a PR to propose the new process.
… but I guess we can add the label now.

pkra: I was thinking of https://github.com/w3c/aria/pull/2015/
… which just changes author should to must.

spectranaut_: I've added it. https://github.com/w3c/aria/labels/needs%20act%20review

Old PRs

spectranaut_: we could look at old PRs.

pkra: what can we do about those waiting for implementations?

spectranaut_: we can advocate.
… we can start with the editorial ones at least.

daniel: there may be other groups we could touch base with.

Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).