- From: Jan Nicklas via GitHub <sysbot+gh@w3.org>
- Date: Sat, 24 May 2025 09:27:07 +0000
- To: public-css-archive@w3.org
I believe the feature to "allow making an element non-inert" is crucial for build good accessibility. One use case which is very common is that you have an input field inside the header navigation to receive focus but it should allow also focus to its flyout:  I believe keeping the status-quo of inert is just not enough. In the following article I am trying to explain it in details with videos and with examples of big websites like bing, youtube, amazon. Even expert frontend developers working on these websites struggle and fail to build easy to use and bug free keyboard navigations: https://dev.to/jantimon/focus-containment-the-broken-state-of-keyboard-navigation-45l1 -- GitHub Notification of comment by jantimon Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10711#issuecomment-2906695573 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 24 May 2025 09:27:08 UTC