Any update on screen reader support?

Hello,

Has any progress been made on making Fleet usable with a screen reader?

I installed it as soon as I was able and was dismayed to find that it was totally unusable. A few versions later you introduced a license agreement screen which was also totlaly inaccessible and made it impossible ot even get as far as the rest of the app.

I may be wrong but my understanding of Fleet is that it was a bit of a showcase for standard Kotlin UI elements. If this is the case then it concerns me even more that developers who start to use these components will be inadvertently also creating totally inaccessible apps. Whereas I would expect basic building blocks to be accessiblel from the start.

I get such mixed messages from you guys regarding accessibility.

On the one hand I've had a lot of very friendly and productive responses to forum posts and you've fixed a lot of bugs. PyCharm was pretty unusable when I started using VoiceOver but now for my day to day work it's actually quite good, albeit with some things that are still unusable or unintuitive. And the v2 toolbox app looked like it would be inaccessible from the start and I had a great dialogue with you and now it works great. (Well it did until the last version and now the menu extra button is broken - hoping that one day my support email might get a reply).

But on the other hand there is Fleet (unusable), YouTrack (button button button amongst other things) and DataGrip (which I gave up on a while ago).

Fleet particularly bothers me though given how long it took for IntelliJ based IDEs to become accessible. It was the chance to lay down groundwork and get it right from the start. It's always so much harder to make things accessible after the event, but it seems that's where we are again. It's particularly disappointing because I felt like we were on a bit of a roll at the time.

And now it's been almost 2 years since the YouTrack (https://youtrack.jetbrains.com/issue/FL-13800/Fleet-does-not-work-with-VoiceOver-menus-and-dialogs-are-not-accessible) and I still can't even get past the license agreement.

Apologies for the rant. It is just frustrating to read the regular updates on your blog about all the new features in Fleet and I am blocked from using any of them.

Also, last time I was on the forums I was able to create new posts but not reply. Not sure if this is fixed but if I go silent, that will be why!

John
 

2
3 comments
Hello, 

Thanks so much for your feedback!
We totally get how important accessibility is. Right now, it's not something we can tackle immediately, but we definitely hear you and will keep it on our radar for future updates.

Thank you!
0

Whilst I appreciate the reply, it's obviously not that important if it's still not even being considered 2 years later. If anything from what you say it sounds further away than ever.

Feels like a wasted opportunity to get things right from the start.

 

 

1
Hello,

I understand that there might have been an oversight in planning these tasks. I have shared this feedback with the UI team, and I hope that the issue will be given higher priority.

Sorry for the inconvenience and thank you!
-1

Please sign in to leave a comment.