5mo
@alexhall @jdking92 @Rosalyn @Bri And links are just the thing that blind users are noticing, because they read a post talking about a URL, try to interact with it, and it doesn't work. But I could happily post formatted lists, bold, italics, blockquotes, and both FastSM and Tweesecake would strip them out silently, and users would never know they missed anything to even complain about. I get that we don't want an HTML viewer for posts. But accessible clients need to do better than just assuming that HTML is completely unimportant and throwing it all away. They could convert the HTML to markdown. Or show the plain text version of the post that the server provides them. Or something else. But they don't. I'm sorry for ranting, but this has been making me crazy in Tweesecake for years now, and I hate that it's the same in FastSM.
1
2
3
0
User avatar
James Scholes @jscholes@dragonscave.space
5mo
@fastfinge @alexhall @jdking92 @Rosalyn @Bri This might be a rant, but it is a top tier, informative one. As someone who's pointed the link issue out to you at least once, I'm sorry you're getting so much repeated grief about it and hope it gets taken more seriously in new clients.
1
1
1
0
User avatar
Alex Hall @alexhall@mastodon.social
5mo
@jscholes @fastfinge @jdking92 @Rosalyn @Bri I agree with James. I didn't realize this was a problem. Now that I know, it seems like a serious oversight that should be a priority to address.
1
1
1
0
User avatar
Bri🥰 @Bri@fwoof.space
5mo
@alexhall @jscholes @fastfinge @jdking92 @Rosalyn I will try to see if I can work this out, but past a certain point, there's only so much I can do. If this what you say is true, and this plaintext representation of posts is indeed available in status objects, I've yet to evger find it. I'll look into it some more, because I definitely understand where you're coming from here, never mind I think the take of outright blocking FastSM/TweeseCake users is a bit hostile, I would still like to find a solution if I can
3
1
0
0
User avatar
Alex Chapman @alexchapman@tweesecake.social
5mo
@Bri @alexhall @jscholes @fastfinge @jdking92 @Rosalyn I agree, blocking FastSM/Tweesecake users is a dick move, I'd never even consider doing such a hostile move over something like this.
1
0
0
0
5mo
@alexchapman @Bri @alexhall @jscholes @jdking92 @Rosalyn If you reply to every single post I make complaining that the link doesn’t work, and demanding that I fix it, even when it’s your client at fault, I’m blocking. End of discussion.
1
0
0
0
User avatar
Alex Chapman @alexchapman@tweesecake.social
5mo
@fastfinge @Bri @alexhall @jscholes @jdking92 @Rosalyn You could just use filters to block words like Tweesecake or something, I'd never block over something like this
2
0
0
0
5mo
@alexchapman @Bri @alexhall @jscholes @jdking92 @Rosalyn No, I can’t. Because the complaints always come in the form of: “Your links don’t work and your posts are inaccessible. Fix it now.”
1
0
0
0
User avatar
Alex Chapman @alexchapman@tweesecake.social
5mo
@fastfinge @Bri @alexhall @jscholes @jdking92 @Rosalyn Well maybe filter out phrases like that or something, but entirely blocking people over it is not cool.
1
0
0
0
5mo
@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.
1
0
0
0
User avatar
Bri🥰 @Bri@fwoof.space
5mo
@fastfinge @alexchapman @alexhall @jscholes @jdking92 @Rosalyn Alright alright guys calm down. This really is not necessary.
2
0
0
0
5mo
@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.
1
0
0
0
User avatar
Bri🥰 @Bri@fwoof.space
5mo
@fastfinge @alexchapman @alexhall @jscholes @jdking92 @Rosalyn I, personally, was never saying that. I want/wanted to actually fix the issue.
2
0
0
0
User avatar
Alex Chapman @alexchapman@tweesecake.social
5mo
@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.
1
1
0
0
5mo
@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.
1
0
1
0
User avatar
Bri🥰 @Bri@fwoof.space
5mo
@fastfinge @alexchapman @alexhall @jscholes Yes, however, leading with hostility isn't the way.
2
0
0
0
5mo
@Bri @alexchapman @alexhall @jscholes I didn’t. I only became hostile when two different people called me a dick and a jerk.
2
0
0
0
User avatar
Alex Chapman @alexchapman@tweesecake.social
5mo
@fastfinge @Bri @alexhall @jscholes No one was calling, you, a dick and a jerk, I was just saying that blocking someone over this stuff is wrong.
1
0
0
0
5mo
@alexchapman @Bri @alexhall @jscholes Right, because I should just put up with the endless complaints. Doing anything else is a dick move, apparently.
1
0
0
0
User avatar
Alex Chapman @alexchapman@tweesecake.social
5mo
@fastfinge @Bri @alexhall @jscholes I did suggest using Mastodon's filters to not have to deal with that stuff, but you didn't like that idea either.
1
0
0
0
5mo
@alexchapman @Bri @alexhall @jscholes Right, because I should bend over backwards for people with broken clients. Filtering it out would mean filtering out the words inaccessible, link, and a bunch of other things. Why is that suddenly my responsibility when it’s not my stuff that’s broken?
0
0
0
0