- From: Di Zhang via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Feb 2025 23:39:41 +0000
- To: public-css-archive@w3.org
I was considering whether we could reuse tabIndex to explicitly set item's focus order, but came to the conclusion that we should avoid that. Adding the reasoning here for prosperity. 1. We want people to move away from positive tabindex as they are not discoverable by the accessibility tree. 2. Since reading-flow is a CSS property, it would be preferable to keep the control on the CSS side. Mixing HTML and CSS to build the rendering-defined sibling reading flow list is not good. 3. By having this new CSS property, we will be able to scope it to only be within an eligible reading flow container. 4. If someone sets the tabIndex with the expectation that it is scoped within the reading flow container, but the code is moved/copied around, the tabIndex will cause jumping around and unexpected focus order. -- GitHub Notification of comment by dizhang168 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11208#issuecomment-2635305768 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 February 2025 23:39:42 UTC