Here’s a thread about the Mastodon client @ivory, and accessibility aka. #a11y. The app is in beta, so this is not a review so much as a followup to concerns I raised previously about the developers’ approach to this topic. (thread linked below.) Since I made that post two weeks ago, I’ve joined the TestFlight for the iOS version of the app, and can now write intelligently about the state of the app’s accessibility.
https://journa.host/@ShellyBrisbin/109565648260766092
Shelly Brisbin (@[email protected])

@[email protected] A question: will Ivory be accessible to screen readers? Have you included blind and visually impaired Mastodon users in the beta? OK, that’s two questions!  #a11y

Mastodon
Why it matters: Tapbots makes Tweetbot, a very popular Twitter app that routinely earns praise from the Apple pundit class, of which I am allegedly a member. But when I tried it some time ago, I found the app did not support VoiceOver, the iOS screen reader. And the developer never responded to requests that the app be made accessible.
When I saw that Ivory was potentially headed down the same path, including getting a lot of praise from people who say they value accessibility, I posted the above to ask Tapbots about their plans. The dev wrote back to say that theirs is a small team, and that accessibility was not on the current priority list. I maintain that if you make something good, and get credit in the community for doing that, people should know whether/how you approach accessibility.

@ShellyBrisbin Also, considering how Mastodon users are more aware of proper hashtags for readers, alt text for images, etc, seems like accessibility should be a priority for a Mastodon app.

To quote The Music Man, you gotta know the territory.

@djloehr Yes. Higher standards and all. Hence my little epic here.