In #389 it was reported that text editors were not accessible yet.
Given that such a central piece of the software it not accessible by screen readers (and spell checkers for the matter) yet, it's very likely that there are other UI roadblocks, too.
I'd love to improve this and take the power of Codeberg to move on here. I'm opening this issue to collect open issues that are already identified, discuss new eventual issues and / or talk about asking for an audit of the software.
Also we should talk about QA to make sure that UI changes / framework migrations etc do not introduce new accessibility issues.
Of course this needs a close collaboration to the upstream developers, but first opening here to collect the material necessary and talk about how Codeberg can support this mission.
We got a recent bump on Social Media and I'd like to add this to the list of highest priority stuff to be completed ASAP. The issue is, that we don't really know what to do and where are blockers. Funding an external analysis is an option, also hiring developers to fix this, but we can probably only support the fix for one matter this year, and there are competiting highest-priority topics 😕
In an internal issue (not very active), we talked about supporting this: https://github.com/go-gitea/gitea/issues/11426 (honeypots instead of captcha). It would be cool if someone could say if this improves the signup situation.
Also, apart from the even-with-intact-vision-hard-to-solve captcha, there might be more issues in Gitea we are not aware of, and I personally don't really know how to properly audit this.
https://github.com/go-gitea/gitea/issues/7057#issuecomment-881230491 some PRs are breaking screen reader support. Looks like we urgently need to step in there. Discussing some possible ways of handling this right now.
We probably need to hire someone to fix the two breaking issues for 1.15 and then someone to do some audit and / or fix some issues. Any idea how to start the search?
Of course close collaboration is necessary, like, there are talks about moving to another UI toolkit etc, maybe we should just use funds to get this milestone in and then continue from there ...
Hi, I mentioned on Fedi that I would like to step in and help.
I have never worked with Gitea's source and I'm not sure whether Codeberg maintains a fork. Should I try to implement a fix against the fork if there is one?
Hmm, best would be to address the mentioned issues (the PRs) upstream at the Gitea source code: https://github.com/go-gitea/gitea/
Codeberg does maintain a fork at https://codeberg.org/codeberg/gitea, but it is only meant for contributions that don't work upstream (e.g. because they are hacky fixes or tiny changes).
If you don't have a GitHub account, you can maybe still raise your PR here at Codeberg ... you'd have to target the codeberg-1.15 branch then.
If you have any questions or need assistance, please let us know how we can help. Thank you very much!
@fnetX thank you for the response! I wanted to hack on it now but my changes to the install template are not visible after I do
TAGS="bindata sqlite sqlite_unlock_notify" make build, even after I tried to
make clean. Is there anything else I need to do?
Okay, just read the thread on GitHub, somehow missed the last messages in my email spam. Would you be available for hire, too, just to fix these urgent issues at first? We'd need some warmup to get official contracting correctly, but it might be a good start, if you're interested, too.
I am not available for hire and, unfortunately, I do not have enough of my holidays left to make sure I will be done with it.
As I wrote there the easiest for now is to just replace those dropdowns with
<select>. Gitea maintainers want more advanced solution and I recommend contacting Jookia (also on Fediverse) who has quite some experience in it and also implemented the previous dropdown. If nothing works out I can try this out in my free time still.
Deleting a branch is permanent. It CANNOT be undone. Continue?