Jookia <contact@xxxxxxxxxx> writes: > I'm the only person to my knowlede that has ever implemented > accessibility improvements for Gitea and done an overview of the code. > Gitea isn't hostile to accessibility features, but the codebase is > written in such a way that making the UI elements screen readable would > require a rewrite. > Nobody's stepping up to that task so Gitea accessibility is just a pipe > dream at the moment. At the moment, ok. So what my former boss would have called "a simple matter of effort"? I probably don't have the web chops for that kind of a rewrite but I think it is worth my time investigating. > Does sourcehut have command line tools? It has an API. They could be written. Realize sourcehut has only been around a couple of years. But I know blind people who are actively using it right now and it works well for them in *any browser*. >> If you are a power user, having things explained to you all the time >> is just a distraction. Investing time to learn pays off mightily. >> Speech and braille are inherently low-bandwidth channels. I suspect >> screen magnification is somewhat low bandwidth too, just not as strongly. > > Ok. Do you only care about power users? In some very real sense, yes. If you don't care about power users first and foremost, you end up with a bunch of helpless perpetual newbies using an appliance rather than a tool. When it breaks or fails to meet their needs, they have nothing to fall back on but their learned helplessness. Again, I'll point an accusing finger at git. It's pretty terrible from a usability perspective, with its abstractions leaking all over its user interface and user documentation. This is the philosophy of only caring about power users taken to an extreme. > If someone links me to some patch or some issue, there's no way to go to > the code or other parts of the project. This is a huge navigation issue. Legit. > Yes, it's that much more of a burden. I've tried it with multiple > projects that I've contributed to and found that mail-based workflows > are a lot harder to deal with. Having stuff scattered everywhere instead > of a single page or set of pages is a nightmare for me. That's fair. > I'm not trying to waste your time by bringing up nitpicks with easy > answers, I'm voicing legitimate accessibility issues that you should be > aware about if you're going to choose to use sourcehut. You will be > excluding a set of users like me from contributing. Well, I've scratched it off of my list of things to consider using. I'm a Socialist; I really do want to give everyone a pony. -- Chris Brannon Founder: Blind and Low Vision Unix Users Group (https://blvuug.org/). Personal website: (https://the-brannons.com/) Chat: IRC: teiresias on freenode, XMPP: chris@xxxxxxxxxxxxxxxxx
