Re: [csswg-drafts] [css-overflow-5] `:target-current` pseudo class should also imply `aria-current=true` on an active scroll marker (#12659)

The CSS Working Group just discussed ``[css-overflow-5] `:target-current` pseudo class should also imply `aria-current=true` on an active scroll marker``.

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> astearns: we were waiting on some a11y input, looks like we've gotten<br>
&lt;lea> TabAtkins: yes but we don't have a one-shot switch for them like `color-scheme`. And perhaps they're less commonly used on inherited properties?<br>
&lt;TabAtkins> daniil: so to recap, we have scroll-target-group, takes a bunch of links and creates a "scroll spy" from them<br>
&lt;TabAtkins> daniil: it makes the most appropriate link "current". We use a :target-current pseudo for that, but it's not indicated in the a11y tree<br>
&lt;PaulG> q+<br>
&lt;TabAtkins> daniil: we took to a11ywg and discussed a proposal. we reoslved there, decided to make a new css/am spec which will define this behavior<br>
&lt;TabAtkins> astearns: is this no action on our part? or waiting for aam before we do something?<br>
&lt;astearns> ack PaulG<br>
&lt;TabAtkins> daniil: nothing on our end for now. after the spec exists, might be some to link to<br>
&lt;TabAtkins> PaulG: we just talked about this in the aac meeting. are you saying this is moving forward with aria-current being injected int othe markup? or just some aam mapping?<br>
&lt;TabAtkins> daniil: aam mapping only<br>
&lt;kbabbitt> sgtm<br>
&lt;TabAtkins> +1<br>
&lt;bkardell> q+<br>
&lt;TabAtkins> bkardell: would b enice to have a css-aam finally, the repo is already there<br>
&lt;TabAtkins> astearns: daniil mentioned it's an upcoming thing<br>
&lt;fantasai> scribe+<br>
&lt;fantasai> bkardell: Is there an editor for this?<br>
&lt;fantasai> ??: I'm not sure, since repo isn't up yet<br>
&lt;fantasai> bkardell: I thought there's a repo<br>
&lt;fantasai> ??: Yes, but no website or anything<br>
&lt;kbabbitt> s/??/daniil/<br>
&lt;fantasai> s/??/daniil/<br>
&lt;fantasai> bkardell: We are celebrating CSS reaching REC and still don't have AAM<br>
&lt;fantasai> astearns: Ok, then we're done with this issue.<br>
&lt;fantasai> astearns: Should we leave it open until this AAM exists so we can link to it?<br>
&lt;fantasai> daniil: Do we need a discussion for the link, or I can do it afterwards?<br>
&lt;fantasai> astearns: Will it be informative or normative?<br>
&lt;fantasai> danii: [missed]<br>
&lt;fantasai> astearns: Ok, we can close this issue unless you want to use it to track the edit.<br>
&lt;bkardell> https://w3c.github.io/css-aam/<br>
&lt;bkardell> I see editors there<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12659#issuecomment-4443404384 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 13 May 2026 16:59:18 UTC