Accessibility - Tab order is wrong on creating an issue (tabindex) #26731
Labels
Comments
techknowlogick
added
the
topic/accessibility
|
-> Fix incorrect "tabindex" attributes #26733 |
wxiaoguang
added a commit
that referenced
this issue
Aug 26, 2023
Fix #26731 Almost all "tabindex" in code are incorrect. 1. All "input/button" by default are focusable, so no need to use "tabindex=0" 2. All "div/span" by default are not focusable, so no need to use "tabindex=-1" 3. All "dropdown" are focusable by framework, so no need to use "tabindex" 4. Some tabindex values are incorrect (eg: `new_form.tmpl`), so remove them Co-authored-by: Giteabot <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When navigating with keyboard when creating an issue the tab order isn't plausible. I expect after editing the title the next tab is the description text area or the tabpanel but it jumps to somewhere else and the next targets are the menu items.
Strange settings of
tabindexattributes on different DOM elements are the cause. A best practice is to not set thetabindex>0and using the natural DOM order.Gitea Version
1.20.2
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
run from docker but doesn't matter
Database
None
The text was updated successfully, but these errors were encountered: