I didn't want to have to go back to GitLab, but it appears as though Gitea is leaving me no choice. Unless someone has a better idea for a nice version control system that doesn't actively try to stop me from using it... https://github.com/go-gitea/gitea/issues/7057
@charlag@talon It's both funny and sad. Whenever Devin or someone else complains about inaccessibility, some fossbros show up to be like "Well yeah, but did you report it? I bet the developers would be happy to work with you if you did!" And yeah. Some might be. Most though react like "Oh, so this doesn't work for you? OK, fix it yourself thx."
@charlag@Mayana I was a happy Gitea user, even with some of the issues that were in place from day one. I know how time consuming implementing something like accessibility can be, and I'll do my part to work around the more minor issues. This is now no longer possible. Yes, I know, if something's broken I should try to fix it myself, but as you can see from that issue it's not an easy task, especially if it's just going to be bulldozed over at some point in the future anyway, like that last little bit of accessibility it did have was. And this was known. They knew that this would break "some" accessibility, yet they went ahead with it either way. That doesn't motivate me to try to fix it very much if I'm honest.
@talon@Mayana well yeah, exactly, when the maintainer is not interested there's nothing you can do (seen in all projects, from best to worst). If they will keep ignoring or overwriting your work it's not worth it.
@charlag@Mayana for example, the user/profile menu was completely inaccessible. The create repo menu was completely inaccessible. I cannot remember it ever being, so I just memorized the URI's for the most common things like /repo/create etc. Anyway, I now can't create repos anymore reliably.