-
-
Notifications
You must be signed in to change notification settings - Fork 78.8k
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.
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
Accordion header usability #23853
Comments
That would be so nice. |
On the other hand people might want to put other clickable elements in a header (one not causing expand / collapse) - ex. a close button. Somehow it seems like we should have 2 areas in the accordion / tab header. |
You can easily do this with the current implementation see codepen example |
imo it has to be an 'a' element due to accessibility reasons examples with "icons" |
@gijsbotje you can easily add Either way I think this issue can be closed. |
It might be worth mentioning in the docs on how to do it. |
PR is welcome. |
I was about to add a PR but I am still not sure what exactly to mention in the docs. While like @gijsbotje solution with the icons a lot but the code changes needed a are bit too much for the documentation IMHO and I think this would be as a part of bootstrap. So I guess probably a single line about adding
I don't agree. One should also think about handicapped users not using screen readers or other people first and foremost using the keyboard and in this case proper links are still better because they can be Tabed to. |
Worth mentioning: Now there is also |
Fixed in #29782 |
Apparently since accordion pane headers look like buttons (now more than ever), it has been shown in our user testing that some users are attempting to click the accordion headers first.
Is there any good reason against making the whole header clickable?
Some examples of other web UI frameworks where the whole accordion header is clickable:
The text was updated successfully, but these errors were encountered: