- From: Chris Swithinbank via GitHub <noreply@w3.org>
- Date: Fri, 20 Feb 2026 12:04:59 +0000
- To: public-css-archive@w3.org
delucis has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-overflow-5] Accessible semantics for `:target-current` == While evaluating the new `:target-current` pseudo-class, I wondered whether it should be reflected in the accessibility tree in some way. I maintain a table of contents implementation using JS that in theory `:target-current` and `scroll-target-group` would be able to replace. Currently, we use `aria-current="true"` to highlight the current item in a table of contents. As far as I can tell (at time of writing, in Chrome 144), `:target-current` is not exposed with a similar “current item in group” semantics in the accessibility tree. Should links matching `:target-current` receive some similar semantics in the AT? I also saw Sara Soueidan discussing this, so want to link that too for reference: https://www.sarasoueidan.com/blog/css-scrollspy/#the-semantic-accessibility-of-html-scroll-markers > Because the purpose of the `scroll-target-group` property and the `:target-current` selector is to allow us to create JavaScript-_free_ native HTML scroll markers, we should expect the browser to add and manage the necessary ARIA attribute(s) required for scroll markers to be inclusive. (After all, that’s the whole premise of this feature: to write a few lines of CSS and let the browser handle all the behavior for us.) > > However, at the time of writing of this post, Chrome (currently the only browser that has implemented this feature) doesn’t add `aria-current=true` to the active anchor yet. --- <sup>Originally posted in https://github.com/w3ctag/design-reviews/issues/1037#issuecomment-3799273495</sup> Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13537 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 February 2026 12:04:59 UTC