Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Re the just boosted post about the end of pinafore development, I completely understand the situation but I'm still sad to see it go. Now Mastodon isn't Twitter so it'll probably work for months if not years to come, but IMO this is going to leave particularly Windows and Linux users without a good desktop or desktop-like client (Mac OS is going to be served by Mona very well once it gets feature parody). But for the foreseeable future I'm probably going to stick to Pinafore as my main desktop client because it offers a ton of logical keyboard shortcuts, has excellent autocomplete support and reads posts in a very clear way even including media descriptions. The official Mastodon UI is almost there in that aspect, but the speech feedback you get when navigating with its keyboard shortcuts has many shortcomings (see https://github.com/mastodon/mastodon/issues/8192). Maybe this is the right time for this to get more love in either Mastodon or at least one of the forks like hometown, though that won't help anyone using something like Pleroma or its forks. #noxp
Right now, if using a screen reader in non-virtual mode so one can use the J and K keys to navigate up and down, and 1 through 3 to quickly switch columns, the screen reader NVDA on Windows with Fi...
Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
I think that got closed? My main issues with the web client are the "article 1 of 20" every time I navigate with J and K, and the fact that I always have to go to the first toot to start that kind of navigation (this last part happens sometimes in Pinafore too, but much less)..
Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
@sukiletxe Yes those two are annoying as well. As for that issue, true that it was closed but if you look at the comments the information presented lacks some important details like media descriptions and you only see absolute times while visually they're displayed as relative.
Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
I considered contributing to the official client instead of Pinafore, but I'm fairly sure that would require me to set up all the server stuff locally, since the front-end is tied to its instance. Setting up the Mastodon server is just not something I'm willing to invest time in, so the barrier to entry is just too high.
Revisiting my pinafore thread from last week this time without a CW, hello world from @semaphore! Really happy to know that Pinafore's legacy will live on.
Sukil Etxenike
in reply to Pitermach • • •Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Pitermach
in reply to Sukil Etxenike • • •Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Sukil Etxenike
in reply to Pitermach • • •Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Jamie Teh
in reply to Pitermach • • •Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Kevan
in reply to Pitermach • • •Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Rook
in reply to Pitermach • • •Content warning: Musing about the end of Pinafore development and official Mastodon UI accessibility shortcomings, long post
Pitermach
in reply to Pitermach • • •Brandon reshared this.
John Lipsey
in reply to Pitermach • • •Semaphore
in reply to John Lipsey • • •pax
in reply to Pitermach • • •