- From: Aaron Leventhal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Apr 2025 17:51:05 +0000
- To: public-css-archive@w3.org
I think the columns use case might possibly be a third use case. We might decide to expose it differently to the a11y tree than the tabpanel case. Would it be crazy to have scroll-marker-type have 3 values? loose, discrete, and set (modulo bikeshedding). If "set", it would automatically apply CSS columns and any keyboard/axtree improvements we come up with. Regarding how 'discrete' affects the ax tree, and whether to remove non-active items, I'd be open to it. Would like to hear arguments either way. We also have the option that we simply expose everything but use accessible relations (controls/details/flowto) to enable better AT processing / improve user navigation. -- GitHub Notification of comment by aleventhal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12122#issuecomment-2839726665 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 April 2025 17:51:06 UTC