I’m increasingly of the belief that the most effective way to fix accessibility issues in the sites and apps that we build is just do it. Don’t ask. Don’t have a lengthy discussion about it and ask the client or PM how they want to proceed or “if they want to fix it.” Just fix it. Can’t fix it with the current design? Change the design. Need a different interaction pattern?
The thing about Twitter is that it really lacks a lot of the features you'd expect from a true Mastodon replacement.
For example, there's no way to edit your toots (which they, confusingly call "tweets"—let's face it, it's a bit of a silly name that's difficult to take seriously).
"Tweets" can't be covered by a content warning. There's no way to let the poster know you like their tweet without also sharing it, and no bookmark feature.
There's no way to set up your own instance, and you're basically stuck on a single instance of Twitter. That means there's no community moderators you can reach out to to quickly resolve issues. Also, you can't de-federate instances with a lot of problematic content.
It also doesn't Integrate with other fediverse platforms, and I couldn't find the option to turn the ads off.
Really, Twitter has made a good start, but it will need to add a lot of additional features before it gets to the point where it becomes a true Mastodon replacement for most users.
"The Calm Web is ... a place that welcomes visitors, respects them, and does its utmost to delight them."
I love the big-picture view of this concept. It articulates what drives me and how I still find purpose in my career as a website maker.
The disease of unconscionable marketing tactics has caused real harm, but this article lays out practical steps towards a cure.