- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Apr 2023 19:00:14 +0000
- To: public-css-archive@w3.org
I've written (but not yet merged) [a change](https://chromium-review.googlesource.com/c/chromium/src/+/3910374) to Chromium to do this, that is, to make elements with `display: contents` focusable. I'm somewhat concerned about landing it given that there seems to be some resistance from other implementors. It's not clear to me whether other implementors are actually willing to make this change, and I think it would be good to find out before changing Chromium to diverge from a currently-interoperable behavior. However, I agree that that currently interoperable behavior is bad. It's important that the resolutions of #2355 and of this issue be consistent, since (as I understand things) part of the contract of reporting to assistive technology that an element has a particular role is that this exposure implies that the element should also have the keyboard behaviors associated with that role (which admittedly not all roles have, but many do). So I think we should either change our resolution of neither issue (which implies that implementations need to change on focusability), or change both (which I think implies implementations need to change AT exposure). I'm curious whether others think that this issue should be reopened in order to build stronger consensus around the correct behavior here. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2632#issuecomment-1497976046 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 April 2023 19:00:15 UTC