Hi folks,
Just wanted to share a new feature idea/proposal released recently. This was driven by internal design/component systems teams at Microsoft and is a way to neatly solve the common "roving tabindex" authoring paradigm with a native solution, while at the same time improving default accessibilty for the same.
It's an early-days incubation proposal, and has lots of issues to work through, but one that I hope will eventually upstream here into the spec, and for that reason I'm creating this issue for tracking ;)
focusgroup attribute
Explainer: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Focusgroup/explainer.md
Thanks!
Hi folks,
Just wanted to share a new feature idea/proposal released recently. This was driven by internal design/component systems teams at Microsoft and is a way to neatly solve the common "roving tabindex" authoring paradigm with a native solution, while at the same time improving default accessibilty for the same.
It's an early-days incubation proposal, and has lots of issues to work through, but one that I hope will eventually upstream here into the spec, and for that reason I'm creating this issue for tracking ;)
focusgroupattributeExplainer: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Focusgroup/explainer.md
Thanks!