@alexchapman@Bri@alexhall@jscholes@jdking92@Rosalyn Sorry, but if you’re so untitled to think that the entire world needs to avoid making standards compliant HTML formatted posts, because your client is utterly and completely broken, and you complain about it constantly, a block is all you deserve.
@Bri@alexchapman@alexhall@jscholes@jdking92@Rosalyn I’m sorry, but it completely is. I am sick and tired of being told that dealing with other people’s broken clients is my problem. And that I need to go out of my way to bend over backwards for people who have been told that they’re using an incompatible and broken client. It’s a bad look for blind people, who demand that everyone else follow W3C and WCAG standards, but then use apps that don’t do so themselves. And when I point this out, it’s my fault anyway, because I just shouldn’t use completely allowed and supported features that work literally everywhere else.
@Bri@fastfinge@alexhall@jscholes@jdking92@Rosalyn Ye same, once I start getting things going with Thrive's Mastodon client again, I also wanna have this fixed on there. Its stupid how the mastodon.py library hasn't got this fix built in yet and we have to manually figure this crap out.
@alexchapman@Bri@alexhall@jscholes@jdking92@Rosalyn Right, but this is my point. “Want to” isn’t strong enough language. If you emailed someone, and they said, “Yeah, I want to follow the accessibility standards. I need to do that some day, if I can figure it out,” you would be furious, and rightly so. Thrive, and FastSM, and every other client using mastodon.py is not following the standards. In the same way that we as blind people will turn to a developer and say, “I’m sorry, that’s not my problem. You need to be accessible.” I can expect the same thing from my fellow blind developers.
@Bri@fastfinge@alexchapman@jscholes Are your changes on master? I just pulled and don't see any other branches, but I don't work with Github that often. Git, all the time, but maybe there's something different with Github. I'm curious to get a look at exactly what's going on here.
@Bri@jscholes@alexhall@alexchapman And for the record, I did file an issue to the mastodon.py library you are all using. But was told it's an issue on the client end, not in there library. So this is, in fact, a battle I've been battling for literal years.
@fastfinge@jscholes@alexhall@alexchapman I guess in that case you were correct, we're able to get those plaintext statuses with mastodon.py. I only learned this though today, me personally.
@alexchapman@jscholes@alexhall@Bri Fair enough. My issue was never with people needing to learn. That's something I do every day. And I, too, have giant bugs almost every day, in almost everything I do. But my response to not following a documented standard is not "Yeah, I'll see if I can fix it at some point. Not a priority. Anyone who's upset about this is a jerk, and they should really be bending over backwards to work around the issue, and blocking people who complain endlessly that they aren't doing nonstandard things to just make it work makes them a jerk."
@jscholes@alexhall@alexchapman@Bri And before anyone says anything: I recognize we are all hobbyists. I recognize this is unpaid work on unpaid software. But I don't give sighted people a pass because of that if they develop inaccessible noncompliant software. Neither do I give blind people a pass if they develop accessible nonstandard software. For exactly the same reasons.
@alexchapman@jscholes@alexhall@Bri And once again. I only became hostile when people started saying I was doing things that made me a dick and a jerk, rather than actually engage with the issue. Similar to how blind people become hostile when developers tell us expecting accessibility is just too much, and we should stay quiet and deal with it.
@alexchapman@jscholes@alexhall@Bri Yup. And when things are inaccessible, blind people should also be policed about our tone, and never ever make frustrated statements about the issue. I hope we'll all remember this standard that we must all be held to the next time an app breaks accessibility and doesn't follow accessibility standards.
