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;sakhapov> sakhapov<br>
&lt;emilio> sakhapov: We have a bunch of links and we can ask the browser to mark the link which has the link whose target is in view<br>
&lt;emilio> ... for a11y we should mark it as `aria-current=true`<br>
&lt;bkardell> q+<br>
&lt;emilio> ... we should add that to the spec<br>
&lt;flackr> q+<br>
&lt;emilio> q-<br>
&lt;Rossen9> ack bkardell<br>
&lt;lea> q?<br>
&lt;emilio> bkardell: you're not suggesting that we should actually set an attribute right? Just the a11y state?<br>
&lt;lea> q+<br>
&lt;emilio> sakhapov: yeah, I guess<br>
&lt;Rossen9> ack flackr<br>
&lt;emilio> flackr: that's what I was on the queue to talk about<br>
&lt;emilio> ... correct, that implies an aria-current state if there's no explicit one for the element<br>
&lt;emilio> bkardell: doesn't that belong to a11y mappings?<br>
&lt;emilio> sakhapov: you're probably right should I ask the a11y wg?<br>
&lt;lea> q?<br>
&lt;emilio> bkardell: I think it should go there<br>
&lt;emilio> q+<br>
&lt;emilio> bkardell: dunno if it goes in html accessibility mappings, not sure if we have a css one<br>
&lt;Rossen9> ack lea<br>
&lt;PaulG> q+<br>
&lt;emilio> lea: +1 to solving this but not quite sure what it's being proposed, so it's not a property<br>
&lt;emilio> ... :target-current is a property<br>
&lt;emilio> s/a property/a pseudo-class/<br>
&lt;emilio> ... so when is this applied, when somebody uses the pseudo-class?<br>
&lt;flackr> qq+<br>
&lt;emilio> ... it'd be easier to have a property<br>
&lt;emilio> flackr: this has nothing to do with whether or not :target-current pseudo-class<br>
&lt;Rossen9> ack flackr<br>
&lt;Zakim> flackr, you wanted to react to lea<br>
&lt;emilio> ... we've resolved that when you use scroll-target-group we select one link as :target-current<br>
&lt;emilio> ... so not affected by usage of the pseudo-class<br>
&lt;emilio> lea: maybe I got confused by the wording of the issue<br>
&lt;dholbert> emilio: it seems like this is the right thing to do. if it has to go into a CSS spec, we should resolve on it<br>
&lt;dholbert> emilio: lea, maybe a better way to frame it -- if you want to express in terms of css properties, you could think of UA stylesheet having :current { internal-property: state}<br>
&lt;Rossen9> ack emilio<br>
&lt;Rossen9> ack PaulG<br>
&lt;bkardell> https://w3c.github.io/css-aam/<br>
&lt;bkardell> https://w3c.github.io/html-aam/<br>
&lt;emilio> PaulG: I believe ??s comments are correct the APA have discussed this and we're going to talk about this at tpac but this should be in HTML probably<br>
&lt;bkardell> s/??s/Sara's<br>
&lt;emilio> sakhapov: so css triggers this behavior but then triggers this pseudo-class<br>
&lt;emilio> ... so it's mostly HTML accessibility<br>
&lt;emilio> sakhapov: so first of all I should find out where we should put this in<br>
&lt;emilio> ... if it's CSS we should resolve on adding aria-current for scroll-target-group<br>
&lt;emilio> ... the issue was also flagged for tpac<br>
&lt;emilio> Rossen9: do we have time scheduled with APA at tpac? We should probably discuss it here<br>
&lt;emilio> bkardell: does it make sense to open an issue in the html-aam repo?<br>
&lt;emilio> Rossen9: yes absolutely<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-3492620918 using your GitHub account


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

Received on Wednesday, 5 November 2025 18:00:22 UTC