-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Usage of appropriate html tags instead of divs #31656
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
Comments
The "Filter" element is already aria-friendly (including the "Profile and Settings" and "Create"):
It is not a button, and it already declares itself as a "combobox", so any aria-aware software should be able to recognize it correctly, so I think it's vimium's responsibility to handle aria-related elements. |
I appreciate the extensive usage of aria attributes/roles and will ask on vimiums site if they plan on using them. Is there a reason why In comparison, GitHub seems to implement the same feature using native elements ( Also I found some overlaping issues which mention accessability (#21742) and rework of the UI (#29849). With a rework in planning, I see no reason to fix this issue now, but keep the concerns in mind. The title is updated to better reflect my intention. |
Because Gitea is still using Fomantic UI : https://fomantic-ui.com/modules/dropdown.html#/usage |
There is also effort being made to switch away from fomantic: https://blog.gitea.com/goodbye-jquery/ |
We close issues that need feedback from the author if there were no new comments for a month. 🍵 |
Description
Some "buttons" currently use the
<div>
tag. This can cause accessability issues.I found this in following places (also see screenshots below):
In my case the browser extension vimium is not able to access the menu points, which appear after clicking those elements.
Screenshots
Top navigation bar
Also on the blue marked subpages
Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
Yes
Operating System
No response
Browser Version
Firefox 128.0
The text was updated successfully, but these errors were encountered: