Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposal for: a declarative way to get keyboard navigation for focusable element groups #7054

Open
travisleithead opened this issue Sep 10, 2021 · 1 comment
Open

Proposal for: a declarative way to get keyboard navigation for focusable element groups #7054

travisleithead opened this issue Sep 10, 2021 · 1 comment
Labels
accessibility Affects accessibility addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest

Comments

@travisleithead
Copy link
Member

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!
@travisleithead travisleithead changed the title A declarative way to get keyboard navigation for focusable element groups Proposal for: a declarative way to get keyboard navigation for focusable element groups Sep 10, 2021
@annevk annevk added addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest accessibility Affects accessibility labels Sep 14, 2021
@jimmywarting jimmywarting mentioned this issue May 14, 2022
Open
@lukewarlow
Copy link
Member

The explainer has moved to https://open-ui.org/components/focusgroup.explainer/

As for implementer interest at least Chromium has been prototyping this, see https://chromestatus.com/feature/5637601087193088

@annevk annevk mentioned this issue Jun 12, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accessibility Affects accessibility addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest
Milestone
No milestone
Development

No branches or pull requests
3 participants
@annevk @travisleithead @lukewarlow