-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Can't set collaborator permissions with only keyboard #8460
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Is this still the case? |
Yes, I haven't written the rest of the dropdown menu accessibility code as I've been doing other things. I needed to do an audit of the dropdown menus in HTML for a reason I forget- I think so I could test all of them. I'll try having a shot at this sometime this month. |
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
I think this issue is resolved. At least I could added @Jookia as a collaborator in my test repo and set them permissions with just keyboard interaction. |
Fixed by #19861 (comment) and confirmed by Jookia: #19861 (comment) I will close this issue. |
[x]
):https://try.gitea.io/Jookia/test/settings/collaboration
Description
When managing collaborators in repository settings, any changes to user permissions made just by using the keyboard to focus the drop down menu and arrows to select an item do not save. I looked at the HTML and saw that the saving only happens onclick, which isn't triggered when using the keyboard.
Because of this you can't set collaborator permissions with only the keyboard. This is a significant roadblock for accessibility.
Screenshots
Bug isn't visible in a screenshot
The text was updated successfully, but these errors were encountered: