Gregory's Server|
19 comments
@ShellyBrisbin Mona is your friend. As are Metatext and Toot, somewhat. Tusker and Tooot! are also going that way. We don't need that guy.  @ShellyBrisbin we started building our app only a month ago. Other clients and the website have been out for much much longer. We will get there. 🙂 @ivory Much easier to build from the get-go even with a small team, and it can be a competitive advantage.  @ivory @ShellyBrisbin FWIW Shelly I think they’re underselling what’s already working. They have custom VO actions on posts in the feed, and basic dynamic type support throughout. Seems on par with Tweetbot in most places. @ivory @ShellyBrisbin I am very disappointed knowing that I am being excluded just so that you can get your app to market sooner. This is very disheartening, so I will be using other apps where the developers are making accessibility a priority. @DavidGoldfield @ShellyBrisbin you aren’t being excluded. We spent a lot of time making Tweetbot accessible and have had great good about it. Ivory already has those underpinnings. But we are currently focusing on completely missing mastodon features at the moment. @ivory @ShellyBrisbin @DavidGoldfield I think it is possible to concentrate on both. If you design with #accessibility in mind from the ground up, you get feedback from disabled users throughout the building process. That feedback is just as valuable as what #Mastodon feature folks would like to see next. #Inclusion is important, #disabled people should not be an afterthought. @Lynessence @DavidGoldfield @ivory @ShellyBrisbin as a person who is blind, I agree. #a11y @Lynessence @ivory @ShellyBrisbin @DavidGoldfield Amen. It is much easier and more efficient to design accessibility into a product from the get-go than to insert it as an afterthought. Additionally, it's been my personal experience that apps in which accessibility was prioritized from the beginning have much better accessibility to begin with. @ivory @DavidGoldfield the last time I checked out Tweetbot, it was inaccessible. So i’m glad to hear that’s changed. But that’s the peril of creating a product without accessibility and adding it later. You’ve already left the impression that accessibility isn’t important to you and people choose other apps. @ShellyBrisbin @ivory I love your apps and I really appreciate the work you’re doing. But this is a horrible response. It’s much easier to build accessibility in from the start than to try to add it later. Please don’t exclude people. @RobW If Paul is manning that account, you probably can consider yourself blocked. 😂 But I agree with you 100% @scottaw I honestly don’t want a pile on. Many people don’t realise accessibility from the start is easier and this is why they think it’s hard. I just hope that knowledge helps a little. I don’t expect for a second that Paul wants to make an inaccessible app. @RobW Oh, no, I agree. That's why I removed them from my reply. Paul was super block happy on Twitter though. He blocked me and I don't remember ever interacting with him. @scottaw that’s a real shame. Although I do understand why criticism can be difficult for a one person shop. @RobW @ShellyBrisbin @ivory so a “feature” that to work well has to be a part of everything in the UI/UX and can require significant code changes to account for is going to be bolted on? “Later”? When? 1.1? 1.2? 5.X? 10.X? Why, in 2022, would you say “we only want people with no disabilities to use our app until we “get around” to treating them like viable customers?” Regardless of intent, that is what that decision says and does. |
@ShellyBrisbin it will be at some point! We haven’t intentionally added any yet because we are focusing on getting to market asap. We are a small team and have a million things to do still! 🙂