Codeberg Accessibility #479
Labels
No Label
bug
Codeberg
contribution welcome
docs
duplicate
enhancement
infrastructure
legal
licence / ToS
public relations
question
s/Gitea/Forgejo
s/Pages
s/Weblate
s/Woodpecker
security
service
spam
upstream
wontfix
No Milestone
No Assignees
12 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Codeberg/Community#479
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
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.
Edit: Current status
Accessibility for Gitea is an ongoing issues, the most important problems currently
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 tomake clean. Is there anything else I need to do?Ah, sorry, it's actually fine
@charlag hey, did you make any progress? Is there something we can help with?
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.
Hey
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.Re CAPTCHA: We'd love to add an audio captcha to Gitea. Contributions very welcome. Building an own CAPTCHA (to Gitea) has the advantage that people can't use generic scripts.
Other options I have on my notes so far:
Small heads-up regarding the captcha: We are considering building a captcha service ourself. The whole story (idea) can be found here: https://codeberg.org/Codeberg-Infrastructure/CaptchaService
Contribution very welcome. We are probably aiming to do this in a one-weekend hackathon for a proof-of-concept prototype.
Any movement on the CAPTCHA issue? We have a dev who cannot create a new account.
https://chaos.social/@dentangle/108652266792247321
No real progress, we are sorry. We're still asking them to send us an email in the meantime until we find someone to come up with a proper patch.
Just disabling the captcha is not a solution. We tried this several times, and spam was shooting to the moon. The most recent observation was that some simple and custom tweak heavily reduced bot-registrations by doing simple transforms to the captcha text.
So yes, the captcha is very effective, and the solution is to offer an accessible one (e.g. via audio or (as we considered to try) with text-based question-answer). We are a handful of volunteers, and cannot compete with proprietary for-profit platforms that have much more funds than we have.
Regarding Gitea, we often wish they had a different priorization, but it's a do-ocracy in the end (those who do decide what they do). For Codeberg, we're just not finding enough time to get into developing real solutions.
Hi Otto,
Thanks for responding to me. Perhaps you may want to get codeberg.org to make an appeal for help in the Fediverse. As the history in the ticket indicates you don't have the internal experience.
So perhaps it may be the time to make the #a11y #accessibility appeal while you have the momentum.
We've had alot of pain dealing with other code forges accessibility processes. So perhaps this is the chance to create a really community focused process.
Cheers
Esther
Definitely worth a try given the recent attention. But our overall increase in e.g. followers was not very high, and most recent calls for contributors didn't lead to much attention to be honest.
We also discussed accessibility-related issues with the public in the past. We once refused to update Gitea until a regression with the menues was fixed. My experience is that people are loud to complain, and leave the debate as soon as we ask questions. For example whether honeypots are accessible to screen readers (it might be a good option to try). But from many those many voices who complain, we have to wait long for someone who will add something that actually pushes things forward.
And since there are some users who are sending us some "angry" messages via Social Media right now, and I'm the one who'll read them all in the end, instead of asking for help publicly I'll just not open social media for a day, or two, or for whatever time I see necessary to protect me from shitstorms.
I don't understand why people think they can post whatever to organization accounts, don't they know humans will read it in the end?
Whatever, since both the text-based captcha system and an audio alternative probably require quite some work, the easiest solution might be to try out some simple honeypot patch on Codeberg and see if we can bring this live within a few days. We'll also have to think how we can measure the spam impact, in order to protect our volunteer moderators from spending too much time cleaning up afterwards.
So you won't disable the CAPTCHA because it creates a problem for you? So you decided it's more important to pass that problem on to vision impaired users instead.
I suggest the following process:
Punting this down the road for years isn't on. We, the Open Source community, are recommending and supporting you. That is subject to change.
If email is your accessible solution, great. Let that be the process for ALL USERS. Asking vision impaired users to overcome additional obstacles isn't acceptable morally or legally.
Real humans have to deal with the accessibility issues too. Every day. You're just the next broken website in a long day at the end of a long week and that happens every day.
Don't take it personally. Take it seriously.
Perhaps lerntools/base#146 or MintApps/server#3 can be an alternative to Captcha?
I brought up this issue in the forge federation chat where @realaravinth is member and also creator of mCaptcha. He and @gusted are looking into possible use of this project on the mCaptcha matrix chat.
(Also added this info to the related fedi discussion)
I have passed a request to the new FossAbility chatroom where there is a community that is really actively looking to bring a11y improvement across the FOSS landscape.
FossAbility was started by @devinprater@devin.masto.host. Other fedizens real active in a11y:
I also created a new topic in the Gitea community forum related to this.
Hi everyone 👋,
I would like to give you a update, that the Codeberg team is looking into alternatives methods to prevent spammers without an non-accessibility captcha and we will discuss it more in-depth in the internal Codeberg meeting.
We're currently leaning into adapting mCaptcha as due to it's design it avoids all accesbility issues and also avoids a cat and mouse game whereby the captcha will require active maintaince. Feel free to give your two cents here about the issue and other possible captcha's.
PS: please keep it on-topic.
We're scheduling a public meeting tomorrow (Thursday 2022-07-21) at 19.00 CEST (17.00 UTC), probably via a BigBlueButton hosting, to talk about our captcha. We hope to get through the important topics within an hour. I'll
happily share the link here if anyone is interested.
@fnetX really appreciated. I sent a toot to thank Codeberg/Gitea and added a link to the meeting call.
I just created the meeting: https://lecture.senfcall.de/ott-zml-1vs-qcc. Feel free to join us, but the schedule will probably be rather tight.
Hi everyone 👋,
A big thanks to those that came to the meeting. It was a really great and productive meeting to discuss this issue.
Here is a summary of what happened in the meeting:
Overall, the general consensus is that mCaptcha is a better option than the current captcha and Codeberg would like to try it out in production as soon as possible. I will be personally be working on making this happen.
Hello everyone 👋,
I would like to give a small update about this issue. I've made progress towards integrating mCaptcha into Gitea and made a Pull Request for this. Once this is merged we can backport it to Codeberg and enable this captcha.
merged and backported for codeberg:
359d80295e(tested)next step would be to alter https://codeberg.org/Codeberg-Infrastructure/build-deploy-gitea/src/branch/codeberg-1.17/etc/gitea/conf/app.ini#L101 and deploy it ...
Hi everyone 👋,
Another progress update.
We're currently working on setting up an mCaptcha instance in the Codeberg infrastructure, but this has faced some problems. This is due to mCaptcha currently not having any released binaries. This on its own has some problems, which I will be working on with the mCaptcha author(@realaravinth).
Another accesibilty suggestion (I hope this is the right place :> ):
Green - red colorblind is the most common colorblind. Colorblind people might have difficult distinction these two colors on the commit graph. You should consider adding a colorblind mode like uBlock Origin.
This may or may not be the correct place for this accessibility issue so please feel free to suggest a better place
From what i can tell, when using codeberg from talkback screen reader on android the menu button at the top right of the page cant be focused or clicked without turning talkback off. Also on issue comments, the emoji button and the 3 horizontal dot menu can be focused but say nothing when the focus is on them. So you get user commented time ago, edited (if edited), silence, silence, then the text of the comment.
NOTE: "," above represents a swipe right to the next focusable element on the page
Thank you for the report. I'll try to confirm with the screenreaders I have at hand. From a quick glimpse at the element, they don't seem to be carrying a text alternative :-(
Should "edited" carry a more descriptive thing to indicate that you can click on it for a further dropdown with the history (e.g. "Edited (open history)")? I don't know what's the best practice there, I don't consider myself a frontend dev.
@fnetX it didnt cross my mind, but i just had a look and would say yes. Maybe something like "edited, click to view history" is what a screenreader would say while visually the edited with the down pointed arrow would stay the same.
Google PageSpeed Insights metioned some accessibility issues on the homepage.
Hi, I made a PR to fix this and other details.
Also PageSpeed Insights metioned many performance issues that we can dicuss on a seperate issue.
https://pagespeed.web.dev/report?url=https%3A%2F%2Fcodeberg.org%2FCodeberg%2FCommunity%2Fissues%2F479%23issuecomment-633066&form_factor=mobile&hl=en
https://pagespeed.web.dev/report?url=https%3A%2F%2Fcodeberg.org%2FCodeberg%2FCommunity&hl=en
https://pagespeed.web.dev/report?url=https%3A%2F%2Fcodeberg.org%2FCodeberg&hl=en
https://pagespeed.web.dev/report?url=https%3A%2F%2Fcodeberg.org%2FCodeberg%2Fgitea%2Fpulls%2F43&hl=en
Upstream issue report.
#817
Hi everyone,
First, let me tell you I love Gitea itself, both the software and its concept (a GitHub/GitLab alternative light on resources and written in go instead of Ruby).
A bit about me: I'm blind since birth, I'm a backend software engineer, used to work in accessibility for many years and maybe will return back to the industry.
I'm considering using Gitea for a project I'm starting with a couple friends. However, as there are blind devs and managers, including myself, now Gitea unfortunately is not a viable solution for us.
That said, I'm willing to do my best in helping with the accessibility issues, both in auditing and in fixing them.
Please note, I tested only on Windows + Chrome + JAWS so far. That's what I saw so far, in no particular order:
{{svg}}Go template directive.+button long time ago, but I need some help from you in figuring out how to do it properly in Gitea.Again, please don't take it as an offending critical comment, hopefully it's just the start of our discussion and future collaboration.
Hi there @Menelion
I DM'ed you in reaction to your Gitea forum post. Codeberg will soon be based on Forgejo, a downstream soft fork of Gitea. We aim to have a very open and inclusive community, and give due attention to accessiblity issues. There is a lot of work to do still, but the launch is planned mid December.
#831
#713
#862
Hi @Gusted, any news about this?
☝️
I've been busy with other Codeberg tasks (ex, the performance problems recently and the creation of Forgejo) ever since this. mCaptcha has been delayed ever since due to those events, unfortunately. I do hope to get it deployed when I have a larger chunk of time available in the next few months.