Brand New Screen Reader: Looking for the interested developers for FOSS project.
Closed this issue · 8 comments
Hey all,
So I thought that it is the best repo to post this hence I'm here with this.
Please read it carefully:
Actually Talkback has several flaws and the code is kind of quite legacy.
Jieshuo is comprehensive, but is closed source.
I'm planning to develop a very comprehensive, stable, powerful and feature rich screen reader for android which should be open source and can replace both the existing leading screen readers.
As there's NVDA on Windows, I want to implement the same for android too.
So, I'm looking for the interested developers.
Please let me know if you are interested.
Android Studio is quite slow and crappy from accessibility point of view, so my main target is to develop such screen reader purely in Xamarin .net.
But if I get many developers who are interested in Kotlin/Java(Android Studio) then I will consider that too.
However, .NET developers are more preferred for this project.
Please get in touch with me if you or somebody is interested and please share this post on your groups/mailing lists too so that we can get enough interested developers and contributers.
If you are really interested, then please fill this short and quick form:
https://forms.gle/fU3gEZDDWSAHFhfr7
Great iniciative which I will support.
Better something than nothing, but unfortunately I think Xamarin Will not be as flexible as Kotlin, because it will add additional translation layer (speed/performance issues), may require to use non-free software and/or libraries and we would unable to use native Android APIs.
Regarding Android Studio accessibility - it performs quite well with screen readers (I'm using JAWS and NVDA). Also studying some documentation might help:
- Accessibility | IntelliJ IDEA Documentation (as it's based on IntelliJ Idea)
- Accessibility features | Android Studio
Also, take a look at @Irineu333's SpeekTouch project as it's really promising.
Closing.
No it doesn't. I'm already into android studio since more than 7 years now. Even the most basic thing: The word navigation is buggy in the editor.
Anyways ...
Regarding Android Studio accessibility - it performs quite well with screen readers (I'm using JAWS and NVDA). Also studying some documentation might help:
- Accessibility | IntelliJ IDEA Documentation (as it's based on IntelliJ Idea)
- Accessibility features | Android Studio
🤣 Do you think that the person who has spent so many years with Android Studio hasn't checked these documentations before?
But yes, I will try with Canary/RC version once, may be they are better now.
Regarding Android Studio accessibility - it performs quite well with screen readers (I'm using JAWS and NVDA). Also studying some documentation might help:
- Accessibility | IntelliJ IDEA Documentation (as it's based on IntelliJ Idea)
- Accessibility features | Android Studio
@akash07k No, I am in no way questioning your experience, absolutely not.
Do you know this guy? https://vitechtoday.com/a-guide-to-becoming-a-visually-impaired-developer-android/
May be a good idea would be to contact him and ask how he configured Android Studio/screen reader if he boasts (in other posts too) that he are even successfully using code completion? I'm thinking about it from yesterday.
Navigating by words? From mine and my friends experience, I can say that using a braille display while coding is much, much better (special characters, indentation which is becoming more and more important in different languages etc.).
Sure. Drop me an e-mail - it's on my public GitHub profile.