PSA: Codeberg currently does not implement accessible account registration. It is impossible for screen reader users to make a Codeberg account due to the image-only captcha. There's a manual fallback path, but no idea how long that takes. I've been forced to use the Wikimedia one, and that was about 3 months. This has been pointed out to them many times, and it's seemingly not something they're willing to fix.

If you didn't know what Codeberg's political stance really is and how they treat the inconvenient part of their userbase... I guess now you know.

▲

dchest 2 minutes ago | parent | next [-]

I wonder why they didn't just enable audio captchas, which are supported by the captcha package I wrote that they use.

▲

mlugg 8 hours ago | parent | prev | next [-]

> This has been pointed out to them many times, and it's seemingly not something they're willing to fix.

On the exact page you're on is a link to an issue [0] acknowledging that the CAPTCHA is inaccessible and expressing that they plan to drop it (albeit with no concrete time-frame). I don't at all understand your argument that Codeberg must be slow at replying to emails (the "manual fallback path") because Wikimedia are; these are two completely unrelated entities and I don't see why you would make inferences about one from the other.

[0]: https://codeberg.org/Codeberg/Community/issues/1797

▲

pier25 5 hours ago | parent | prev | next [-]

How is accessibility a political issue?

	▲	tsimionescu 4 hours ago \| parent [-]
		How is it not? In the not so distant past of the 1930s there were political parties advocating for the mass killing of people with disabilities, or at least the sterilization of those with heritable disabilities. There have been real campaigns in that period that did this type of forced sterilization, especially in some mental hospitals. You'll still find people espousing such beliefs, thankfully at the fringes for now. Accessibility is the opposite position of that - but it's by no means a universally accepted good, unfortunately, especially when it requires extra effort to implement.

▲

8 hours ago | parent | prev | next [-]

[deleted]

▲

bayesnet 7 hours ago | parent | prev [-]

It greatly saddens me to see how little concern there is for accessibility for dev tooling. It says something about our industry that accessibility is often viewed as a “luxury” feature that can be dealt with once you’ve reached some level of success or revenue or whatever.

I’m hopeful AI tools can improve qol for those who require screen readers and similar tools but have a sinking feeling that it will only transfer even more of the burden for accessible access from operator to user.

	▲	miki123211 2 hours ago \| parent [-]
		> It greatly saddens me to see how little concern there is for accessibility for dev tooling. This really depends on company size, and the company in question. Everything Microsoft does in this space is excellent, VS Code almost feels like an app specifically designed for the blind at times. Other large companies aren't as good, but their products are usually somewhat usable. Startups are a mixed bag, Zed is notoriously and completely inaccessible for example. Most SaaS tools wouldn't pass an audit but can be used with significant annoyances. Open Source is usually pretty bad. GTK still doesn't do any accessibility on non-Linux platforms. QT used to be completely inaccessible, although they've significantly improved in the last couple years. Linux in general has major issues that makes it almost unusable unless you understand it at a very deep level, and maybe not even then. Accessibility isn't a sexy thing to do, so unless you're practicing manager-driven development, nobody wants to work on it.