Opened 11 years ago
Closed 8 years ago
#7791 closed feature (patcheswelcome)
Accordion Tabindex should be customizable
Reported by: | HankS | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | [meta] ui.a11y | Version: | 1.8.16 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
The accordion's keyboard support could be further improved by having a way to specify the tabindex to use. The current default of tabindex="0" prevents the accordion from being inserted in the middle of the overall tab flow.
Suggestions: add an option to specify the tabindex during accordion creation, an option to disable tabindex changes altogether (letting the developer handle them), or simply restore the tabindex originally specified in the markup by keeping a copy before changing to -1.
(Note: Trying to force a proper tabindex by changing it after accordion creation, or during the accordion's "change" event, doesn't work because the tabindex's are also reset to 0's and -1's when the keyboard up/down keys are pressed.)
Change History (9)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Component: | ui.accordion → [meta] ui.a11y |
---|
comment:3 Changed 11 years ago by
Scott, any thoughts on this? Should be addressed while you're working on Accordion anyway.
comment:4 Changed 11 years ago by
Type: | enhancement → feature |
---|
comment:5 Changed 10 years ago by
Milestone: | 1.9.0 → 1.10.0 |
---|
comment:6 Changed 10 years ago by
scott_gonzalez, can you mark this as open if it's a feature we're going to be implementing one day, or close as wontfix if not? Thanks!
comment:7 Changed 10 years ago by
Status: | new → open |
---|
Customized tab index is such a hassle, but for single focus widgets I think it's possible to handle. I don't think this is common enough to warrant an option, but I'd be ok with refactoring the code to make it possible to implement an extension.
comment:8 Changed 10 years ago by
Milestone: | 1.10.0 → none |
---|
comment:9 Changed 8 years ago by
Resolution: | → patcheswelcome |
---|---|
Status: | open → closed |
I'm willing to accept PRs that add extension points to make this possible, but I don't think this is something we're going to address on our own.
This isn't restricted to Accordion - we're even building a bunch of new widgets where tabindex defaults to 0. Do we want to support custom tabindex everywhere?