Gregory's Server@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.
|
6 comments
 @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. |
@DavidGoldfield @ivory @ShellyBrisbin Likewise. We don’t need it anyway.